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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
2-8 h30 min Setup, dann laufend45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-121-3 maintaining, briefing for everyone2-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsRAID Log, Status Report SourceAssumption List, Critical Assumptions, Learning PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
RiskTrackingStakeholdersGovernance
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods