Most change programs invest heavily in getting to go-live and almost nothing in what happens after. The program team disbands. The budget closes. The sponsors move on. And the change, left without the feedback mechanisms that kept it on track during delivery, slowly drifts back towards the old way of working. This article covers two practices that prevent that drift: feedback loops that keep the organisation sensing and adapting, and post-implementation reviews that turn experience into organisational intelligence. Both are essential. Neither works without the other.
A feedback loop is not a survey. It is a system that takes input from the people living the change, converts that input into decisions, acts on those decisions, and communicates the result back to the people who provided the input. If any of those steps is missing, it is not a loop. It is a dead end. The five feedback mechanisms below, used together, give you the breadth, depth, and speed you need to sustain change after the program ends.
Click any feedback loop below to explore how it works, what good looks like, and the most common way organisations get it wrong.
The pattern is predictable. During the program, feedback flows freely because there is a team dedicated to collecting it, analysing it, and acting on it. After the program, that team dissolves and the feedback mechanisms either stop entirely or continue collecting data that nobody reviews. The solution is not to keep the program team running indefinitely. It is to transfer the feedback mechanisms to the business with clear ownership, defined rhythms, and the authority to act on what they hear.
A post-implementation review is not a project closure exercise. It is not a celebration. It is not a performance assessment of the program manager. It is a structured process for turning experience into organisational intelligence. Done well, it produces insights that make every subsequent change program better. Done badly, it produces a document that nobody reads. The difference lies in who is in the room, what questions are asked, and whether the findings lead to action.
Work through the five sections below. Each section covers a different dimension of the review, with guided prompts to structure the conversation and expandable guidance on what good answers look like. Use this as both a planning tool and a facilitation guide.
The composition of the review determines its value. Most PIRs include only the program team and the executive sponsor. This produces a review that reflects what the program intended, not what the organisation experienced. The following groups should be represented, and their absence should be treated as a risk to the quality of the review.
Timing matters. Too early and you are reviewing the implementation, not the outcomes. Too late and people have forgotten the details and moved on. The most effective approach uses a staged review cadence.
Feedback loops and post-implementation reviews are not separate practices. They are two parts of the same system. Feedback loops provide the continuous stream of intelligence that keeps the change on track day to day. Post-implementation reviews provide the structured reflection that turns that intelligence into organisational learning. Without feedback loops, the PIR has no data. Without the PIR, the feedback loops have no strategic direction. Together, they create a continuous improvement cycle that keeps change alive long after the program has ended.
Use this checklist to assess whether your post-go-live continuous improvement system is genuinely functional or just present on paper. Each item represents a condition that effective organisations meet. Gaps indicate where your change is vulnerable to regression.
0 of 12 complete
This topic is part of Sustainment, the fifth pillar of the TCA Change Model.
Explore the Full Model