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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h1-3 h15-60 min5-20 min
Participantsdifferent
3-124-102-93-20
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanCurrent-state map, Future-state map, Bottleneck listIdeal Day Estimates, Assumption Notes, Capacity CaveatsEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
KnowledgeMappingRisk
LeanFlowWasteDelivery
EstimationEffortAgile
EstimationEffortRisk
Add more methods