Your health tech product may work exactly as designed and still leave customers unsure what to do next. A look at the handoffs, ownership and everyday operations that shape the experience around the software.
The customer often ends up doing the coordination the company hasn’t done. They repeat the story, chase the update, work out which team owns the problem. I’d add that to the walkthrough: where are we asking the person we’re meant to be helping to hold the whole thing together? It makes the cost of a vague handoff much harder to dismiss.
I think "A founder becomes a bottleneck when the same question keeps finding its way back to her" is such a useful way to look at it, because it's often hard for the owner to see how they've contributed to becoming the bottleneck. For a leader to be effective, they must relentlessly eliminate ambiguity in every conversation, and handoffs are where so much of it hides.
I love "Who has this now?" as the question to trace through a workflow, and naming an owner for every handoff. Thank you for this, Katie.
What stands out is that the internal handoff becomes part of the customer's experience, whether or not the company considers it part of the product.
A founder who repeatedly supplies missing context can keep the experience functioning while preventing the company from discovering that the handoff itself needs redesign.
The recurring question finding its way back to the founder is a useful diagnostic signal.
The seam I run into at work is onboarding and sales. Our onboarding emails skip any account sales already owns, but that rule lived inside the email workflows. When I built a second thing that drafts emails, it didn't know.
For that workflow walkthrough, I'd include a handoff the receiving team sends back. Who holds it while the missing information is found? Naming a sender and a receiver can still leave the rejected work belonging to neither.
The customer often ends up doing the coordination the company hasn’t done. They repeat the story, chase the update, work out which team owns the problem. I’d add that to the walkthrough: where are we asking the person we’re meant to be helping to hold the whole thing together? It makes the cost of a vague handoff much harder to dismiss.
I think "A founder becomes a bottleneck when the same question keeps finding its way back to her" is such a useful way to look at it, because it's often hard for the owner to see how they've contributed to becoming the bottleneck. For a leader to be effective, they must relentlessly eliminate ambiguity in every conversation, and handoffs are where so much of it hides.
I love "Who has this now?" as the question to trace through a workflow, and naming an owner for every handoff. Thank you for this, Katie.
What stands out is that the internal handoff becomes part of the customer's experience, whether or not the company considers it part of the product.
A founder who repeatedly supplies missing context can keep the experience functioning while preventing the company from discovering that the handoff itself needs redesign.
The recurring question finding its way back to the founder is a useful diagnostic signal.
The seam I run into at work is onboarding and sales. Our onboarding emails skip any account sales already owns, but that rule lived inside the email workflows. When I built a second thing that drafts emails, it didn't know.
For that workflow walkthrough, I'd include a handoff the receiving team sends back. Who holds it while the missing information is found? Naming a sender and a receiver can still leave the rejected work belonging to neither.