7.2 Project Retrospective and Evaluation
Managing a project well during execution matters — but what truly strengthens the next project is what happens after this one ends: reflection and evaluation.
This section covers how to reflect on results, process, team, and organization together, and how to use structured methods to surface successes worth repeating and mistakes worth avoiding.
Why Retrospectives Matter
Once a project ends, most team members move straight to the next assignment. Skipping the retrospective tends to leave:
- Success factors that nobody can quite name — and therefore can’t repeat
- Mistakes and oversights that quietly recur
- Insights stuck in one person’s head, never reaching the team
A retrospective isn’t about blaming the past; it’s a strategic move to raise the odds for the next project.
Four Dimensions of a Project Review
For a holistic view, look at the project from four angles:
- Results: were the goals met? quality, delivery, cost, satisfaction
- Process: were planning, progress tracking, and change management effective?
- Team: were collaboration, roles, and communication clear?
- Environment: were external factors — stakeholders, structure, tools — appropriate?
Looking at all four moves the conversation past “it went well / it didn’t” toward insights with real depth.
Evaluation Methods: KPT, 5 Whys, 360-Degree Feedback
KPT (Keep / Problem / Try)
- Keep: what went well and should continue
- Problem: what didn’t go well
- Try: ideas for improvement
5 Whys
Trace problems to their root by asking “why?” five times in a row. It pushes past symptoms toward the actual cause.
360-Degree Feedback
Collect feedback from everyone involved so the team sees itself from multiple angles — revealing dynamics that any single perspective would miss.
Using ActionBridge for Retrospectives
ActionBridge gives the retrospective something to stand on:
- Replay task histories and comments to see how decisions actually flowed
- Use burndown and Gantt views to analyze pace and where delays appeared
- Share retrospective templates (KPT format) as common documents
- Collect candid feedback through anonymous comments or surveys
The result is a fact-based, dialogue-driven review — not a memory contest.
How to Make Retrospectives Stick
To keep retrospectives from sliding into ritual:
- Schedule them as part of closure, not as an optional extra
- Involve the whole team, not just the PM
- Frame the conversation as forward-looking improvement, not fault-finding
- Feed the output back into project templates and WBS for next time
Summary: Retrospectives Spark Improvement
A retrospective isn’t about regretting the past — it’s about designing a better next project. Turning insights into shared team knowledge, rather than personal lessons, is the hallmark of a learning team.
How this looks in AB
In AB Project Management, a Retrospective page in the project Wiki captures KPT in a format the next team can search. Pin it from the project home so it’s the first thing anyone sees later. Tasks tagged Lesson carry individual takeaways with owners — and AI assistants connected via MCP can be asked to summarize the project’s change-history into a draft retrospective to seed the discussion.
→ Next, go to 7.3 Knowledge Transfer for Future Projects and explore how to capture and pass on learnings effectively.