If Everything Is Working, Don't Assume It's Stable
Wired for More | Strategic Leadership Series | March 2026
Stability Series - Part 1 of 1
Functioning and stability are not the same thing. The difference matters most when nothing looks wrong.
———————————————————————————————————————
In healthcare systems, stability is most often inferred from performance. Targets are being met. Decisions are being made. Clinics are running. Meetings are occurring. The metrics are acceptable. From the outside, the system appears intact, and the natural conclusion is that it is holding.
That conclusion is frequently wrong, and the cost of getting it wrong is that the window for light intervention closes while the organization is still reading the situation as fine. The system that looks stable from the performance layer can be quietly contracting at the capacity layer, and the two do not become visibly aligned until the contraction has been running long enough to produce the kinds of events that finally make the gap impossible to ignore.
———
A system that is functioning is not necessarily a system that is stable. Functioning is output. Stability is the range that makes durable output possible. They are not the same measure.
———
What contraction looks like before performance declines
The early indicators of a contracting system are not dramatic. Conversations require slightly more effort than they used to. Ambiguity feels less tolerable at the margins. Dialogue between leaders shortens incrementally. The threshold for disagreement lowers in ways that are individually small and collectively significant. None of these shifts triggers intervention. They are read as normal consequences of a demanding environment, which in high-accountability healthcare systems means they are read as expected and therefore not worth naming.
Under sustained pressure, the nervous system adapts by shifting toward risk detection and certainty-seeking. The range that makes leadership effective, the cognitive range to hold complexity without collapsing into rigidity, the relational range to tolerate disagreement without escalation, the emotional range to remain steady without over-controlling, contracts before any performance measure moves. Leaders still decide. Teams still deliver. Projects still move forward. What shifts is the internal effort required to maintain that functioning. More explanation. More checking. More vigilance. The work gets done, but it costs more than it should, and that additional cost is invisible in every metric the organization is watching.
———
Fragility does not look like collapse. It looks like reduced tolerance for uncertainty, a lower threshold for disagreement, and a growing reliance on control where flexibility used to be sufficient.
———
Why the gap between functioning and stability matters
The gap between a system that is functioning and a system that is stable is most consequential at the point of disruption. A stable system can absorb unexpected load, navigate conflict, and recover from error without those events becoming destabilizing. A system that is functioning but fragile has no such buffer. The unexpected load that a stable system would process as a challenging period becomes, for a fragile system, the event that finally makes the underlying contraction visible.
The disruption gets treated as the problem. The months of narrowing range that preceded it, the real problem, does not get named because it was never visible in the data the organization was watching. The intervention addresses the disruption. The conditions that made the system fragile remain intact. The next disruption finds the system in the same position, or worse.
The case for naming the phase accurately
The most practically useful thing a CMO or medical director can do when a team or department appears to be functioning well is to ask whether functioning is actually the right measure. Are conversations getting shorter? Is the tolerance for ambiguity holding or narrowing? Are the leaders in the system asking genuine questions or managing exchanges toward predetermined conclusions? Is the team producing results because they have range, or because they are pushing through contraction?
These questions do not require a crisis to be worth asking. They require only the recognition that operating successfully and stabilizing sustainably are different things, and that the gap between them is where the most preventable organizational costs accumulate. The earlier the contraction is recognized, the lighter the recalibration required. Stability is not the absence of visible dysfunction. It is the presence of range. If that distinction feels relevant in your environment right now, it is worth acting on before the metrics confirm it.
———————————————————————————————————————
The system that looks fine and is quietly narrowing is not a stable system. It is a functioning system that has not yet produced the event that will make its fragility undeniable.
———————————————————————————————————————
meriotleadership.com/wired-for-more
———————————————————————————————————————
Wired for More | Meriot Leadership Institute
Stability Series | Part 1 of 1 | March 2026
