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 |  Operations 5 Whys |  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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 |
Timedifferent | 30 min Setup, dann laufend | 15-30 min | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | 1-3 |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | RAID Log, Status Report Source | Root cause notes, Countermeasures | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
