View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() UX Research Personas | ![]() Architecture Views and Beyond | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 Tage | 1-3 Tage | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Internes Team | 1-4 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Persona Profiles, Needs Summary, Scenario Notes | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ResearchCustomerSynthesis | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |



