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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumHighLowLow
Timedifferent
2-8 hSeveral meetings plus preparation and analysis; total effort depends on scope45-90 min60-90 min
Participantsdifferent
5-12Evaluation team, architects, and relevant stakeholders2-84-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAssumption List, Critical Assumptions, Learning PlanAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureQualityRiskTradeoffsStakeholders
AssumptionsRiskDecisionDiscovery
RiskArchitectureWorkshopValidation
Add more methods