Timeline Retrospective
Sorts by when it happened, not what kind — the only format built to catch narrative arcs other retros flatten into a single pile.
Free · No credit card · Guests join by link
The board
01
EARLY SPRINT
What happened in the first few days?
02
MID SPRINT
What happened around the midpoint?
03
LATE SPRINT
What happened as you wrapped up?
Every other format in this catalog sorts cards by category — strength or risk, mad or glad. Timeline sorts by when: early sprint, mid sprint, late sprint. It trades categorical clarity for chronological shape, and that trade reveals something the other formats structurally can't: whether problems cluster at a specific point in the sprint.
That distinction is easy to miss from memory alone. A team that 'always struggles at the end' looks identical, in a category-based retro, to a team with scattered problems throughout — both just produce a pile of Risk cards. Timeline is the format that makes the difference visible, because the columns themselves are the calendar.
When to use Early · Mid · Late Sprint
- You suspect problems cluster near a specific point in the sprint — usually the end — but can't prove it from memory
- Long or multi-week sprints where early-sprint events fade by the time retro happens
- Irregular sprints — a big release, an incident, a scramble — where the order of events matters more than a category
- Onboarding a new lead or PM who needs to understand a sprint's actual shape, not just an aggregate mood
How to run it in Retromik
- 1
Anchor the boundaries before writing
State roughly which dates count as early / mid / late for this sprint in the board's focus question, so everyone sorts consistently instead of guessing.
- 2
Vote on what matters
Each person places a limited set of voting tokens on the cards they think deserve discussion. Limited tokens force real prioritization.
- 3
Discuss the top cards
Walk through the highest-voted cards one by one. The facilitator steers the focus; anyone can comment on any card.
- 4
Reveal and group themes
Authors are revealed and the facilitator drags related cards into named themes, turning scattered notes into patterns.
- 5
Commit to action items
Convert the discussion into specific, owned action items with due dates — the part most retrospectives skip.
Frequently asked questions
What is a Timeline retrospective?
A retro that sorts cards chronologically — early sprint, mid sprint, late sprint — instead of by category like strengths or risks. It's designed to surface when problems happened, not just what kind of problem they were.
How is this different from Strengths, Risks, Learnings?
Strengths·Risks·Learnings tells you what happened; Timeline tells you when. A team can have the exact same set of problems, but if they all cluster in the last two days, that's an actionable pattern a category-based retro won't surface on its own.
What if a sprint doesn't have a clean early/mid/late structure?
Use whatever three-part split makes sense — pre-launch/launch/post-launch for a release sprint, or before/during/after an incident. The value is in ordering, not the exact labels; feel free to rename the columns for your context.
Is the Timeline template free to use?
Yes. Retromik is free — create a board with the Timeline template, share the link, and teammates can join and add cards as guests without an account.
Related templates
Strengths · Risks · Learnings
A balanced sprint review that looks backward and forward at once — Retromik's signature format.
ViewMuda · Mura · Muri
Toyota's lean lens for sprint retros — hunt waste, unevenness, and overload instead of vague complaints.
ViewMad · Sad · Glad
An emotional check-in that surfaces how the team actually feels — before it becomes attrition.
ViewRun your next retro with Early · Mid · Late Sprint
Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.
Start free