A Business Case Is Not a Decision

A leadership team is reviewing six strategic priorities:

One promises growth.

One promises cost savings.

One promises better access.

One promises stronger clinician efficiency.

One carries political visibility.

One has a particularly persuasive sponsor.

All of them sound important. All of them have some logic behind them. All of them arrive with different assumptions, different levels of financial detail, and different levels of executive polish.

At that point, the problem is no longer strategy.

It is comparability.

And that is one reason good initiatives still lose.

Not because they lacked value.Not because nobody cared.But because the decision process around them was not strong enough to surface value clearly, compare trade-offs cleanly, and hold up under scrutiny.

This is a familiar pain for health system strategy leaders.

A good initiative can lose because it was framed in weaker language than a less valuable one. A high-potential priority can stall because its financial logic was not structured well enough for the room. A decision can drag on for weeks — not because the organization lacks intelligence, but because it lacks a repeatable way to weigh competing choices under pressure.

That is where the real problem lives.

Most health systems do not lack ideas, dashboards, analytics teams, or strategy decks.

They lack a stronger decision layer.

And when that layer is weak, several patterns show up again and again.

1. Too many initiatives enter the room with no common logic

One initiative is framed around growth. Another is framed around efficiency. Another is framed around patient access. Another is framed around digital modernization.

Each one may be valid. But if they arrive in different formats, with different assumptions and different levels of financial rigor, leaders are not really comparing priorities.

They are comparing narratives.

That is a serious problem.

Because in high-stakes environments, the better-packaged initiative often beats the better initiative. The one with the most persuasive sponsor or the cleanest slides lands. The one with the clearest strategic logic but weaker framing stalls at the gate — or never makes it into the room at all.

What gets funded is not always what creates the most value. It is often what feels easiest to defend in the moment.

That is not disciplined prioritization.

It is negotiation disguised as strategy.

And everyone in the room knows it. Which is why strategy conversations in capital-constrained health systems often feel less like rigorous analysis and more like political maneuvering — with high stakes and uneven footing.

The root issue is structural. When there is no common framework for presenting and comparing priorities, the decision process defaults to whoever argues loudest, whoever has the most institutional credibility, or whoever packaged the business case most convincingly. None of those variables have anything to do with actual value.

2. Finance gets involved too late

A priority can look strong in a strategy conversation and still collapse when the room shifts toward capital scrutiny.

That is when the harder questions arrive:

What exactly is the value?Over what timeframe?What assumptions is this based on?What do we give up if we fund this now?What would change the recommendation?

Too often, those questions arrive after enthusiasm has already formed.

The initiative has been socialized. Leadership has gotten emotionally attached. Momentum exists. And now finance is being asked to validate something that already feels decided — instead of evaluating it against alternatives on shared terms from the start.

This creates two problems at once.

First, it turns the finance review into a defensive exercise rather than an analytical one. The goal shifts from "what is the right decision?" to "can we make the numbers work for what we've already signaled we want to do?"

Second, it means the assumptions underlying the initiative have never been stress-tested in the open. They were formed privately, socialized informally, and are now being presented as if they are settled. When finance finally pushes on them, the pushback reads as obstruction — not diligence.

This is one reason strong-looking priorities suddenly stall.

The problem was not the initiative itself.The problem was that the underlying logic was never structured well enough to survive scrutiny.

And by the time scrutiny arrives, there is no clean way to engage with it without reopening everything — which is exactly what most organizations are trying to avoid.

3. The same decisions keep getting re-litigated

This is one of the most frustrating patterns for strategy leaders.

A priority gets discussed.A recommendation gets socialized.A decision appears to move forward.

Then, weeks or months later, the same debate comes back in slightly different language.

The assumptions are rebuilt from scratch.The rationale gets re-explained to a slightly different audience.The trade-offs get reopened because someone new is in the room.The same questions get asked again, by the same people who asked them last time.

Why?

Because the organization preserved a moment — maybe a deck, maybe a business case, maybe a verbal alignment in a room — but it did not preserve the decision logic itself.

The next time the question resurfaces, there is no structural base to return to. There is only the vague memory of a previous conversation and the artifacts that capture its conclusions without capturing the reasoning that produced them.

So the work restarts.

And this compounds in ways that are easy to underestimate. Every re-litigated decision consumes senior time. Every rebuilt business case creates new versions with slightly different assumptions that cannot be reconciled with the old ones. Every reopened trade-off signals to the organization that no decision is ever truly settled.

Over time, this makes prioritization feel heavier than it should. Leaders spend more time managing process than making decisions. Strategy begins to feel like it is moving slowly — not because the problems are hard, but because the infrastructure underneath the process is too thin to hold.

Nothing compounds.

The organization gets smarter, but the decisions don't.

4. Good initiatives lose to stronger storytellers

This is uncomfortable, but real.

Some teams are better at packaging a story than others.Some leaders are more persuasive in a room than others.Some sponsors know how to create momentum better than others.

When there is no stronger decision layer underneath the process, those differences matter too much. The quality of the pitch substitutes for the quality of the logic. The confidence of the presenter substitutes for the rigor of the assumptions.

The result is that the organization starts funding presentation quality more than decision quality.

A good initiative with weaker framing loses to a weaker initiative with stronger sponsorship.

That does not just distort one decision.

It erodes confidence in the process itself.

And once that erosion sets in, it is hard to reverse. The teams that learn to package well keep packaging. The teams that rely on substance keep getting surprised when substance is not enough. The organization gradually trains itself to reward advocacy over analysis — and the people who see what is happening grow quietly frustrated.

Prioritization becomes more political, not less.

The conversation that should be about where to deploy scarce capital becomes about who can build the most effective coalition before the decision meeting. And the strategy leaders who are best positioned to add value — the ones who understand the whole portfolio, who can see the trade-offs across competing priorities — find themselves spending more time managing optics than doing analysis.

This is a slow and corrosive dynamic. And it is almost entirely a structural problem.

5. Execution starts with misalignment already baked in

Sometimes an initiative gets approved, but the decision underneath it was never fully resolved.

Finance may not see the value the same way strategy does.Operations may not agree on sequencing.Leadership may not share the same assumptions about what success looks like.Dependencies may still be vague.Risk tolerance may still be unspoken.

So execution begins with hidden disagreement inside it.

From the outside, the initiative looks approved.From the inside, the logic is still unstable.

The first sign is usually a missed milestone. Then a scope question that should have been answered before kickoff. Then a budget conversation that reopens what was supposed to be settled. Then a cross-functional friction point that escalates faster than anyone expected.

What looks like an execution problem is often a decision problem that was passed forward.

The approval came, but the clarity did not come with it. The organization moved forward on a shared commitment to proceed without a shared understanding of what proceeding meant. And the gap between those two things — between approved and actually aligned — is where slippage begins.

This pattern is frustrating precisely because it is invisible until it surfaces as something else. A strategy miss. A budget overrun. A leadership tension that nobody anticipated. The root cause is rarely diagnosed correctly because by the time it shows up, it looks like an operations problem, a capability problem, or a resourcing problem.

It was a decision quality problem.

It just showed up three months late.

This is why good initiatives still lose

Not because the organization lacks intelligence.

Not because people do not care.

Not because there is no data.

But because the decision process is still too dependent on fragmented business cases, presentation quality, uneven assumptions, and logic that cannot be reused once the meeting ends.

That is the deeper issue.

McKinsey's research on transformation outcomes points to something important: even successful transformations regularly fall short of capturing the full financial value at stake. The conclusion most organizations draw is that execution discipline is the gap. But a closer read suggests the problem often starts earlier — in how priorities are structured, compared, and defended before they ever move into execution. The value loss is not just downstream. Much of it is upstream, in a decision process that was not rigorous enough to set execution up to succeed. (mckinsey.com)

Geisinger's analytics governance work offers a useful contrast. A presentation of their approach describes reduced duplicative efforts and better distribution of resources across priorities. That is not simply an analytics story. It is a structure story. It describes what becomes possible when an organization creates repeatable discipline around how requests are evaluated, how priorities are compared, and how resource allocation is governed over time — not just in a single budget cycle, but as a compounding capability. (icahn.mssm.edu)

The distinction matters. Analytics answers questions. Structure changes how questions get formed, compared, and decided.

Most health systems have invested heavily in the former. Very few have invested seriously in the latter.

What to do about it

If good initiatives keep losing, the answer is usually not "get better at storytelling."

The answer is to strengthen the decision model itself.

That means moving toward a structure where:

• initiatives are evaluated on shared logic, not individual framing

• assumptions are made explicit before the room gets attached to a direction

• trade-offs are visible before polarization sets in

• value ranges are honest about the uncertainty underneath them

• dependencies and risks surface early, not at execution kickoff

• decisions become easier to defend — and easier to revisit cleanly when conditions change

This is where decision maturity begins. Not in better presentations or faster analytics cycles, but in a layer of infrastructure that sits underneath those things and gives them something durable to connect to.

A strong decision process should help leaders answer a clear set of questions:

What exactly are we comparing?What assumptions are driving this recommendation?What trade-offs are we accepting?What would change the answer?What deserves funding now, what deserves a pilot, and what should wait?

Those are not presentation questions.

They are not analytics questions.

They are decision-layer questions.

And the organizations that get consistently better at answering them will have an advantage that compounds in a way that dashboards and data investments cannot replicate on their own. Because in a market where capital is tight, governance pressure is real, and strategy leaders are being asked to make fewer, better bets, the winners will not simply be the systems with more data.

They will be the systems with stronger decision logic.

That is what keeps good initiatives from getting lost.

When the pressure is high and the room wants answers, clearer logic changes everything. If you are tired of defending high-stakes decisions with slides, fragments, and gut feel — start here. See how the Strategy Intelligence Engine helps you bring more clarity, stronger trade-offs, and greater confidence into decisions that carry real weight. Download the Sample Decision Artifacts here.

Sources:

McKinsey — Why even successful transformations fall shorthttps://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/successful-transformations

Analytics Governance in Support of Health Care Transformation (Geisinger, hosted by Mount Sinai)https://icahn.mssm.edu/files/ISMMS/Assets/Departments/Population%20Health%20Science/Analytics-Governance.pdf