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 Affinity Diagramming | ![]() Delivery RAID Log |
|---|---|---|---|
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 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 45–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 3-10 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Theme clusters, Insight statements, Opportunity areas | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeRoot cause | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






