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 |  Architecture Architecture Decision Record |  UX Research Affinity Diagramming |  Architecture arc42 |
|---|---|---|---|---|
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. | 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 15-45 min | 45–90 min | 1-2 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-3 | 3-10 | 1-4 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Theme clusters, Insight statements, Opportunity areas | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeRoot cause | ArchitectureDocumentationCommunication |