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
How Might We
Innovation
How Might We
Process Mapping method illustration showing its working structure
Operations
Process 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 Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30–45 min1-3 h15-30 min1-4 h
Participantsdifferent
1-103-102-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsProcess Map, Handoff List, Improvement BacklogRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
FramingOpportunityIdeationQuestions
ProcessOperationsImprovement
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods