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
Paper illustration for Three-Point Estimation.
Decision Making
Three-Point Estimation
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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.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
MediumHighLowLow
Timedifferent
10-30 min je ItemHalber Tag30-120 min15-30 min
Participantsdifferent
1-85-202-62-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesSimulation Notes, Gaps List, Updated RunbooksObservation Notes, Improvement IdeasRoot cause notes, Countermeasures
Tagsno overlap
EstimationUncertaintyForecasting
ResilienceOperationsIncident
LeanObservationProcessOperations
Root causeIncidentLeanProblem solving
Add more methods