What change management is for
Change management is the discipline of moving people through a change — readiness, communication, training, reinforcement. Done well, it lifts adoption and reduces resistance. It is necessary work, and ETEGY treats it as such.
But its unit of measure is the person, not the model. It answers "did people take up the new way?" — not "did the operating model actually change, and can we prove it?"
What change management reliably produces
The discipline works — on the thing it measures. Capgemini's study puts numbers on it.
higher change success when an organization brings real data maturity to the effort — evidence that most change is still run on instinct, not measurement.
not enough
Accenture's read: the people side of change is "often the missing ingredient" — essential, yet on its own it does not deliver the business outcome.
The lift is real. But notice what it measures: the success of the change effort, read as adoption — not whether the system that produces value was structurally different afterward.
Adoption is not structural change
This is the quiet substitution at the center of most programs: adoption metrics stand in for transformation. People logged in, completed training, followed the new steps — so the transformation is declared done.
Capgemini notes the discipline is so often reduced that it is "frequently confused with internal employee communication." Whether people complied is a fact about people. Whether the model changed is a fact about the work — and only the second is transformation.
Where the gap shows — point by point
None of these mean change management failed. They mean it was asked to prove something it was never built to measure:
- Measured by activity, not outcomeAttendance and logins stand in for whether the model changedActivity
- Confused with communicationReduced to messaging the change rather than changing the workCapgemini
- Adoption without redesignNew tools taken up while the underlying process is untouchedStructure
- Sustained only under oversightBehaviors revert the moment attention moves onReversion
- No trace to a governed resultAdoption can't show the reported outcome came from the changeProof
How ETEGY reads it
Change management is necessary, not sufficient. We keep it — and add the thing it was never built to provide: proof that the operating model itself changed, traced to the work that produced the result.
Adoption gets people to a new model; we make sure there is a new model — a Zero-Based read of the actual state, structured across the GSDPI lifecycle, with its change held to a provable standard. Not compliance. Structural change you can defend. See the ZBT Discovery →