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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.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.
Complexitysame
LowLowLowLow
Timedifferent
30-120 min45-90 min30-60 min15-30 min
Participantsdifferent
2-63-122-82-6
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Observation Notes, Improvement IdeasExpectation Map, Alignment Notes, AgreementsFishbone Diagram, Cause Categories, Investigation BacklogRoot cause notes, Countermeasures
Tagsno overlap
LeanObservationProcessOperations
AlignmentStakeholdersTeam
Root causeQualityOperations
Root causeIncidentLeanProblem solving
Add more methods