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 PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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 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
MediumMediumMediumLow
Timedifferent
15-45 min1-3 h1-3 h5-20 min
Participantsdifferent
1-83-103-123-20
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
PERT Estimate, Expected Value, Risk NotesDomain Context Map, Boundary Notes, Ownership MapSystem Map, Dependencies, Leverage PointsEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationUncertaintyRisk
Domain-Driven DesignContextBoundaries
Systems thinkingMappingBoundariesChange
EstimationEffortRisk
Add more methods