5Fs retro
Definition
A retrospective format with five columns: Facts (what happened), Feelings (how the team felt), Findings (lessons learned), Future (what to try next), and Fun (what to celebrate).
The 5Fs retro is a comprehensive format that deliberately separates data from emotion and diagnosis from prescription. Most retrospective formats collapse some of these layers, Facts and Feelings are distinct in 5Fs because teams often conflate observations with interpretations, and separating them produces cleaner action items.
Column breakdown:
- Facts, objective events: shipped three features, missed the deadline by two days, onboarded two new engineers.
- Feelings, emotional responses: the team felt rushed, there was anxiety about the deadline, the demo felt good.
- Findings, lessons: we underestimated integration time, we need a pre-mortem before big features.
- Future, experiments and commitments: add integration time to estimates, schedule a pre-mortem for next quarter's launch.
- Fun, wins worth celebrating: the design-engineering collaboration was unusually smooth, the new hire got up to speed in two days.
When to use it: Best for quarterly or project-level retrospectives where there's enough to reflect on. The five columns take longer to populate than three-column formats, budget 45 to 60 minutes rather than 30.
Why Fun as a separate column: Teams consistently underinvest in celebration. Making Fun explicit forces acknowledgment of what went right in a way that's distinct from Findings, it's about morale and culture, not lessons.
BoardSnap reads the 5Fs board and outputs a five-section structured summary. Each section maps to a column, and the Future items become action items with priority flags.
Examples
- Facts: shipped four features, two bugs in production. Feelings: proud of the pace but stressed by the last-minute QA crunch. Findings: QA needs to start in parallel with development. Future: pair QA with each feature team. Fun: the new CI pipeline got cheers in standup.
- An engineering team uses the 5Fs retro at the end of every quarter to get a more complete picture than their sprint-level start / stop / continue sessions provide.
- A product manager uses the 5Fs format with a cross-functional team that includes design, engineering, and customer success, the Facts column keeps the conversation grounded.
- A coach introduces the 5Fs to a team that has been running the same three-column retro for two years and needs fresh prompts.
Snap a 5fs retro. Ship its actions.
BoardSnap turns any whiteboard, including this one, into a summary and action plan.