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 Card Sorting | ![]() 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 content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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 | 20-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | Based on research question | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






