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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
30–45 min20-60 min30-120 min1-3 h
Participantsdifferent
1-101-42-63-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsRunbook, Checklist, Escalation PathObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
FramingOpportunityIdeationQuestions
OperationsReliabilityDocumentation
LeanObservationProcessOperations
ProcessOperationsImprovement
Add more methods