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
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.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 problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30–45 min1-3 h1-4 h30-60 min
Participantsdifferent
1-103-103-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsProcess Map, Handoff List, Improvement BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
FramingOpportunityIdeationQuestions
ProcessOperationsImprovement
Root causeProblem solvingQualityIncident
Root causeQualityOperations
Add more methods