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 |  Engineering Hypothesis-Driven Troubleshooting |  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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 30-240 min | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 1-3 |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | TroubleshootingProblem solvingDiagnosis | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
