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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
LowLowMediumLow
Timedifferent
15-30 min30-60 min1-4 h30-60 min
Participantsdifferent
2-63-123-83-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Root cause notes, CountermeasuresStart Stop Continue Board, Improvement ActionsProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanEmotion Board, Themes, Action Items
Tagsno overlap
Root causeIncidentLeanProblem solving
RetrospectiveImprovementTeamReflection
Root causeProblem solvingQualityIncident
RetrospectiveTeamReflection
Add more methods