Timeline Retrospective

When to use

End of a project, end of a quarter, end of a year. Anywhere the team has enough events to plot and enough emotional range to draw a line. Don't run it on a two-week sprint — the setup overhead doesn't pay back when there are six events to plot. Skip it for sprints; use SSC. Skip it remotely if you can't get a board big enough — a six-month timeline on a 13-inch laptop is unreadable.

How it runs

1. Pre-populate the events as facilitator

   Releases, hires, departures, incidents, milestones. Build the event timeline before the meeting — if the team spends thirty minutes remembering when things happened, you've burned the meeting on the calendar. The team's time should go on the dots, not the timeline.

2. Walk the events together, briefly

   Five to ten minutes. Confirm the events, add anything missing. Don't discuss yet — the discussion happens after the mood line is drawn.

3. Plot mood dots, silently

   Each person puts dots above the line (good) or below (rough) at each event, height indicating intensity. Fifteen minutes. The dots are personal — not a team consensus, not an average.

4. Draw the line

   Connect the dots into a line per person, or draw a single average line across the team. Look at the shape — where it climbed, where it dipped, where two people remember the same week very differently.

5. Discuss the dips and the gaps

   The discussion is about the shape, not every event. Spend the time on the deepest dip, the steepest climb, and the events where the team's dots disagreed most. Those three points carry the meeting.

6. Capture lessons for the next cycle

   End of project or quarter — the right output is lessons, not next-sprint commitments. Two or three lessons named, with whoever owns carrying them forward.

Why it works

Listing what happened produces a calendar. The mood line turns it into a story — the team can see the shape of how the cycle felt, which is information that doesn't survive in card-based formats. The disagreement between dots is often the most useful signal: when one person remembers the launch as a win and another remembers it as the worst week of the quarter, the gap between their dots is the conversation.

Variations

• Mood line per person vs single team average. Per-person surfaces disagreement (useful); single average smooths it out (faster but less revealing).
• Pair it with 4Ls — Timeline first to surface the events and shape, 4Ls to extract Liked/Learned/Lacked/Longed For from each major dip and climb.
• Drop the events and run mood-only as 'Emotional Seismograph' — useful when the team's calendar is well-known but the feelings haven't been said.
• Add markers for arrivals, departures, kudos, challenges, milestones — Miro's variant. More structure; more setup; better for projects with many discrete sub-phases.

Facilitator notes

Pre-population is the load-bearing piece. If the facilitator hasn't built the event timeline beforehand, the meeting becomes a 30-minute calendar exercise and the mood discussion gets squeezed. Walk through the events yourself the day before; treat anything missing as a sign you're not close enough to the team's reality to facilitate this retro.

Pitfalls

• Running it on a sprint. There aren't enough events. Use SSC.
• Skipping pre-population. Half the meeting becomes a calendar exercise; the mood line gets fifteen minutes.
• Treating the mood line as a quiz with right answers. The disagreement between dots is the value, not a bug.
• Discussing every event. Spend the time on the deepest dip, the steepest climb, and the gaps — three points, not twelve.

Remote tips

The visual is the part that fails remotely. Pre-build the timeline at high resolution; share-screen and zoom to one event at a time during discussion rather than asking everyone to read a 6-month canvas on their laptop. Open the board 48 hours before so async writers can plot dots; the mood line benefits from people thinking about it overnight.

Example outputs

• Event (week 4): the auth migration. Most dots low — the team remembers it as the rough patch.
• Event (week 9): the on-call rota change. Most dots high; one dot low (the engineer who absorbed the worst pages before the change).
• Event (week 11): the customer escalation. Wide spread — half the team felt it acutely, half barely noticed. The gap is the conversation.
• Lesson: pre-flight runbooks before any migration that touches auth. Owner: Priya. To carry into next quarter.

FAQ

Timeline or Start/Stop/Continue?

Timeline for end-of-project or end-of-quarter, when there are enough events to plot and the right output is understanding. SSC for sprints, when the right output is action. Don't run Timeline on a two-week sprint — there isn't enough material, and the setup overhead doesn't pay back.

How long does it take?

Sixty to ninety minutes done well, plus an hour of facilitator prep beforehand to populate the events. If you're scheduling thirty minutes for a Timeline retro, you're either rushing or you should run something else.

Should the mood line be per-person or team average?

Per-person, almost always. The disagreement between dots is the most useful signal Timeline produces — the week somebody remembers as a win and somebody else as a disaster is the conversation you came for. Averaging the dots loses that.

Related activities

Recommended use cases