Objectives vs. outcomes

Did we meet the goals in the business case?

The target was invoice processing in two days. We're at three, down from six before go-live.
The goal was to retire the old CRM by June. Finance still uses it.
We aimed for 90% of staff using self-service. Usage is at 72% after eight weeks.
Benefits realized

Which benefits can we measure since go-live?

Month-end close takes four days instead of seven.
We cancelled the licenses for the old reporting tool, which saves $40,000 a year.
Manual entry errors on orders dropped by about two thirds.
What worked

What in the rollout should we repeat next time?

Running the old and new systems side by side for two weeks caught three data errors before cutover.
Super users in each office answered most questions before they reached the help desk.
We rehearsed the cutover twice, and go-live weekend finished six hours early.
Open issues

What still isn't working since go-live?

Finance still exports to Excel to build the monthly report.
The mobile app logs people out every 15 minutes.
Customer records migrated without their notes, and support keeps asking for them.
Actions and owners

Who will fix what, and by when?

Build the monthly finance report in the new system by the end of next month.
Raise the session timeout with the vendor this week.
Recover the customer notes from the old system before its backups are deleted in March.

What is a post-implementation review?

A post-implementation review (PIR) checks whether a system, project or change did what it was meant to do once it went live. It compares the objectives in the business case with the outcomes since go-live, measures the benefits realized so far and lists the issues that are still open. Most PIRs happen one to three months after go-live, when there has been enough real use to judge the result. The board has five columns. Objectives vs. outcomes sets each goal next to what actually happened. Benefits realized records the gains you can measure, with the numbers. What worked captures the parts of the rollout worth repeating, and Open issues lists what still isn't working for users or support. Actions and owners turns the gaps into fixes, each with an owner and a due date. In TeamRetro, everyone adds ideas privately first, then the group sorts them, votes on the issues that matter most and assigns the actions. A PIR looks at the result in production. A Lessons Learned session packages advice for the next project, and an After Action Review debriefs an event straight after it ends. Invite the sponsor, the delivery team and the people who use or support the system, and bring the business case so the review measures against what was promised.

Post-implementation review format

Objectives vs. outcomes

Did we meet the goals in the business case?

Start from the objectives the change was approved for, ideally copied from the business case with their target numbers. For each one, add what has actually happened since go-live and how you know. Where a target was missed, note the gap and save the reasons for the discussion.

Benefits realized

Which benefits can we measure since go-live?

List the gains you can show with numbers or clear evidence, such as time saved, costs avoided, fewer errors or a risk removed. Ask where each figure comes from. Benefits that haven't appeared yet go into Actions and owners with a date to check again, so nobody counts them early.

What worked

What in the rollout should we repeat next time?

Look at the implementation itself: planning, testing, data migration, training, communication and cutover. Ask what made each success possible, so the practice can be reused on the next rollout. Include what users and support noticed, as well as the project team.

Open issues

What still isn't working since go-live?

Collect the problems users and support still live with: defects, workarounds, missing features, slow processes, and gaps in training or data. Ask who is affected and how often. Group duplicates, then vote, so the team fixes the issues that cost the most first.

Actions and owners

Who will fix what, and by when?

Turn the top-voted issues and missed objectives into actions, each with one owner and a due date. Decide which ones the project team fixes and which ones move to business-as-usual support. Add them as actions in TeamRetro, and set a date to re-measure the benefits that need more time.

When to use this retrospective

  • One to three months after a new system, tool or process goes live, when there has been enough real use to compare results with the business case.
  • After a major or failed change in IT, when your change management process calls for a post-implementation review.
  • When a sponsor or steering committee asks whether the project delivered the benefits it promised.
  • Before you close the project budget or hand the system to business-as-usual support, so every open issue has an owner.
  • When people are working around a new system and you need to know why before adoption drops further.

Suggested icebreaker questions

  • What was the first thing you noticed after go-live?
  • Which part of the new system would you miss most if it went away tomorrow?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Pull the business case, the success measures and the go-live date before the session, and add the key numbers to Objectives vs. outcomes yourself. Without them, the review turns into opinion.
  • Invite people who use and support the system, as well as the delivery team. They see the issues the project team has stopped noticing.
  • Separate benefits you can measure from benefits you expect. "Invoice processing fell from six days to two" belongs in Benefits realized, while "should save time" is still a hope.
  • Keep it blameless. Ask what in the plan, the process or the tools let an issue through, not who caused it.
  • Give every open issue an owner before the session ends, including the ones that will move to business-as-usual support.
  • Book a short follow-up for the benefits that need more time to show, and check the actions then.

Frequently asked questions

What should be included in a post-implementation review?
A post-implementation review compares the original objectives with the actual outcomes, measures the benefits realized, records what worked and the issues still open, and assigns actions with owners. Many also compare cost and schedule with the budget. This template gives each part its own column.
What is the purpose of a post-implementation review?
It finds out whether the change delivered the value it was approved for, and what still needs fixing. It also gives the sponsor evidence for closing the project, and shows the next project which estimates and benefits were realistic.
How do you do a PIR?
Gather the business case and the data since go-live, then invite the sponsor, the delivery team and the people who use the system. Work through objectives, benefits, what worked and open issues in that order. Finish by giving each issue an owner and a due date, and share the results with the sponsor.
What questions should a post-implementation review ask?
Did we meet the objectives in the business case? Which benefits can we measure since go-live? What worked well in the rollout? What still isn't working? Who will fix it, and by when? The five columns in this template ask those questions in that order.
When should a post-implementation review be done?
Usually one to three months after go-live, when enough people have used the system to judge it. A major or failed IT change is often reviewed sooner, while the details are still fresh. Benefits that take longer to appear can get a second check later.
What does PIR stand for?
In business and project management, PIR usually means post-implementation review. In IT operations, the same letters can also mean post-incident review, which looks at an outage instead of a planned change.
Ready to run this retrospective?Try this retrospective live