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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
1-2 h1-3 h45-60 min1-4 h
Participantsdifferent
2-81-82-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeArgument Map, Evidence Gaps, Decision RationaleAssumption map, Test backlog, Risk rankingChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
SensemakingDecisionRationale
AssumptionsRiskExperimentsValidation
RiskDecisionSensemaking
Add more methods