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 for Risk Storming.
Architecture
Risk Storming
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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 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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-8 h60-90 min3–4 h for initial assessment; preparation and deeper analysis additional45-60 min
Participantsdifferent
5-124-121 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsAnnotated Diagram, Prioritized Risk List, Action BacklogLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksAssumption map, Test backlog, Risk ranking
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskAssessmentLean
AssumptionsRiskExperimentsValidation
Add more methods