methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper timeline with three dates, parallel lanes for work, signals and decisions, and labeled links.
Facilitation
Timeline
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
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.When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
LowMediumLowHigh
Timedifferent
30-90 min2-4 h15-30 min1-6 Wochen
Participantsdifferent
2-124-102-64-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Timeline, Milestones, Insight NotesJourney Map, Pain-point List, Opportunity BacklogRoot cause notes, Countermeasures8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
TimelineFacilitationSequence
JourneyServiceService design
Root causeIncidentLeanProblem solving
QualityProblem solvingRoot cause
Add more methods