Linked Patient Learning

Loading Experience

A relay is never won by the fastest runners. It's won by the cleanest handoffs — and lost in the ones that drop the baton.
Watch a relay race and you'll notice the outcome rarely turns on who runs fastest. Four exceptional runners lose to a good team every time they fumble an exchange. The race is won and lost in the handoffs — the few seconds when the baton passes from one runner to the next, held, for an instant, by neither.
Pharma's patient infrastructure is a relay. The field runs a leg, then passes to the hub. The hub runs its leg, then passes to specialty pharmacy. Patient services, market access, each runs its stretch and hands off to the next. And the patient is the baton.
Every function can run its leg well. The patient still gets dropped — not on anyone's leg, but in the exchange between two of them, where the baton belongs to no one.
To the patient, the handoff is the whole experience
Here is what makes the baton the right way to see it: the patient feels every exchange.
The handoff isn't an abstraction to them, and it isn't an org chart. It's a transition they live through — the call that doesn't come after the field rep moves on, the coverage question that falls between market access and patient services, the refill that lapses in the gap where one team's job ended and the next team's hadn't yet begun. To the patient, those seams are the experience of being on therapy. The handoff is the moment they feel whether the infrastructure is holding them or dropping them.
A patient rarely leaves because one runner was slow. They leave because, at the exchange, no one had the baton.
Every runner owns their leg. No one owns the exchange.
Ask a pharma team who's responsible for persistence, and every function answers confidently — each describing its leg of the race.
Patient services owns the support experience. Market access owns coverage and affordability. The field owns the prescriber relationship. Specialty pharmacy owns fulfillment. Each is measured on its own leg, reviewed on its own leg, held to account for its own leg. And each runs it well.
But persistence isn't produced by any single leg. It's produced by the sequence — the baton moving cleanly from one runner to the next, across coverage changes and refill cycles and the ordinary disruptions of a life. And every exchange is a seam between two functions, each of which believes the baton is the other's to carry at that moment.
The patient who drifts off in a coverage gap didn't fall on market access's leg or patient services' leg. They fell in the exchange between them — a moment that belonged to no one's dashboard, no one's review, no one's job description.
You can field four excellent runners and still lose the race in the handoff. Because excellence on a leg does nothing for the exchange between legs. No one is measured on the handoff. So no one owns it. So the baton drops.
Why the drop is invisible until the race is already lost
The reason this persists is that each runner can only see their own leg.
Market access can see that coverage lapsed; it can't see that the lapse went unaddressed because patient services never knew the baton was coming. Patient services can see a patient went quiet; it can't see that the silence started with a prior-auth problem two legs back. Everyone is watching their own stretch of track, and no one is watching the exchange zones where the baton actually hit the ground.
So the drop doesn't show up as a drop. It shows up, eventually, as a persistence number lower than anyone expected, with no single function able to explain it — because the loss happened in the exchange none of them could see, and none of them owned. By then the baton is on the ground and the race is already lost. The post-mortem stalls where it always stalls: every runner ran their leg.
Ownership isn't the same as accountability
Here's the distinction that matters for a leader standing above the track.
You can hold every runner accountable for their own leg and still have no one who owns the race — because the race is won in the exchanges, and accountability, as usually structured, stops at the edge of each leg. Functional accountability, however rigorous, cannot produce an owner for something that lives in the space between functions. Making each runner faster does nothing for the handoff.
Someone has to own the exchanges. Not another runner added to the team, but a view of the whole race at once — where the handoffs are, which ones drop the baton, and what it costs when they do. Ownership of persistence begins with the ability to see across the legs that produce it, because you cannot own what you cannot see, and no runner can see the whole race from inside their own lane.
That whole-race view — where the baton is dropping across the exchanges, made visible to every function at once — is what our patent-pending diagnostic, the Gap Finder, was built to produce. Not another runner. The view from above the track that no single leg can have.
The question worth putting to your team
At your next cross-functional review, it's worth asking the question directly and watching what happens.
Who has the baton in the exchange between our functions — and how would we know if we were dropping it there?
If every function answers by describing its own leg, and no one can answer for the exchange between them, you've found it. Not a slow runner anywhere on the team.
A dropped baton, in the space no one's job includes.
Linked Patient Learning helps pharma teams see where patient persistence leaks across the handoffs between functions — the exchanges no single team owns.
Written by
Liza Prettypaul-Lodhia
Share your details and we'll send you the playbook.