Pick the format that fits the conversation you need to have. Every template prefills the columns and a reasonable anonymity default — you can override any of it at create time.
The default. Three columns, no surprises.
The canonical sprint retrospective. Works for almost every team and almost every sprint. Start here if the team is new to retros or you just want to surface what to keep and what to fix.
Best for: Most teams, most of the time.
Use this template →Action-oriented. Every card is a behavioural verb.
Forces concrete behavioural framing — every entry is something the team will start doing, stop doing, or keep doing. Cuts through abstract complaints and pushes the conversation toward what changes next sprint.
Best for: Teams stuck in vague complaint mode that need concrete change.
Use this template →Surfaces emotion. Useful when the team feels off.
An emotional framing — what made you mad, sad, or glad this sprint. Use this when the team's morale is dipping or when the data-flavored retros are missing the human signal. Pair with strong anonymity.
Best for: Tense moments. New manager. Failed launch. Friction nobody is naming.
Use this template →Past-tense reflection plus aspiration.
A reflective framing covering wins (Liked), insights (Learned), gaps (Lacked), and future hopes (Longed for). More dimensions than the classic three, useful at quarter or release boundaries when the team has more to process than a single sprint.
Best for: End-of-quarter, end-of-release, or post-mortem retros.
Use this template →Visual metaphor. Good for distributed teams.
Imagine the team as a sailboat: what wind pushes you forward, what anchors hold you back, what rocks (risks) lurk ahead, what island (goal) are you sailing toward. A metaphor-rich format that often unlocks ideas the literal templates miss.
Best for: Distributed teams, kick-off retros, strategy-flavoured cycles.
Use this template →Calibrate intensity rather than binary keep/drop.
Each habit gets nuance: keep it as-is, add it from scratch, do less of it, or do more of it. Better than Start/Stop/Continue when the conversation is about adjusting existing practice rather than introducing wholesale change.
Best for: Mature teams iterating on established practice.
Use this template →