PROVE · E · EVALUATE THE OUTCOME
The post-implementation review your organization keeps skipping
A post-implementation review compares what a project promised with what it delivered. A 45-minute format, the questions to ask, and how to keep it up.
The post-implementation review is in almost every project methodology, and it is skipped in almost every organization. By the time it's due, the team has moved on, the sponsor is focused on the next priority, and the review feels like paperwork for a project that's already "done."
That's a costly habit. The post-implementation review is the only point where an organization learns whether its investment decisions were good. Skip it, and every estimate, every business case and every prioritization decision stays uncalibrated.
What a post-implementation review is, and isn't
A post-implementation review (PIR) compares the outcome of an investment with what was intended. It happens after release, once there's enough time for results to appear.
It is not:
- A sprint retrospective. Retros look at how the team worked. A PIR looks at whether the investment worked.
- A closure report. Closure confirms deliverables. A PIR examines results.
- A blame session. If people fear the review, they'll avoid it or sanitize it.
When to hold it
Hold the main review 90 to 180 days after release for most initiatives. Earlier, and benefits haven't had time to appear. Later, and memories fade and other changes muddy the picture. For large programs, add a short adoption check at 30 to 60 days. See Benefits realization.
The most important step is scheduling the review when the investment is approved. A review scheduled at approval tends to happen. One left until "after go-live" rarely does.
A 45-minute format
Attendees: the business owner, the product or project lead, a representative of users, and whoever facilitates the portfolio.
- Restate the intent (5 minutes). Read the original problem, objective and target out loud. Many teams are surprised by what they originally committed to.
- Review the evidence (15 minutes). Outcome measures against baseline and target; adoption; actual cost against estimate.
- Explain the gaps (15 minutes). For each significant gap, positive or negative, ask why.
- Decide and record (10 minutes). What happens next for this investment, and what should change for future ones?
The questions that matter
About the outcome
- Did the primary measure move? By how much against the target?
- Are people actually using what was delivered?
- What happened that we didn't expect?
About the decision
- Knowing what we know now, would we approve this investment again?
- Were the assumptions behind the decision correct? Which ones weren't?
- Was the estimate of cost and effort accurate?
About the future
- Is there follow-up work needed to realize the benefit, such as training, process change or a small fix?
- What should we do differently when assessing similar requests?
The second group is the one most often skipped, and it's the most valuable. It is how prioritization gets better over time. See Closing the loop.
Possible outcomes of the review
| Finding | Typical response |
|---|---|
| Target met or exceeded | Record it; note what made it work |
| Partly met, adoption is the issue | Fund adoption work, such as training or workflow changes |
| Partly met, solution is the issue | Consider a targeted improvement or accept the result |
| Not met, estimate was unrealistic | Recalibrate estimates for similar work |
| Not met, conditions changed | Record the change; reset or retire the target |
Making it a habit
- Schedule it at approval. Put the date in the decision record.
- Keep it short. 45 minutes and a one-page summary. A heavy process won't survive.
- Make it safe. Leaders should thank teams for honest bad news. The aim is learning, not grading.
- Report on review completion. Track how many completed investments had a review. What gets counted gets done.
- Share the lessons. A short quarterly summary of what reviews revealed is valuable for everyone who writes business cases.
How Aizu helps
In Aizu, the original intent, owner, decision rationale and assumptions stay with the initiative, so a review starts from the record instead of from memory. Outcome targets and measurements recorded after release show the trend, and the activity log shows what changed along the way. The review's findings can be recorded on the same initiative, where the next decision about similar work can see them. Related: Tracking project performance beyond on-time and on-budget.
Frequently asked questions
What is the difference between a post-implementation review and a lessons-learned session?
A lessons-learned session usually focuses on how the project was run. A post-implementation review focuses on whether the investment achieved its intended outcome, and what that means for future decisions.
Who should lead a post-implementation review?
A neutral facilitator, often from the PMO or portfolio office, with the business owner presenting the outcome evidence. The facilitator keeps the review focused on learning.
Should every project have a post-implementation review?
Every medium or large investment should. For small changes, a brief note on whether the change achieved its purpose is usually enough.