top of page
  • LinkedIn
  • Youtube

The End of Centralized Consensus

  • Jan 25
  • 3 min read

Updated: Jan 25

    Executive meeting view of a healthcare operations dashboard with site-by-site variances highlighted

The boardroom is quiet in the way it gets when the dashboard looks clean but the room feels uneasy. Someone scrolls past a list of “minor” workflow exceptions, each one tagged with a different site name, each one carrying the same polite comment: “Handled locally.”


What is quietly changing


We are entering a period where centralized consensus is thinning out. The United States has formally completed its withdrawal from the World Health Organization, which is not just a funding story, but a signal that shared protocols and shared data ties can be severed at the top. At the same time, provinces like Alberta are redesigning governance away from one centralized structure toward pillar or sector-based agencies and more localized leadership models.


In a world like this, healthcare organizations do what humans always do when the centre weakens. They localize decisions. They improvise. They create workarounds that feel practical in the moment and become expensive in aggregate.


This is the pattern in multi-site performance right now: not instability, but drift. Not chaos, but quiet divergence. It shows up as small differences in appointment types, intake logic, documentation conventions, billing cues, and escalation pathways. Each difference looks rational inside its own hallway. Together, they fracture the organization’s ability to know what is true.



Infographic showing multi-site drift: variance in operating definitions leads to data inconsistency, hidden revenue leakage, and uneven care


The wrong culprit keeps getting blamed


Leadership teams keep blaming the usual suspects.


They call it training. They call it accountability. They call it resistance. They call it “culture.” The story becomes personal because personal stories are easy to tell in a meeting, and because the alternative, admitting that the system itself is producing variance, threatens the myth of control.


In that framing, the problem is a set of people who need more reminders, more oversight, more motivation. The answer becomes louder leadership and more activity.


The real limiter is governance, not effort


The structural constraint is governance, specifically the governance of operating logic and information integrity.


Most multi-site organizations are not suffering from a lack of effort. They are suffering from the absence of a shared spine: a single operating taxonomy that makes work comparable, a shared definition of what “done” means, and a credible mechanism that keeps local optimization from eroding enterprise coherence.


This is why interoperability conversations keep circling back to governance rather than purely technical upgrades. The Canadian Digital Health Interoperability Task Force separates technical factors from human-factor interoperability, describing the system-level relationships and governance conditions that determine whether harmonized data can actually be adopted. Federal health-data work reinforces the same point: progress stalls when policy and governance lag behind the tools.


When the centre weakens, the temptation is to let each site “do what works.” But “what works” often means what reduces friction today, not what preserves integrity tomorrow.


Integrity is not a moral word here. It is an operational one.


Without information integrity, you cannot reliably see revenue leakage because leakage hides inside inconsistent documentation patterns. Without a shared taxonomy, you cannot compare access, demand, and capacity because each site is counting different realities. Without standard operating logic, you cannot govern risk because the organization cannot prove that it behaves consistently under pressure.


Governance drift rarely announces itself. It accumulates.


Where attention should go next


If you accept the diagnosis, attention shifts away from volume and motivation and toward three colder, more decisive questions.


Where is variance permitted, and where is it prohibited. Not as a values statement, but as a governance choice. A multi-site enterprise cannot be “locally flexible” everywhere. The question is not whether sites should adapt, but whether adaptation is happening in places where comparability and safety depend on sameness.


What is the organization’s source of truth. If two sites document the same clinical moment differently, the organization does not have two styles. It has two realities. And a leadership team cannot govern two realities without eventually choosing one by accident.


What incentives are silently shaping behaviour. Variance often persists because it is rewarded, or at least not penalized. The path of least resistance becomes the path of least governance. Over time, the organization trains itself to accept exceptions as a form of competence.


This is not a how-to. It is a boundary line between diagnosis and action. The leverage is upstream. The performance ceiling is set by governance long before it is set by effort.


In the old world, leaders could wait for a global authority, a national strategy, or a provincial centre to standardize the ground beneath them. That assumption is becoming less safe. The macro system is fragmenting, and the cost lands locally.


Lastly


When the centre stops holding, performance belongs to whoever governs the definitions.


 
 
 

Comments


Diagnostic Closure

This pattern is rarely dramatic.

It is persistent.

And it is expensive when left unexamined.

For readers looking to understand the broader diagnostic frame behind this perspective, see The Diagnostic Lens.

bottom of page