The New Leader Inherits the Blind Spots, Not Just the Role

After a restructuring, the hardest part of the job isn't fixing what's broken. It's finding out what's broken before it costs you.

A new leader steps into a commercial or patient-support role after a restructuring, and the calendar starts running immediately. There's a launch to protect, a team to steady, a leadership team that wants a plan.

And there's a problem no one puts on the org chart: the person who knew how the patient infrastructure actually worked is gone.

Not the process documents — those exist. The knowledge. Where the handoffs quietly failed. Which vendor relationship was held together by one person's relationships. Why persistence dipped in the second quarter last year and what was done about it. That knowledge left when the reorg did, and it rarely got written down.

So the new leader inherits the role, the title, and the budget — and a set of blind spots they don't yet know they have.

The six-month rediscovery

What happens next is predictable, and expensive.

The new leader does the only thing they can: they start rediscovering. They meet stakeholders. They read the vendor contracts. They sit in on calls, audit the processes, ask questions, and slowly assemble a picture of what they actually inherited. It's diligent work, and it takes six to twelve months to do well.

The trouble is that the patient journey doesn't pause for the leader to catch up. Patients keep moving through the infrastructure during those months — through the handoffs the new leader hasn't mapped yet, the gaps no one flagged, the seams that were already leaking before they arrived. By the time the leader has rediscovered where the problems are, two or three quarters of patients have already moved through them.

The discovery period isn't neutral. It's a window during which the infrastructure runs on assumptions the new leader hasn't had time to test — and the persistence cost of those months lands later, as a number that's harder to explain because no one owned the transition.

The trap: rebuilding what was there before

There's a second, subtler problem, and it's the one that quietly wastes the most.

A new leader under pressure to show progress defaults to rebuilding what existed before — because that's what the org chart says should be there, and because rebuilding is legible. Stand the team back up. Re-staff the roles. Restore the structure.

But what existed before wasn't necessarily working. The restructuring may have removed roles that mattered and kept ones that didn't. Rebuilding the old structure faithfully means inheriting the old blind spots along with it — recreating the same seams, the same unowned handoffs, the same leaks, now with a new team that believes it's starting fresh.

The instinct to restore what was familiar is strong, and it's often wrong. The question isn't "what was here before?" It's "where are patients actually falling through now, and does the structure I'm about to rebuild address that — or just look like what was here?"

Starting from evidence instead of archaeology

The alternative to a six-month archaeology project is to start from a scored picture of what you inherited, in weeks rather than quarters.

Instead of rediscovering the infrastructure one stakeholder interview at a time, a new leader can establish a baseline directly: where the patient journey stands today, where persistence is leaking across the functions, which gaps are inherited structural problems versus which are new. That turns the first board meeting from a request for more time to learn into a scored diagnostic and a prioritized plan — evidence instead of assurances.

This is the specific situation our patent-pending diagnostic, the Gap Finder, was built to compress. It gives a new leader the map of what they inherited — the blind spots made visible early, before the discovery period costs another two quarters of patients. Not to replace the leader's judgment, but to give it something to work from on day thirty instead of day two hundred.

The point isn't to skip the learning. It's that a new leader shouldn't have to lose two quarters of patients to find out where the infrastructure was already broken.

The question worth asking in the first month

For any leader who's just stepped into a restructured role, one question is worth asking before the rebuild begins:

Do I actually know where patients are falling through the infrastructure I inherited — or am I about to rebuild what was here and hope it holds?

If the honest answer is that you're still assembling the picture, that's not a failure. It's the normal condition of inheriting a role after a reorg.

But the patients moving through the gaps you haven't found yet aren't waiting for you to finish learning. The faster you can see what you inherited, the fewer of them you lose while you find out.

Linked Patient Learning helps new leaders see what they inherited — where patient persistence is leaking across the infrastructure they've stepped into, before the discovery period costs another quarter of patients.