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 of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration for Risk Storming.
Architecture
Risk Storming
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
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.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.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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h60-90 min60-90 min45-60 min
Participantsdifferent
2-84-104-122-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeProblem Cluster, Prioritized Challenge, ExperimentAnnotated Diagram, Prioritized Risk List, Action BacklogAssumption map, Test backlog, Risk ranking
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
FacilitationDecisionProblem solvingWorkshop
RiskArchitectureWorkshopValidation
AssumptionsRiskExperimentsValidation
Add more methods