The Strategy Was Right. The Operating Model Wasn't.

In pharmacy, good strategies often fail in the distance between the executive decision and the patient-facing workflow.

STEADY STATE ADVISORS PERSPECTIVE

When a major initiative underperforms, organizations tend to reach for one of two explanations: the strategy was wrong, or the team did not execute.

That framing is usually too simple. In pharmacy, the strategy can be directionally right and the teams can work extraordinarily hard while the initiative still fails. The missing element is often the operating model - the practical system that connects an executive decision to thousands of actions, decisions and exceptions across the organization.

Execution is not what happens after strategy. The ability to execute is part of the strategy.

The distance to the frontline matters

A decision can sound elegant in a leadership meeting and become unrecognizable by the time it reaches the pharmacy counter.

Add a clinical service. Change the network economics. Introduce a new manufacturer program. Centralize a process. Create a new channel. Each decision may have a strong strategic rationale. But it also changes workload, timing, systems, inventory, training, incentives, patient conversations and exception volume.

If those changes are not designed as part of the initiative, frontline teams are forced to build the operating model in real time. They create workarounds, interpret ambiguous priorities and absorb exceptions. Leadership may see inconsistent execution. The frontline experiences an incomplete design.

Five places good strategies break

Workflow: The new activity is added without removing, simplifying or automating existing work. A theoretically manageable task becomes the final demand placed into an already constrained process.

Incentives: The stated priority and the measured priority are different. Teams are asked to deliver a new outcome while staffing, goals and performance systems continue to reward the old behavior.

Systems: Technology supports the standard transaction but not the information, judgment or exception handling required by the new model.

Ownership: Everyone is responsible for the outcome, which often means no one has authority to resolve cross-functional problems.

Feedback: Early warning signals are treated as resistance or isolated execution failures instead of information about the design. The organization scales the problem before it learns from it.

Pilot for learning, not confirmation

Many pilots are unintentionally designed to prove that the preferred strategy works.

They receive extra attention, hand-selected teams and temporary workarounds. The result may demonstrate possibility without demonstrating repeatability.

A useful pilot should test the operating model under conditions that resemble the environment in which it must survive. It should deliberately seek exceptions. It should measure the labor and coordination that are easy to hide. It should identify which results depend on heroic effort. And it should give frontline teams permission to explain not only what failed, but why the design made failure predictable.

The goal of a pilot is not to protect the original idea. It is to make the idea executable.

Make the invisible work visible

Pharmacy organizations depend on enormous amounts of invisible work: phone calls, clarifications, manual research, inventory searches, patient explanations, benefit troubleshooting and coordination between parties. Because this work is rarely captured in a strategic model, it can look free.

It is not free. It consumes capacity, contributes to burnout, delays patients and determines whether a program produces its intended economics.

Before scaling an initiative, leaders should trace the work at transaction level. Who touches it? How long does it take? What information is missing? What exceptions occur? Which decisions require judgment? What other work is displaced? This is not micromanagement. It is strategic due diligence.

The operating-model questions belong in the first meeting

Who will perform the work? What will they stop doing? Which system enables the process? What happens when the patient, claim, product or location does not fit the standard path? Who can make a decision across functional boundaries? How will the economics change when volume and complexity increase? What feedback will cause us to alter the model?

These questions are sometimes deferred because they feel tactical. In reality, they determine whether the strategic value exists outside the spreadsheet.

The strongest strategies are not simply ambitious. They are designed with respect for the people and systems that must make them real. When that operating reality is brought into the strategy early, execution stops being a hope and becomes a capability.

THE STEADY STATE QUESTION

Which part of this initiative currently depends on invisible work, local interpretation or heroic effort?