The Stewardship Gap
Why transformations keep losing force after leaders have already named the problem
A senior leader at a healthcare firm had done the hard work. He had diagnosed the transformation clearly, named the failure pattern and traced where the original purpose had fragmented between the executive vision and the vice presidents tasked with delivering it. He brought it to the steering committee. They agreed. They cited it in the next quarterly review.
Six months later, the breakpoint was still there. Slightly worse, now with documentation.
Most transformation failures are not mysteries. The leaders involved usually know something is wrong. They can name it. They discuss it in reviews. And then the same pattern appears in the next update, slightly worse, with more documentation.
The first piece in this series was about recognizing those breakpoints. This piece is about why recognizing them often does not change them.
The diagnosis was complete in the healthcare case. There was no one whose job it was to act on it. The executive sponsor owned the program. The vice presidents owned their functions. No one owned the gap.
Call this the stewardship gap: the space between knowing what the transformation needs and having someone whose explicit job it is to keep that work alive once the launch energy is gone.
In “The Five Breakpoints,” I described five predictable failure patterns that show up across large-scale change: strategic disconnection, incentive fragmentation, process friction, technology illusion and momentum mirage. Underneath those patterns are four conditions on which transformation success depends: Purpose, Commitment, Capability and Momentum. Most transformations launch with all four intact, at least on paper. They fail because no one is responsible for sustaining them once the original energy fades and the operating pressure arrives.
Closing the stewardship gap is the difference between transformations that move and transformations that report progress while losing force.
Four Forces, Four Stewardship Functions
The Four Forces are not steps in a change model. They are simultaneous conditions that must be present and maintained throughout a transformation.
Purpose is the shared definition of what success looks like. Commitment is the fuel that keeps the work prioritized when tradeoffs appear. Capability is the organizational machinery that allows it to actually move. Momentum is the velocity that sustains progress after launch.
When all four are active, transformation moves. When any one weakens, you get a breakpoint. Most transformations have all four at kickoff. The question is who maintains them when the organization gets busy, when competing priorities show up and when the original energy dissipates.
Forces do not sustain themselves. Each needs a stewardship function with a named owner.
Purpose is not announcement. Commitment is not endorsement. Capability is not talent or tooling. Momentum is not activity. Most leaders understand the forces intuitively. Few design the stewardship for those forces before the pressure arrives.
Purpose, Carried by Interpretation
An organization launched a cloud migration with a stated goal of improving deployment speed. The infrastructure team heard “reduce ticket resolution time.” The security team heard “maintain compliance posture.” The application teams heard “get off legacy hardware.” All three were defensible readings of what had been announced. None of them were the same outcome.
A year later, the migration had produced new infrastructure, a new compliance framework and faster hardware. Deployment speed had not changed.
Purpose, in the context of transformation, is not a values statement or a strategic direction. It is a specific, measurable definition of what success looks like that every team, at every level, would describe the same way if asked. The bar of getting that level of agreement across an entire organization is harder to clear than most leadership teams expect.
McKinsey’s State of Organizations 2026 report, drawing on more than 10,000 senior leaders across 16 countries, found that 56 percent of C-suite executives reported clarity on their organization’s strategic priorities. At middle management, that number dropped to 27 percent. A 29-point collapse across a single organizational layer.
What looks like a communication failure is more accurately a structural feature of how information moves through layered organizations. Strategy does not simply cascade. It gets retold, and each retelling changes it. Frederick Bartlett’s serial reproduction research from 1932 showed that information passed through a chain of people degrades predictably at each handoff. Three layers between an executive team and execution means strategy is effectively retold three times before it becomes action.
The stewardship function for Purpose is interpretation. That is different from announcement and from documentation.
Interpretation is the ongoing work of translating enterprise outcomes into team-level definitions of what success looks like this quarter, in this workflow, for this team. Done well, it produces the difference between a strategy people have heard about and a strategy people are actually working from.
Someone in your organization must own that work continuously. They must surface divergence early, when it can still be corrected, rather than discovering at a quarterly review that three teams have been optimizing for different outcomes. They must maintain coherence when conditions change and update the definition of success before teams are left guessing.
In the cloud migration case, the executive team treated the announcement as the work. The interpretation was left to each function. Three functions interpreted three different outcomes. There was no stewardship of the meaning. The result was three reasonable answers to three different implicit questions, none of which was the question the transformation had set out to answer.
Self-check: Who in your organization is actively maintaining the definition of success, not just announcing it?
Commitment, Carried by Ownership
An insurance company launched an AI-driven claims triage initiative with a clear mandate from the C-suite. Months later, the adjusters were still running dual processes: the AI model’s output alongside the manual review that had always existed.
When asked why, the answer was consistent across the team. No one had told them the manual process was no longer required and they were still being measured on claim accuracy.
The AI worked. The commitment had not been designed.
Commitment is the fuel of transformation. It shows up in budgets, in calendar time and most revealingly, in incentive structures. You can read an organization’s real commitments by looking at where money and time actually go under pressure, not at what was promised in the kickoff deck.
Commitment is not endorsement. It is the designed priority that holds when tradeoffs appear.
That distinction matters because commitment erodes. That is not cynicism. It is how organizations work under pressure. Competing priorities surface. Quarterly numbers create gravity. Leaders who fully intended to prioritize the transformation find that the incentive structures surrounding them make other choices more rational. Most organizations never explicitly design what commitment is supposed to look like once it becomes hard to maintain.
KPMG’s Adaptability Index, published April 2026 and based on surveys of more than 300 C-suite leaders, found that 81 percent of executives said boards had raised expectations for organizational adaptability, but only 30 percent said their organization could actually reconfigure structures, roles and processes quickly. Bain’s Live the Model survey of nearly 1,000 respondents found that only one in three felt personally motivated to adopt the new operating structure their organization was asking them to embrace.
The gap between expectation and capacity to act is the visible signature of weak commitment. Most boards mistake it for a strategy problem because the strategy is the easier thing to revisit.
The stewardship function for Commitment is ownership. That means named decision rights, designated accountability that cannot be reassigned to a working group, and an explicit check before the work launches on whether the incentive structures facing every leader with veto power over the transformation actually make prioritizing it rational. If they do not, that problem needs to be addressed before the announcement, not after.
In the insurance case, the C-suite read the announcement as the commitment. It was not. The measurement criteria the adjusters were judged on still rewarded the manual process they had always run and no one had explicitly retired that process. Both pieces of design work were skipped, so the organization absorbed the new tool into the old habits. The AI sat next to the manual review for months because the system gave the adjusters no reason to stop running both.
Self-check: For every team whose behavior has to change, do their measurement criteria reward the new state and has the old way been explicitly retired?
Capability, Carried by Architecture
A technology company invested in a new customer relationship management platform designed to align and accelerate handoffs between departments. The platform was well designed. The training was thorough.
Six months after launch, handoff failures had not declined.
The reason was not the technology. Each department still managed its own queue independently, with no shared view of which customers were transitioning between teams. The platform could show the information. The process for acting on it did not exist. Nobody owned the space between departments.
Organizations consistently overestimate their capability for transformation by looking at talent. They assess whether they have skilled people. They often do. But skilled people inside broken handoffs still produce slow, fragmented results. The bottleneck is rarely the person and almost always the structure they are working inside.
Capability is not about individual competence. It is the organizational machinery: how work moves, where decisions get made, how exceptions get handled and whether teams can coordinate across boundaries without losing time or creating conflict. These are the structural factors that determine whether good people can execute efficiently or whether they spend their energy navigating workarounds they have built to survive a process that no longer fits how the work actually flows.
McKinsey’s 2026 report found that 38 percent of respondents cited rigid structures as the primary barrier to transformation. That rigidity does not show up as a single dramatic failure. It shows up in handoffs that stall, decisions that escalate unnecessarily and processes that were designed for a different set of requirements but never redesigned. The workaround becomes the operating model. The official process becomes theater.
The stewardship function for Capability is architecture: designing how work flows across boundaries, where decisions live, how exceptions get handled and who owns the space between functions where most failures actually occur. Architecture is the work of identifying and removing the friction that forces skilled people to build workarounds inside their own organization.
In the technology company case, the platform was capable. The architecture was not. Who owns the customer as they move between departments? Who has authority to act on the shared view? What happens when a handoff fails? None of that had been designed. The result was a capable tool inside an incapable system.
Capability produces two of the five breakpoints. Process friction shows up when work cannot move through the system. Technology illusion shows up when leaders buy a tool and mistake it for the system. Both reveal the same missing stewardship: no one owns the architecture of how work actually moves.
Self-check: If you mapped how work actually flows today, would it look like the formal process or the workarounds your teams built to survive it?
Momentum, Carried by Reinforcement
A manufacturing firm launched an operational redesign with strong early momentum. New workflows were piloted. Early adopters were vocal supporters. The first 60 days showed real movement.
At the 90-day mark, the leader who had championed the change was pulled into other work. The redesign continued running on the original plan. But without someone actively watching for drift, teams had quietly reverted to the old process. They had not made a formal decision to revert. The new process had simply become more effort than the old one and nothing in the environment was reinforcing the change.
By the time the company ran a formal assessment, the old model had reclaimed the ground.
Momentum is the velocity that sustains transformation after the launch energy fades. It grows through early wins, visible progress and consistent reinforcement. It dies when organizations confuse activity with movement.
Momentum is not enthusiasm. It is not a kickoff. It is not the fact that people are still attending the meeting. Momentum is the organization’s ability to convert progress into confidence and confidence into continued action.
The launch is the event that gets celebrated. The leaders who drove it get recognized. Then the real work begins: the unglamorous, sustained effort of changing how an organization actually operates. And the reward structures largely go silent. Organizations are better designed to celebrate starting than to sustain finishing.
KPMG’s data makes this concrete. Only 9 percent of executives identified increased psychological safety as a key behavior change in their transformation. Only 24 percent made dynamic talent deployment a key change. These are not peripheral concerns. They are the conditions that allow people to raise problems early, shift resources to where they are actually needed and keep the work moving after the launch energy fades. When they are absent, the organization keeps reporting progress while momentum quietly bleeds.
The stewardship function for Momentum is reinforcement: a named person, distinct from the executive sponsor, who watches for drift, maintains short feedback loops and has the authority to intervene before a slide becomes a stall. This person does not just measure progress. They diagnose the difference between progress and performance, between teams that are actually moving and teams that are reporting activity to satisfy a stakeholder expectation. Without that distinction, a transformation can run for months producing convincing status updates while the underlying momentum is gone.
In the manufacturing case, the leader who left was the sponsor. There was no separate steward of the change. The activity continued because no one was responsible for the energy. By the time anyone looked, teams had quietly opted out, not through resistance, but through the absence of anyone making it harder to revert than to continue.
Self-check: Who in your organization is responsible for telling the difference between progress and performance on this transformation and what authority do they have to act on it?
Why Stewardship Is Hard to Staff
Naming the work is necessary. It is not sufficient.
Anyone who has worked inside a large organization will recognize a problem with the recommendation to name stewards for each of the four forces. Stewardship roles are structurally underrewarded.
Launches come with fanfare, executive visibility and credit. The steward inherits the work that follows, often including pieces of the launch that were never finished, and is measured against outcomes that take years to surface. The leader who declared victory at the launch has frequently moved on by the time the consequences arrive.
This is not a problem the steward can solve through better personal positioning. It is a design problem at the level of how the organization structures recognition, accountability and tenure.
There are partial moves that help, even inside an unchanged system. Before launching the transformation, name the stewards for each of the four forces. Modify their performance objectives so they are measured on sustained outcomes: adoption rates at twelve and twenty-four months, durable behavioral change and structural integration into how the organization actually works, not just launch milestones. Make the role visible enough at announcement that taking it carries real career upside, not just career risk. Pair launch sponsors with named stewards in formal communications, so the organization sees the two roles as equally consequential.
Naming stewards does not have to mean assigning four separate people. It means assigning four explicit functions. Interpretation and Reinforcement can often sit with one steward, since both involve maintaining coherence and surfacing drift. Ownership usually requires C-suite authority because it touches incentives, decision rights and executive tradeoffs. Architecture often belongs with the COO or with a designated operating model owner because it concerns how work actually moves across the organization.
No single existing enterprise role today does all four functions well. Chiefs of Staff often handle Interpretation informally but without the authority to make it stick. Chief Transformation Officers hold Ownership on paper but often with weak political backing. COOs sometimes do Architecture, depending on the company. Program Management Offices usually monitor Reinforcement-style indicators but lack the standing to intervene when drift appears.
The recommendation here is not to hire a new role by default. It is to assign the four functions explicitly, map them onto the existing leadership structure and give each function the political backing it requires.
None of this resolves the deeper structural problem. The system that rewards launches over sustainment will keep producing the dynamic at scale. But these moves raise the floor. They make stewardship visible enough to staff and concrete enough to measure, even before broader structural changes get made.
That raises the harder question for the next piece: if stewardship matters this much, why do organizations keep failing to support it?
The Difference Between Launching and Building
The Four Forces are shaping conditions in your transformation whether you are actively managing them or not. At any given moment, Purpose is drifting or being maintained. Commitment is eroding or being reinforced. Capability is calcifying or being redesigned. Momentum is building or bleeding.
None of those is static. Each moves in the direction the people responsible for it are pushing, including the direction of nobody pushing at all.
Most transformation leaders address these conditions reactively, after a breakpoint has appeared. The ones who build transformations that hold address them before launch. They name the stewardship functions explicitly, assign real ownership rather than implied ownership and build monitoring into the operating rhythm before the early energy fades.
A launch is an event that happens once. A build is a set of designed conditions that someone has to maintain, with named owners and the authority to act when those conditions begin to weaken.
The healthcare leader from the opening of this piece had the diagnosis. What he was missing was an owner for the function the diagnosis pointed to. The work of interpretation, the ongoing translation of strategic clarity across organizational layers, had no name attached to it, so it never happened. The forces were there at launch. The stewardship was not. That is the gap worth closing.
For each of your four forces, name the person whose job it is to maintain it. If the only name you can produce is the executive sponsor, you do not yet have a steward. The sponsor’s job is to launch, fund and unblock. The steward’s job is to keep the condition alive when no one else is watching. Conflating the two roles is what produces the breakpoint pattern that most transformations eventually report on and few ever recover from.
The harder version of the question, and the one most worth sitting with, is this: what would happen if you stopped actively managing this transformation for 90 days?
If the honest answer is that the work would keep moving without you, you have built stewardship into how the organization operates. If the honest answer is that the work would drift into status reports and lose force, you have not built a transformation yet. You have launched one.
Citations
McKinsey & Company, The State of Organizations 2026. Survey of 10,018 senior leaders across 16 countries, June to September 2025; published February 19, 2026. Statistics cited: 56 percent C-suite / 27 percent middle management strategic clarity; 38 percent of respondents identifying rigid structures as the primary barrier to transformation.
Bain & Company, Live the Model survey. 976 respondents across nine countries, September to October 2025. Statistic cited: only one in three respondents felt personally motivated to adopt the new operating structure.
KPMG, Adaptability Index 2026. Surveys of more than 300 C-suite leaders, published April 15, 2026. Statistics cited: 81 percent of executives say boards have raised expectations for adaptability; 30 percent say their organization can reconfigure quickly; 9 percent identified psychological safety as a key behavior change; 24 percent made dynamic talent deployment a key change.
Bartlett, F. C. Remembering: A Study in Experimental and Social Psychology. Cambridge University Press, 1932. Serial reproduction research demonstrating predictable degradation of information passed through chains of transmission.