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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitydifferent
LowHighMediumMedium
Timedifferent
1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope45-60 min1-2 Wochen pro Iteration
Participantsdifferent
2-8Evaluation team, architects, and relevant stakeholders2-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAssumption map, Test backlog, Risk rankingPrioritized Assumption List, Test Plan, Results Report
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ArchitectureQualityRiskTradeoffsStakeholders
AssumptionsRiskExperimentsValidation
ExperimentsValidationDiscoveryAssumptions
Add more methods