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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowMediumLowMedium
Timedifferent
5-20 min1-3 h15-30 min1-4 h
Participantsdifferent
3-204-102-63-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsCurrent-state map, Future-state map, Bottleneck listRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
EstimationEffortRisk
LeanFlowWasteDelivery
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods