View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  UX Research Personas |  Decision Making RAPID |  Decision Making Argument Mapping |
|---|---|---|---|---|
Purposedifferent | 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 target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 1-3 Tage | 45-90 min | 1-3 h |
Participantsdifferent | 1-3 | Internes Team | 3-12 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Persona Profiles, Needs Summary, Scenario Notes | RAPID Role Map, Recommendation, Decision Log | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ResearchCustomerSynthesis | DecisionRolesGovernance | SensemakingDecisionRationale |