View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Card Sorting |  Delivery RAID Log |  Architecture Risk Storming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 60-90 min | 15-45 min |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale |
Tagsno overlap | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance |