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 for Wideband Delphi.
Decision Making
Wideband Delphi
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.A single opinion rarely holds up for planning when the future is genuinely uncertain. It separates options, evaluation criteria, and open risks. The result is captured as an Estimate Range, Assumption Log, and Expert Consensus Notes.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
1-3 h1-4 h or multiple rounds45-60 min1-4 Wochen
Participantsdifferent
2-84-12 Experten2-81-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Context Map, Integration Patterns, Boundary NotesEstimate Range, Assumption Log, Expert Consensus NotesAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
EstimationExpertsForecasting
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods