Meetings
Run a Small-Team Retrospective That Leads to One Change
Keep retrospectives practical by choosing one improvement, one owner, and one follow-up date.
A retrospective is successful when it changes one future behavior, not when it produces the longest list.
Collect observations before the meeting
Ask people to add notes before the retro. This gives quieter teammates time to think and keeps the meeting from being dominated by the freshest frustration.
Group observations by what helped, what slowed work, and what needs a decision.
Choose one improvement
A team can discuss many issues, but it should commit to one concrete change at the end.
The change should be small enough to try in the next cycle and clear enough that everyone knows whether it happened.
Review the change next time
Begin the next retrospective by checking the previous action. Did it happen? Did it help? Should it continue?
This creates accountability without making the retro feel punitive.
Quick checklist
- Collect notes before the retro.
- Group observations.
- Choose one improvement.
- Assign one owner.
- Review the action in the next retro.
Guide FAQ
How should I adapt this guide for a small team?
Start with the checklist, assign one owner, and run the workflow for one week before adding extra fields or process steps.
Should this replace our project-management software?
No. These guides are designed to clarify lightweight workflows. They can support a larger tool, but they do not need to replace one.
What is the best first step?
Write the outcome you want, choose the smallest related template or checklist, and test it on one real workflow before scaling it.