View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordHypothesis-Driven TroubleshootingRAID LogArchitecture Communication Canvas
| Criterion |  Architecture Architecture Decision Record |  Engineering Hypothesis-Driven Troubleshooting |  Delivery RAID Log |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 30-240 min | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | 1-3 | 1-6 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TroubleshootingProblem solvingDiagnosis | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |