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 Risk Storming |  UX Research Affinity Diagramming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. | 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 | 30 min Setup, dann laufend | 60-90 min | 45–90 min | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-12 | 3-10 | 1-3 |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | Theme clusters, Insight statements, Opportunity areas | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | SynthesisQualitativeRoot cause | ArchitectureRationaleDocumentationGovernance |