top of page

Your three-year plan has a half-life of one policy change

Nov 10
7 min read

Updated: 2 days ago

A wooden block tower with pieces pulled out

Every health system has a plan. A good one, usually. Months of work, a ranked set of initiatives, a three-year horizon, sign-off from the board.


Then something moves.


A payer-mix shift. A reimbursement change. A policy that redraws how Medicaid is financed. A merger that changes the footprint. A labor market that reprices the whole staffing model. Pick any one. They land every year, and some years they land in clusters.


Here is the tell that should worry every leader who just approved a plan. When the shock lands, almost no one updates the plan. They set it aside and build a new one.


The work could not bend. So it broke.


That is not a failure of planning. The planning was rigorous. It is a limit of what planning was asked to produce. A snapshot of a world, frozen on the day it was approved, with no way to move when the world did. A plan you cannot re-run is a plan you will rebuild from scratch, on the worst possible week to be starting from scratch.


The property that would change this has a name. Reusability. The ability to change what moved, and only what moved, and watch the plan re-settle instead of starting the whole exercise over.



The fragility is the problem, not the shock


Shocks are not surprises. Everyone in healthcare knows the ground moves. The current environment is the case study. Kaufman Hall describes a "new normal" for 2026: rising expenses, a larger share of revenue from public payers, and climbing bad debt. (kaufmanhall.com)


Leaders see it. Deloitte's 2026 survey asked healthcare finance leaders about the outside forces and capability gaps that could affect margins. Only 47% say their organizations are well prepared to manage them. (deloitte.com)


None of that is a shock in the sense of a surprise. It is a shock in the sense that it invalidates the assumptions underneath last year's plan.


The change was never unforeseeable. The problem is that the plan had no way to absorb it. So a predictable change in the world produces an unpredictable scramble inside the building, every time.



Why the plan can't bend


Walk through what happens when a plan meets a shock, and the fragility is easy to see.


The plan is a set of conclusions, not a model. It says fund these, defer those. It does not carry the live logic that produced those answers. So when an input changes, there is nothing to turn. There are only conclusions to discard.


The assumptions are buried and scattered. When a rate changes, which initiatives depended on that rate? No one can say quickly, because the assumption sits invisibly across dozens of separate cases in dozens of formats. You cannot update what you cannot find.


The logic lived with people, not in a system. It was in the strategy team's heads, or a consultant's engagement that has since closed. In a sector with this much turnover, the ability to re-run the plan often walks out the door with the person who built it.


Every initiative was scored once, on its own basis. Even if you wanted to rescore, there is no shared engine to feed the new numbers into. There are twenty separate cases, so updating the plan means redoing twenty business cases.


And no one owns the re-run. There is no trigger and no cadence for "the inputs moved, rescore the portfolio." So the shock produces an ad hoc scramble, and a scramble defaults to a full restart, because no lighter option was ever built.


Put those together and you get the quiet, expensive truth of health system planning. The plan is not updated because it cannot be. It can only be replaced.



The real cost is the blindness


It is tempting to count the cost of fragility as wasted hours. Months of good work, set aside and redone. That is real, and when the scarce resource is the capacity to build the work, it is not small.


The larger cost does not show up on any invoice. It is the stretch between the shock and the rebuilt plan. The organization keeps making real commitments against a map everyone already knows is dead.


Capital gets committed. Build capacity gets assigned. Initiatives keep moving, because the business does not pause while strategy regroups. All of it runs on the old assumptions, for the full quarter or two it takes to rebuild. The longer the rebuild, the longer the blindness. That window, not the rework, is where the money goes.



What the field actually built


Health systems have invested heavily in individual decisions. A revenue-cycle build here, a staffing model there, a documentation project, a care-coordination effort. Each one was justified by its own business case. Each case was built on a snapshot: these rates, this volume, this payer mix, this cost of labor.


Those snapshots expire. When the payer mix shifts toward public coverage, revenue-integrity work gains value relative to growth bets. When the labor market tightens, a staffing-heavy initiative gets harder to execute, not just less valuable. The order that made sense last year is quietly wrong this year.


Almost no one re-ranks. Not because the people are not capable, but because each case was a static artifact, not a line in a model that can be re-run. The field built a portfolio of decisions, each one a monument to the conditions on the day it was approved. What it was never given is the one thing that would let the portfolio survive a change in those conditions. A shared, re-runnable basis underneath all of them.



Rescore, don't restart


The answer is not a better plan. A better plan is still a snapshot. The answer is a different kind of artifact underneath the plan.


When competing initiatives are scored on one shared, explicit, deterministic basis, the plan stops being only a document and gains a model. The assumptions are visible and named, not buried. The logic is in a system, not in someone's head. When a shock lands, you change the assumption that moved and watch the ranking re-settle.


Three properties make that possible.


The initiatives are comparable, so there is one model to re-run, not twenty cases to redo.


The logic is defensible, so when you change one input you can see exactly what moved and why. Determinism matters here for a reason most people miss. If the same inputs always produce the same score, then one changed input produces one traceable change in the ranking. You are not re-arguing the whole portfolio. You are watching a single assumption propagate.


And the evaluation is reusable, so it survives the shock. The plan you can re-run is worth more than the plan you rebuild. Not because it is more accurate on day one. Because it is still alive on the day the world changes.


Evidence from adjacent decisions points the same way. Premier's account of Kaleida Health describes a systemwide value analysis structure, applied the same way across the system. It put clinical and supply chain teams on shared data about cost, quality, and outcomes. Premier credits it with $17.7M in savings in 2022 and about $75M from 2018 to 2023. Those were purchasing decisions, not strategic initiatives. The lesson carries: the gain came from a structure the system kept using, not a single brilliant plan. (premierinc.com)



A system of record, not a report


That is the idea behind what Adaptive Product built.


SIP is the system of record for decision-making. The Data Value Accelerator (DVA) is the comparison engine for strategic initiatives.


The words were chosen with care. A report is something you commission once and file. A system of record is where the decision lives, cycle after cycle. It holds the assumptions, keeps the reasoning, and is still there when the next shock lands.


DVA is the engine that runs on it. Every competing initiative is scored on one measure of value, at weights your organization sets. Quality, access, and mission carry weight alongside money. Each score carries its assumptions in the open, so every ranking can be defended in the room and reused next cycle.


The score is the Value Realization Index (VRI), on a 0 to 100 scale. VRI is the FICO score of strategic initiatives. Unlike FICO, the reasoning is visible and the priorities are yours.


Here is what that means on the week a shock lands. A reimbursement assumption changes. You change it once. DVA rescores every initiative that depended on it. Each VRI re-settles, and because the same inputs always give the same score, you can trace exactly which initiatives moved and why. You are re-running a model, not rebuilding twenty business cases.


The engine compares. The committee decides. What changes is that the committee decides on a current map, instead of a dead one.



The question to ask before the next shock


You do not get to choose whether the ground moves. You only get to choose whether your plan can move with it.


So before the next shock lands, ask one question of the plan on the table right now. If one major assumption changed tomorrow, say a rate or the payer mix, could you update the plan? Or would you have to rebuild it?


If the answer is rebuild, the plan is already fragile. The shock has not happened yet. It is coming, the way it always does. Not because the work was wrong. Because it was never built to be re-run.


Test the plan before the shock does. DVA is in early access, and it starts with a 30-minute demo. Bring the initiatives your plan depends on most, and you'll see them compared on one basis.




Sources


 
 
 

Comments


iStock-1250152599.jpg

Stay In The Know

Sign up with your email address to receive news and updates.

Thanks for submitting!

bottom of page