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 a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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.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
MediumMediumLowMedium
Timedifferent
2-4 h45-90 min15-45 min1-3 h
Participantsdifferent
4-103-121-31-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
JourneyServiceService design
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods