Stop 10 · Testing & User AcceptanceTopics · 8/8

Post-Implementation Review

In short

The launch party is over. But did the project actually fix the problem it was meant to? A post-implementation review checks the results and captures lessons, so the next project goes better.

Evaluating a delivered solution after launch — did it actually solve the original business problem, and what would you do differently — closing the loop on the full BA lifecycle from Phase 1.

The purple blob unpacks an open suitcase full of seashells and souvenirs while writing in a small notebook.

Think of it like this

After the family trip

Back from Goa, the family sits down. Did taking the train actually save money? Was the hotel worth it? What would we skip next time? Without that chat, you'd make the same mistakes on the next trip.

Watch it happen

Three months after launch: target vs actual

Queue time

Errors

Adoption

Cost

1/5The business case promised four results. Now we check each against real data.

The big ideas

What you need to know

Wait, then measure

Review after the system has settled, often a few weeks to a few months, so numbers reflect normal use.

Compare to the business case

Check each promised benefit against actual data. This closes the loop the business case opened.

Capture lessons

What went well, what didn't, what to do differently. Be specific enough that another team can use it.

Follow-up actions

Unmet goals become backlog items or new initiatives, each with an owner.

Save yourself the pain

Common mistakes

Oops

Turning the review into a blame session.

Do this instead

Focus on the process and decisions, not individuals. People share more when it's safe.

Oops

Writing lessons learned that nobody ever reads.

Do this instead

Share the top three lessons with the next project team and turn them into checklist items.

Your mission

Review something you shipped

~25 min

Quick check

What's the main purpose of a post-implementation review?

Go deeper

1Write a post-implementation review for a hypothetical completed project.
2Learn to measure success against the original business objectives from the BRD, not just 'it shipped'.
3Practice capturing lessons learned that would genuinely improve the next project.