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 of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
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.The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.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.
Complexitydifferent
LowHighLowLow
Timedifferent
30-120 minInitial 3-6 h, then monthly or quarterly reviews30-60 min15-30 min
Participantsdifferent
2-65-122-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Observation Notes, Improvement IdeasExecution Loop, Review Cadence, Strategic Learning LogFishbone Diagram, Cause Categories, Investigation BacklogRoot cause notes, Countermeasures
Tagsno overlap
LeanObservationProcessOperations
ExecutionCadenceLearningGovernance
Root causeQualityOperations
Root causeIncidentLeanProblem solving
Add more methods