Every Transformation Leaves a System — and a Story

Project closure does not close the organizational experience

A project can close properly. Deliverables can be accepted, responsibilities handed over and open issues reduced to an agreed level. None of that guarantees that the organization will remember the transformation accurately.

Over time, people leave. Constraints change. New technology becomes possible. A decision that made sense under one set of conditions is judged later under another. If the reasons behind the decision are lost, the organization fills the gap with a simpler story.

That is why I distinguish between a Decision Log and Lessons Learned. The first preserves what was decided. The second should preserve why, what worked, what hurt and what the organization would do differently.

The story becomes part of the starting condition for the next wave

A manager who lived through a painful ERP program does not hear a new transformation message from zero. A new employee may inherit the same story without having experienced the original project at all.

I once worked with an IT director who had lived through an earlier ERP failure followed by penalties for people involved. He entered the new program with a very different starting point from a new key user: technology transformation meant personal risk. The sponsor could deliver the same message to both and they would hear different things. History had already edited the message before it reached him.

The story may be fair. It may be incomplete. It may even be wrong. What matters is that it shapes trust, perceived risk and willingness to invest effort in the next change.

Every transformation therefore creates two assets: the system that remains and the narrative that remains around it.

Do not confuse fatigue with resistance

After a difficult phase, management may see integration, new data and business value. The people who carried the phase may remember weekends, rescue mode, defects, role changes and constant escalation.

When they say 'not now' to the next wave, that may be resistance. It may also be exhaustion.

Prosci describes change saturation as a condition in which the volume of change exceeds the organization's capacity to adopt and use it. In its 12th Edition Best Practices research (2023), Prosci reported that about 80% of respondents were near, at or past the point of saturation. I would not use that as a universal market statistic for every company, but it is a useful warning against treating capacity as infinite. Prosci's current web guidance reports a different figure for its most recent research, which is why I keep the edition visible rather than presenting 80% as a timeless benchmark.

Change-fatigue research outside enterprise technology points in the same direction. Beaulieu, Seneviratne and Nowell's integrative review, published online in 2022 and in the Journal of Advanced Nursing in 2023, included 26 publications and grouped the literature around definitions, preceding factors, associated behaviors, consequences and mitigation strategies. The sector is different, so I do not transfer the findings mechanically to ERP. The broader lesson is simply that cumulative change has a human capacity dimension.

Readiness for the next wave is not a mood

I do not look for a single readiness score. I look for operating evidence.

• How many major changes are hitting the same groups at the same time?
• Are key people still in rescue mode from the previous wave?
• Did the business see enough value to justify another round of disruption?
• Has support moved from project dependency to a stable operating model?
• Do people trust that lessons from the previous phase were actually used?
• Is the next scope smaller, better sequenced or better resourced where the previous phase overloaded the organization?

Sometimes the right answer is to proceed. Sometimes it is to pause, reduce scope or add capacity. 'Not now' is not always 'we do not want to change.'

The value side of that decision — whether the previous wave produced enough business evidence to justify more disruption — is developed in Value Realization Is a Management System, Not a Benefits Slide.

Preserve the why, not only the what

Decision logs become more valuable with time, not less. Future leaders need to know what constraints existed, what alternatives were considered, what assumptions were made and which assumptions later proved wrong.

This protects both sides of organizational memory. It prevents old decisions from becoming sacred simply because 'that is how we built it,' and it prevents every inherited design from being dismissed as evidence that the previous project was incompetent.

A learning organization needs enough context to challenge the past fairly.

Sustainability is an organizational capability

Sustainability as a level of success — ownership, governance, support and the new way becoming ordinary — is defined in Beyond Go-Live: Four Levels of Transformation Success. This article is concerned with the part of sustainability that lives in memory: what the organization remembers, forgets and carries into the next wave.

Key takeaway

Do not ask only what system the transformation left behind. Ask what story it left behind, who owns that story, and whether the next transformation will inherit evidence, context and trust — or only memory.