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 Three-Point Estimation.
Decision Making
Three-Point Estimation
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption 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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
10-30 min je Item1-3 h2-4 h1-3 h
Participantsdifferent
1-83-103-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesDomain Context Map, Boundary Notes, Ownership MapFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsSystem Map, Dependencies, Leverage Points
Tagsno overlap
EstimationUncertaintyForecasting
Domain-Driven DesignContextBoundaries
Theory of ConstraintsSystems thinkingChange
Systems thinkingMappingBoundariesChange
Add more methods