R
Retromik

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.

Use this template free

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 a Timeline Retrospective

  • 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 a Timeline Retrospective

  1. 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. 2

    Write events, not opinions

    Each card is something that happened, ideally with a day: "Day 3: staging went down". Opinions come later, in the discussion.

  3. 3

    Mark highs and lows

    Ask people to start each card with + or −. Read across the three columns and the sprint's shape appears: where it went well and where it dipped.

  4. 4

    Find the turning point

    Look for the moment the sprint changed direction, for better or worse. That's usually the most useful conversation.

  5. 5

    Act on the pattern, not the event

    One bad day is noise. If the same dip shows up sprint after sprint, like a rush in the last two days, that's the thing to fix.

Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.

Read the full facilitation guide

Example cards

What good cards look like for a software team. Specific, about the work, never about a person.

EARLY SPRINT

  • − Planning took two hours because stories weren't ready.
  • + The new joiner had a laptop on day one.

MID SPRINT

  • − Staging was down for a day and a half.
  • − Product changed the priority of the import feature.

LATE SPRINT

  • − We rushed three stories into the last day.
  • + The release went out on time after a late fix.

A 45-minute agenda

  1. 0–5 minSet the date boundaries
  2. 5–15 minWrite events with + or −
  3. 15–20 minRead the timeline left to right and vote
  4. 20–35 minDiscuss the turning point and the biggest dips
  5. 35–45 minAgree actions for patterns, not one-off events

Common mistakes

  • Cards that are opinions instead of events.
  • Only the last few days get remembered. Prompt for the first week explicitly.
  • Storytelling that runs long. Keep each event to one card.
  • Fixing one-off events instead of repeating patterns.

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.

Does a Timeline retrospective work for a quarter or a whole project?

Yes, it's a natural fit for longer periods, where people forget the early weeks. Rename the three columns in Retromik to match the phases, for example by month or by milestone.

Related templates

Strengths, Risks, Learnings Retrospective

Strengths · Risks · Learnings

A balanced sprint review that looks backward and forward at once — Retromik's signature format.

View

Kaizen Retrospective

Muda · Mura · Muri

Toyota's lean lens for sprint retros — hunt waste, unevenness, and overload instead of vague complaints.

View

Mad, Sad, Glad Retrospective

Mad · Sad · Glad

An emotional check-in that surfaces how the team actually feels — before it becomes attrition.

View

Run a Timeline Retrospective with your team

Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.

Start free