Workflow before feature
Map the human work, system boundaries, exceptions, evidence, and handoffs before deciding what belongs in software.
Healthcare product strategy
I help healthcare companies, especially in behavioral health, make the choices between a promising idea and a durable product: whose problem matters, what the system should own, where people stay in control, how value will be proven, and what your team should build next.
Where strategy breaks
Make those choices explicit enough that product, technology, operations, sales, and implementation can move together.
Map the human work, system boundaries, exceptions, evidence, and handoffs before deciding what belongs in software.
Choose the economic buyer, daily operator, approval path, and proof threshold instead of relying on a broad healthcare-AI narrative.
Sequence the smallest product and operating change that can create measurable value, credibility, and the next commercial option.
Engagements
A practical path
Identify the user, buyer, workflow, business constraint, and risk that the strategy must resolve.
Define the promise, system boundaries, operating loop, evidence, delivery model, and commercial path.
Turn the thesis into a pilot, prototype, roadmap, or operating change with observable success criteria.
Why this perspective
In behavioral health, Ian co-founded TheraMatch and then led product and technology work across the network, claims, and payment systems around TPN Match. TheraMatch and TPN Match reached $1 million in ARR and more than 1 million lives under care in less than 12 months.
Ian Harman has also worked across member and payer platforms, provider networks, virtual care, clinical workflows, enterprise communications, privacy, implementation, product marketing, and healthcare EDI.
That range matters because a healthcare product fails as easily in implementation, trust, workflow fit, or buyer proof as it does in code.
Common questions
It is the set of choices connecting a real care or administrative workflow to a valuable product, a feasible delivery plan, measurable evidence, and a buyer willing to adopt it.
Yes. A paid-pilot engagement can define the specific buyer, operational promise, safety boundaries, workflow, evidence plan, pricing hypothesis, and implementation path needed to test value honestly.
Yes. Product direction is translated into architecture, integration, data, team, sequencing, and operating implications so the strategy can be delivered rather than merely presented.
Make the next decision count
Most strategy engagements start with my two-week Product & AI Assessment. I work with the people closest to the problem, compare what you could build, buy, change, or stop, and leave your team with a recommendation it can act on. If you need someone to own the product agenda after that, we can talk about ongoing leadership.
Related reading
Guides for practices and essays for founders and operators, gathered in one place.