Facilitation Mapping tool

Timeline

Places events, turning points, and knowledge gaps in an evidence-based course.

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.

Core question

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

Plan the work Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 2-12 people
Time: Duration

Example and worksheet use the same method-specific structure.

Paper timeline with three dates, parallel lanes for work, signals and decisions, and labeled links.

Scope
Bound the period and question
Start, end and purpose are explicit before collection begins.
Events
Collect observable events
Facts, decisions and perceptions are captured one by one.
Sequence
Order and connect events
Cards are sequenced and dependencies are made visible.
Learn
Test patterns and act
The group tests clusters and breaks against the evidence.

Add new evidence at the affected date; give hypotheses and actions a review date.

A good fit when

Useful for longer iterations, projects, changes and incidents when several viewpoints must be combined. Use a dedicated analysis afterward for deep causal work.

Ideal for

Project reviews
Incident learning
Roadmap context

Not good for

Deep root-cause analysis alone
Prioritization without criteria

Outputs

Evidence-based course
Dated events in separate lanes with sources and knowledge gaps.
Learning steps
Tested patterns, hypotheses and actions with owner and review.

Timeline with parallel lanes

Fictional example

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

Timeline with parallel lanes
Lane	May 6	May 13	May 20
WorkWhat was delivered or changed?	Import enabled	Support note added	Import limited
SignalsWhat data or observations are available?	2 test accounts, no errors	9 drop-offs in tickets	Drop-offs fall to 2
DecisionsWhich decision changed the course?	Broad rollout	Measure failure pattern	Keep limit, review June 3

1. May 6
Work
Import enabled
Signals
2 test accounts, no errors
Decisions
Broad rollout
2. May 13
Work
Support note added
Signals
9 drop-offs in tickets
Decisions
Measure failure pattern
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

First step

Set the question, start and end. Make calendars, tickets, releases, metrics and direct participants available.

Open the method guide

Good to do first

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.

Operations

After-Action Review

Supplies the plan and goal against which the evidenced course is laid.

Where to go next?

Operations

5 Whys

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

Systems Thinking

Iceberg Model

Looks behind a recurring turning point for a structural cause.

Deep dive

Purpose

When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time.

How it works

Participants gather events along a shared timeline and mark breaks, clusters, and gaps in the course of events. This reveals which sections shape the view of cause, effect, and the next decisions.

In detail

Timeline works well because events, decisions, and turning points are put into a visible sequence, making patterns over time stand out. Additional precision gains value when different perspectives on the same period are placed side by side and linked to causes and consequences. Substance comes from accuracy, critical gaps, and interpretable transitions, so history becomes a basis for learning or planning.

Facilitation

Clarify in advance which time period and which kind of events you're capturing, so the line doesn't grow arbitrarily. It gets interesting at dense phases or quiet stretches that allow several interpretations; deeper clarification pays off there. Close with the most important turning points and a brief reading of what follows from them.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Timeline Facilitation Sequence

Sources

Agile Retrospectives · Timeline Activityoreilly.comPrimary reference by Esther Derby and Diana Larsen for timeline data gathering in longer retrospectives.Cross-Section Evidence-based Timelines for Software Process Improvement Retrospectivesarxiv.orgCase study on reducing recall gaps through evidence-based cross-perspective timelines.

Artifact templates

Incident TimelineChronological template for incident reconstruction with sources and uncertainty.

markdown

incident-timeline-markdown.md

Chronological template for incident reconstruction with sources and uncertainty.

Incident Timeline

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

Time	Event	Source	Confidence	Note
HH:MM			high/medium/low

Observed delays

Open gaps

Learnings

Timeline: WorksheetPrepare the whole flow or one selected phase with real inputs.

markdown

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.