The Stewardship Gap

Recognizing the breakpoints
is not enough.

The diagnosis was complete in most stalled transformations.

What was missing is what is missing in most stalled transformations: no one whose job it was to act on it. The stewardship gap is 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.

The gap defined.

"The space between knowing what the transformation needs and having someone whose explicit job it is to keep that work alive."

Each of the four forces requires a stewardship function — a specific kind of ongoing work, owned by someone with the authority to do it. Most transformations launch with all four forces intact. They fail because no one is responsible for sustaining them when operating pressure arrives.

Purpose is not
a values statement.

It is a specific, measurable definition of what success looks like that every team at every level would describe the same way.

The cloud migration case: launched to improve deployment speed. Infrastructure heard "reduce ticket time." Security heard "maintain compliance." Applications heard "get off legacy hardware." One year later: deployment speed unchanged.

Commitment is the designed priority
that holds when tradeoffs appear.

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.

The insurance case: AI-driven claims triage launched with C-suite mandate. Months later, adjusters still running dual processes. No one had told them the manual process was no longer required. They were still being measured on claim accuracy. The AI worked. The commitment had not been designed.

Capability is not competence,
talent, or tooling.

It is the organizational machinery: how work moves, where decisions get made, how exceptions get handled.

The CRM case: new platform aligned to connect departments. Six months after launch, handoff failures had not declined. Each department still managed its own queue independently. The platform could show the information. The process for acting on it did not exist. Nobody owned the space between departments.

Momentum dies when organizations
confuse activity with movement.

It dies when the people responsible for reinforcing it are pulled to other priorities and no one is watching for drift.

The manufacturing case: operational redesign with strong early momentum. At 90-day mark, the champion was pulled to other work. Teams quietly reverted — not through resistance, but because nothing in the environment was reinforcing the change. By formal assessment: old model had reclaimed the ground.

Stewardship roles are
structurally underrewarded.

Launches come with fanfare, executive visibility, and credit. The steward inherits the work that follows.

Measured against outcomes that take years to surface — while the leader who declared victory at launch has frequently moved on. This is not a character problem. It is a structural one. The system rewards launches over sustainment. Paper 3 takes this on directly.

Four self-check questions.

The gap in the data.

Bain Live the Model: only 1 in 3 feel personally motivated to adopt the new operating structure. The gap between expectation and execution is where stewardship lives — or doesn't.

A launch is an event.
A build is something else.

There is a structural difference between launching a transformation and building one.

A launch is an event that happens once. A build is a set of designed conditions that someone must maintain, with named owners and the authority to act when conditions begin to weaken. Most transformation programs are designed as launches. They are measured as builds.

The 90-day test.

"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 not — you have launched one. Not built one.

Most transformations launch
with all four forces intact.

They fail because no one is responsible for sustaining them when operating pressure arrives.

Naming a steward is necessary. It is not sufficient. Stewardship without structural support produces the DevOps pattern: responsibility for the gap, authority over neither side. Paper 3 develops what structural support actually looks like.