The diagnosis is usually right
In most failed programs, the analysis was correct and the solution reasonable. What was missing was everything else: leadership that modeled the behavior, the organization's absorption capacity, and a mechanism to sustain the change once the project team left.
What sets the successful ones apart
The public evidence converges on a few factors, and all of them are about execution, not design.
- Visible, specific commitments from senior leadership, not speeches
- A limited number of simultaneous initiatives per area
- Named owners with consequences for every behavior change
- Measurement of real adoption, not training attendance
Change capacity is a finite resource
The same area can't absorb five transformations at once. Mapping change load by area and sequencing it in waves is as important a design decision as the content of the program itself.
Key takeaways
- The cause of failure is usually adoption, not design.
- Each area's absorption capacity limits how many changes can coexist.
- Without an owner and a consequence, the new behavior doesn't stick.
NS frameworks and reference sources
- Proprietary NS framework · AE·NS — methodological notes from the Culture and Change practice
- NS project base: anonymized cases by sector and geography
- Open market evidence and academic literature, recalibrated with client data
- McKinsey — 'Why do most transformations fail?' (success rate ~30%)
- Kotter (1996) — Leading Change
- Prosci — Best Practices in Change Management
This article develops proprietary NS Business Strategy frameworks, drawing on our project base and on public industry literature and studies cited above. Figures are reference ranges; each project is measured against the client's actual data.