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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
5-20 min1-3 h1-3 hHalf day
Participantsdifferent
3-203-122-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsSystem Map, Dependencies, Leverage PointsContext Map, Integration Patterns, Boundary NotesStress Test Report, Action Plan per Scenario
Tagsno overlap
EstimationEffortRisk
Systems thinkingMappingBoundariesChange
Domain-Driven DesignBoundariesStrategy
StrategyBusiness modelRiskDiagnosis
Add more methods