Where are you in your SAP journey?
SAP Activate phases shown above each zone for reference
Discover · Prepare
01
Considering
Why this transformation, why now, and why this scope?
Is this transformation redesigning the operating model, or preserving it?
What operating model implications have not yet been surfaced?
Explore
02
Planning
Which decisions being taken now will be hardest to unwind later?
Where is operational modernization being quietly traded for delivery certainty?
What is being assumed about organizational readiness?
Realize · Deploy
03
Building
Does what is being reported match what is happening on the ground?
Where is pressure accumulating that has not yet been escalated?
Which decisions are being walked back without being formally re-cut?
Run
04
Running
Is the program still doing what it was meant to do?
What operational debt is being absorbed silently?
Where is the organization carrying the cost of decisions made under pressure?
The cost of correction is rarely highest at the moment a problem becomes visible.
It is highest at the moment a problem could have been surfaced and was not. Programs do not fail at go-live; they fail months earlier, when uncomfortable observations stay inside the delivery line because the structure of delivery does not reward escalation.
The point of this question is not to score a transformation. It is to compress the gap between when the program drifts and when the drift is named. That gap, more than any methodology choice, determines whether the cost of correction is small enough to absorb or large enough to reshape the program.
Different stages surface different patterns. The questions worth asking in Considering are not the questions worth asking in Building. The instrument is calibrated to the state.
A deeper read on each zone.
For each of the four zones, what the questions are designed to surface and why this stage of the lifecycle deserves an independent read rather than a delivery-line read.
01
Considering
What this zone surfaces.
The Considering zone is where the highest-leverage decisions of the entire transformation are made. Not the technical ones, the structural ones. What is this transformation actually for? What outcomes is it being asked to deliver? What operating-model implications have not yet been thought through?
The leverage point is here. The cost of getting this right is the lowest it will ever be.
02
Planning
What this zone surfaces.
Planning is where the integrator’s view of the program meets the organization’s view of itself. They are rarely the same view. The integrator sees a delivery sequence. The organization sees an operating change. Both are right. Neither is complete.
The questions worth asking here are about asymmetry — where do the two views diverge, and what is the cost of pretending they don’t? The answer almost always involves organizational readiness, which is the dimension most consistently underestimated at this stage.
03
Building
What this zone surfaces.
Building is where the gap between reporting and reality opens. Not because anyone is hiding anything — because the structure of delivery rewards stable reporting and penalizes uncomfortable escalation. Programs do not lie. Programs absorb pressure quietly until they cannot.
04
Running
What this zone surfaces.
Operational debt absorbed silently here will surface later, often as a request to budget another transformation. That request is usually evidence that the first one was not finished. The independent read here is what tells the board whether the work is actually done.
If a deeper read would be useful.
- Document version
Get the full PDF read.
- Conversation