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 for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 h2-6 h1-4 h1-3 h
Participantsdifferent
3-122-83-81-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanEvent Model, UI Flow, Commands, Read ModelsChallenge Findings, Risk Register, Mitigation PlanArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
KnowledgeMappingRisk
EventsBlueprintDomain-Driven DesignBehavior
RiskDecisionSensemaking
SensemakingDecisionRationale
Add more methods