View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Personas | ![]() Delivery Communication Plan | ![]() Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 Tage | 45-90 min | 15-45 min |
Participantsdifferent | Internes Team | 2-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Communication Plan, Channel Matrix, Message Cadence | ADR File, Decision Log, Rationale |
Tagsno overlap | ResearchCustomerSynthesis | CommunicationStakeholdersDeliveryPlanning | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






