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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h45-90 min90-180 min initial, dann laufend1-2 h
Participantsdifferent
2-82-83-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesAssumption List, Critical Assumptions, Learning PlanKPI Tree, Owner ListDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
AssumptionsRiskDecisionDiscovery
MetricsStrategyAlignmentMeasurement
StrategyDecisionAssumptionsHypothesis
Add more methods