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 illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitydifferent
HighLowLow
Timedifferent
2-6 h30-60 min15-30 min
Participantsdifferent
3-103-122-6
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Event Timeline, Causal Factor Chart, Cause List, Corrective ActionsStart Stop Continue Board, Improvement ActionsRoot cause notes, Countermeasures
Tagsno overlap
CausalityIncidentRoot causeTimeline
RetrospectiveImprovementTeamReflection
Root causeIncidentLeanProblem solving
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective