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 Dot Estimation.
Facilitation
Dot Estimation
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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
LowMediumHighLow
Timedifferent
5-20 min1-3 h2-6 h15-30 min
Participantsdifferent
3-204-103-82-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsCurrent-state map, Future-state map, Bottleneck listFault Tree, Critical Paths, Cause Hypotheses, Control ActionsRoot cause notes, Countermeasures
Tagsno overlap
EstimationEffortRisk
LeanFlowWasteDelivery
RiskRoot causeSafety
Root causeIncidentLeanProblem solving
Add more methods