Compare plan and result
Begin with what was intended, what happened and the evidence behind the difference.
← All toolkits
Manager routines
Team Retrospective
Compare intended and actual results, identify what shaped performance and choose one owned improvement.
Use this when
Start with a live team problem.
- A project or delivery cycle has just finished.
- The same operational issue keeps returning.
- The team moves quickly but rarely adjusts the system.
How to use it
Move from context to one usable agreement.
Examine conditions
Look at decisions, information, handoffs, tools and assumptions before judging individuals.
Choose one improvement
Assign an owner and a testable change for the next cycle.
Worked example
Retrospective after a product launch
Use the example to understand the level of specificity. Replace the content with evidence from your own team.
INTENDED RESULT Launch on Tuesday with sales, support and customer communications ready. ACTUAL RESULT Product launched Tuesday. Support guidance arrived Wednesday and created inconsistent answers. WHAT HELPED - Clear launch owner - Daily risk review in the final week WHAT HINDERED - Support was informed after the release decision - No owner for the customer-question guide WHAT WE LEARNED Technical readiness and operating readiness were treated as the same decision. ONE IMPROVEMENT Add Support sign-off and a named customer-guidance owner to the launch readiness check. OWNER AND REVIEW Head of Product. Test on the next release and review within 48 hours.
Blank template
Team Retrospective
Copy this into Docs, Notion or your existing workspace, or print it for a team conversation.
TEAM RETROSPECTIVE Work or period reviewed: Facilitator: Date: INTENDED RESULT ACTUAL RESULT WHAT HELPED - WHAT HINDERED - WHAT SURPRISED US - WHAT WE LEARNED - ONE IMPROVEMENT TO TEST - OWNER REVIEW DATE AND EVIDENCE -
The System Folks · Free founder resource · thesystemfolks.com/resources/team-retrospective
Common mistakes
Keep the tool connected to real work.
- 01
Turning the review into a list of complaints.
- 02
Choosing several improvements that no one owns.
- 03
Reviewing memory and opinion without comparing intended and actual results.
Why this works
Evidence behind the resource
Properly conducted debriefs improved individual and team effectiveness by roughly 20 to 25 per cent on average.
Read Debriefs and performance meta-analysisNeed help implementing it?
A template can reveal a bigger operating problem.
If each retrospective reveals the same cross-team constraints, we can help redesign the workflow and operating rhythm rather than repeating the discussion.
Contact us when one costly workflow or team bottleneck needs diagnosis, build support and adoption.
Get implementation support Use another toolkit