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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
5-20 min1-3 h15-60 min1-3 h
Participantsdifferent
3-203-122-93-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsSystem Map, Dependencies, Leverage PointsIdeal Day Estimates, Assumption Notes, Capacity CaveatsKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
EstimationEffortRisk
Systems thinkingMappingBoundariesChange
EstimationEffortAgile
KnowledgeMappingRisk
Add more methods