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
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
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 for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
LowMediumMediumLow
Timedifferent
60-90 min2-6 h45-60 min60-90 min
Participantsdifferent
4-102-82-84-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentEvent Model, UI Flow, Commands, Read ModelsAssumption map, Test backlog, Risk rankingAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
EventsBlueprintDomain-Driven DesignBehavior
AssumptionsRiskExperimentsValidation
RiskArchitectureWorkshopValidation
Add more methods