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
Six paper cards show a person moving from a problem through a service flow to a completed outcome.
UX Design
Storyboarding
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
When a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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
MediumLowMediumMedium
Timedifferent
30-90 min15-45 min1-2 h1-3 h
Participantsdifferent
1-81-31-81-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Storyboard, Concept Narrative, Testable AssumptionsADR File, Decision Log, RationaleConcept Map, Relationship Labels, Knowledge GapsArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
VisualizationConceptsSequencePrototype
ArchitectureRationaleDocumentationGovernance
KnowledgeConceptsMappingSensemaking
SensemakingDecisionRationale
Add more methods