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 Card Sorting |  Architecture Architecture Decision Record |  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. | 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. | 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. | 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 | 20-45 min | 15-45 min | 1-2 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Based on research question | 1-3 | 1-4 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Content groups, Label set, IA hypotheses | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Information architectureNavigationStructure | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |