The committee had met six times. The quality data was clear. The care pathway was evidence-based. The physicians in the room nodded. Six months later, nothing had changed.
Not because the initiative was wrong. Not because the physicians were resistant. Because the environment it landed in was never built to hold it.
This is the diagnosis most physician leaders never make, not about their patients, but about their organizations. They identify the problem. They design the intervention. They communicate it clearly and launch it with intention. And then they watch it fail in ways clinical training never quite prepared them for.
The issue is never the initiative. It is the environment the initiative was asked to change.
What the environment actually is
When leaders hear the term “environment,” they usually think culture, the values on the wall, the mission statement, the language in the engagement survey. These matter, but they are not the environment that determines whether change takes root.
The environment I am describing is structural. It is built from specific organizational conditions that most physician-led practices and health systems have never deliberately designed, and whose absence explains most of the change failures that get attributed to physician resistance.
Clarity. Not the strategic goal, but the operational why. When a physician is asked to adopt a new care pathway, modify a documentation workflow, or participate in a quality initiative, they are asking, whether they say it or not, why this, why now, and what problem does it actually solve for the patients in front of me? When that question doesn’t have a clear answer, one that two people in different departments would describe the same way, the initiative hasn’t launched. It has been announced. There is a difference, and the front line knows it.
Alignment. In health care organizations, the distance between a leadership decision and a front-line behavior is filled with interpretation. Every layer between the executive suite and the exam room is a potential point of drift, where a department head softens the message, a manager adds their own emphasis, or a team quietly prioritizes the workflow they already trust. Alignment is not achieved through communication alone. It is achieved through consistent follow-through at every level, and most organizations have never built the structure to produce it.
Accountability. This is where physician-led organizations lose the most ground, and where the loss is most visible to everyone except leadership. When the standard is applied to the struggling clinician but quietly set aside for the high producer, when the difficult conversation is deferred because the relationship feels too valuable to risk, every person on the team receives the same message: The standard is optional if you produce enough RVUs. That message travels faster than any communication campaign, and it costs more than any single clinician’s productivity is worth.
Visibility. Most health care organizations manage using what I think of as autopsy data, the monthly dashboard, the quarterly report, the annual patient satisfaction summary. By the time the information arrives, the moment for intervention has passed. The organizations that execute change most consistently have built something closer to vital signs: real-time awareness of what is actually happening, current enough to act on, trusted by the people doing the work. The difference between autopsy data and vital signs is not a technology problem. It is a leadership decision about what the organization will commit to seeing.
Trust. This is the condition that makes all the others possible and the one most depleted without notice. In physician organizations, trust is built through specific, observable deposits: doing what you said you would do, involving physicians before decisions are final rather than after, applying the same standard to yourself that you apply to your team. It depletes through equally specific withdrawals: a compensation structure changed without meaningful input, a schedule restructuring presented as settled rather than discussed, a commitment made during a difficult period that quietly expires when conditions improve. Those withdrawals compound in ways that do not appear on a productivity report until the departure notices begin.
The question to ask before the next initiative
Before the next quality project, the next workflow change, the next attempt to move a team in a new direction, the most valuable question a physician leader can ask is not how do I get my physicians to change? It is: Have I built the environment that makes change possible?
The physician-led organizations that execute change consistently are not the ones with the most compelling vision or the most urgent data. They are the ones where expectations are clear enough that the front line can explain them in their own words, where accountability is applied with enough consistency that people trust the standard is real, and where leadership has made enough deposits in the trust account that when something hard is asked, people believe it is worth giving.
That environment is not built during an initiative. It is built before one, in the development of operational disciplines, the daily standard holding, the honest communication that happens when nothing urgent is forcing it.
The committee can meet six more times. The data can get sharper. The pathway can be refined. Or the environment can be built once, deliberately, before the next launch.
Only one of those investments compounds.
Dave Cummings is a health care executive.




















