methodatlas
Method guideFacilitation

Timeline

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityLow
Time30-90 min
Participants2-12
FormatWorkshop + async
MaturityCanonical
Plan the work
01

Prerequisite

What needs to be finished first

Complete firstBounded period

Start, end and reason are named.

Without a boundary, collection becomes arbitrary.
Complete firstEvidence access

At least one dated source and direct participants are available.

Without sources, the timeline can reinforce recall bias.
02

Preparation

What needs to be ready before start

Materials

Long paper strip or digital board, cards, markers and access to dated sources.

People / roles

Facilitator, timekeeper, scribe and participants with different viewpoints.

Pre-read

Gather calendar entries, tickets, releases, incident events, decisions and key metrics.

Time needed

30–90 minutes depending on period and evidence.

Setup

Lay out time horizontally and prepare parallel lanes for work, signals and decisions. Define notation for fact, perception, hypothesis and gap.

03

Core question

The one question this method answers

Which supported events and turning points explain how the situation developed during the reviewed period?

04

Flow

Phases with goal, actions, output and pitfall

A timeline reconstruction connects dated events, decisions and perceptions across a bounded period. It supports shared recall and learning without treating temporal proximity as causation.

Timeline with parallel lanes

Fictional example

Fictional review of a course portal launch. Temporal sequence is separated from supported dependency.

Timeline with parallel lanes
LaneMay 6May 13May 20
WorkWhat was delivered or changed?Import enabledSupport note addedImport limited
SignalsWhat data or observations are available?2 test accounts, no errors9 drop-offs in ticketsDrop-offs fall to 2
DecisionsWhich decision changed the course?Broad rolloutMeasure failure patternKeep limit, review June 3

  1. 1. May 6

    Work
    Import enabled
    Signals
    2 test accounts, no errors
    Decisions
    Broad rollout

  2. 2. May 13

    Work
    Support note added
    Signals
    9 drop-offs in tickets
    Decisions
    Measure failure pattern

  3. 3. May 20

    Work
    Import limited
    Signals
    Drop-offs fall to 2
    Decisions
    Keep limit, review June 3

The link between broad rollout and drop-offs is a hypothesis to test.

Agile Retrospectives · Timeline activity

  1. 1

    Scope

    Bound the period and question

    Goal

    Create one shared temporal and topical boundary.

    Inputs for this step

    • Reason for the review
    • Known start and end points

    Actions

    • State the guiding question and start and end dates.
    • Name relevant event types and viewpoints; clarify privacy and confidentiality.

    Output

    Timeline boundary

    Question · start · end · viewpoints

    Quality check

    Would an event outside the period be excluded unambiguously?

    Pitfall

    The group retells the entire project history without a clear boundary. Post the start, end and question visibly and park out-of-scope contributions.

    Timing: 5–10 minutes

  2. 2

    Events

    Collect observable events

    Goal

    Build a broad and checkable event base.

    Inputs for this step

    • Calendars, tickets, releases or incident data
    • Participant recollections

    Actions

    • Capture one event per note with date or period and source.
    • Label observation, decision and personal perception; mark uncertainty.

    Output

    Event cards

    Time · event · source · type · confidence

    Quality check

    Does every card include time and a traceable source or label?

    Pitfall

    General judgements replace concrete events and points in time. Ask for the date, observable change and origin of the statement.

    Timing: 10–20 minutes

  3. 3

    Sequence

    Order and connect events

    Goal

    Create a readable course with turning points and gaps.

    Inputs for this step

    • Event cards
    • Defined period

    Actions

    • Order cards by time; use parallel lanes for work, decisions and effects.
    • Mark predecessor, consequence, break and information gap with labeled links.

    Output

    Evidence-based timeline

    Lanes · turning points · links · gaps

    Quality check

    Are sequence and claimed dependency visibly distinct?

    Pitfall

    Proximity on the timeline is treated as causality without evidence. Use separate notation for temporal sequence and supported dependency.

    Timing: 10–25 minutes

  4. 4

    Learn

    Test patterns and act

    Goal

    Derive a checkable learning question and next action.

    Inputs for this step

    • Ordered timeline
    • Marked gaps and turning points

    Actions

    • Describe clusters, long waits and turning points without asserting causes too early.
    • Record one central explanation, missing evidence, action, owner and review date.

    Output

    Learning and action record

    Pattern · hypothesis · gap · action · review

    Quality check

    Does the action follow supported evidence or an explicitly labeled hypothesis?

    Pitfall

    The review ends with interesting stories but no checkable follow-through. Schedule one learning question and bounded action with an owner and review.

    Timing: 10–20 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Timeline · Ereignisse über ZeitEreignisse chronologisch ordnen, Wendepunkte markieren und daraus Muster, Lücken oder nächste Schritte ableiten
TimelineDas Visual zeigt eine chronologische Ereignisachse mit Ereigniskarten, Wendepunkt, Muster und abgeleitetem Insight.Ereignisse zeitlich ordnen und Muster sichtbar machenTimeline-Arbeit trennt Chronologie, Interpretation und abgeleitete Lernpunkte.StartScope und ZeitraumEreignisEntscheidung fälltWendungneue InformationMusterVerzögerung sichtbarableitenInsightBrüche und Abhängigkeiten alsnächste Schritte festhalten
Form

Timeline with dated events, sources, turning points, gaps, learning questions and agreed actions.

Versioning / ownership

Record period, creation date and evidence version. Add later evidence and label changed interpretations.

Tool alternatives
  • Paper wall and cards
  • Digital whiteboard with lanes
  • Table export for dated events

incident-timeline-markdown.md

Chronological template for incident reconstruction with sources and uncertainty.

Incident Timeline

Incident: ... Period: ... Sources: logs, alerts, chat, tickets

TimeEventSourceConfidenceNote
HH:MMhigh/medium/low

Observed delays

  • ...

Open gaps

  • ...

Learnings

  • ...

timeline-working-template.md

Prepare the whole flow or one selected phase with real inputs.

Timeline: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete timeline Time: 30–90 minutes plus evidence gathering

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Long paper strip or digital board, cards, markers and access to dated sources.
  • Roles: Facilitator, timekeeper, scribe and participants with different viewpoints.
  • Advance information: Gather calendar entries, tickets, releases, incident events, decisions and key metrics.
  • Overall time needed: 30–90 minutes depending on period and evidence.
  • Setup: Lay out time horizontally and prepare parallel lanes for work, signals and decisions. Define notation for fact, perception, hypothesis and gap.

Prepare for the work steps

Scope: Bound the period and question

  • Reason for the review
  • Known start and end points

Events: Collect observable events

  • Calendars, tickets, releases or incident data
  • Participant recollections

Sequence: Order and connect events

  • Event cards
  • Defined period

Learn: Test patterns and act

  • Ordered timeline
  • Marked gaps and turning points

Timeline with parallel lanes

LaneTime 1Time 2Time 3
Work
Signals
Decisions
  • Work: What was delivered or changed?
  • Signals: What data or observations are available?
  • Decisions: Which decision changed the course?

Enter your own dates, sources and decisions. Label links as supported or assumed.

Agile Retrospectives · Timeline activity

Scope: Bound the period and question

Expected artifact: Timeline boundary

Question · start · end · viewpoints

Entry:

...

  • Would an event outside the period be excluded unambiguously?

Events: Collect observable events

Expected artifact: Event cards

Time · event · source · type · confidence

Entry:

...

  • Does every card include time and a traceable source or label?

Sequence: Order and connect events

Expected artifact: Evidence-based timeline

Lanes · turning points · links · gaps

Entry:

...

  • Are sequence and claimed dependency visibly distinct?

Learn: Test patterns and act

Expected artifact: Learning and action record

Pattern · hypothesis · gap · action · review

Entry:

...

  • Does the action follow supported evidence or an explicitly labeled hypothesis?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/timeline/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

timeline-beispiel.md

Concrete filled scenario, fictional example

Fictional example: course portal

May 6: Import enabled for all accounts; two test accounts showed no errors. May 13: Nine support tickets report drop-offs; decision: measure the failure pattern. May 20: Parallel imports limited; drop-offs fall to two.

Hypothesis: The broad rollout increased parallel imports. Logs still need to confirm this. Next step: Operations checks concurrency by May 27; review on June 3.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Bound the period and questionThe group retells the entire project history without a clear boundary.View in phase
  2. Collect observable eventsGeneral judgements replace concrete events and points in time.View in phase
  3. Order and connect eventsProximity on the timeline is treated as causality without evidence.View in phase
  4. Test patterns and actThe review ends with interesting stories but no checkable follow-through.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

The period or guiding question remains disputed.
Important claims lack both time and source.
The group treats temporal proximity as proven causation.
A necessary person or source is missing for the central segment.
Actions have no owner or review date.

Where to go next?

A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys

Traces a cluster recognized in the timeline back to its root cause.

Iceberg Model method illustration showing its working structure
Systems Thinking
Iceberg Model

Looks behind a recurring turning point for a structural cause.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods