View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingCommunication PlanArchitecture Decision RecordViews and Beyond
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Delivery Communication Plan |  Architecture Architecture Decision Record |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-240 min | 45-90 min | 15-45 min | 1-3 Tage |
Participantsdifferent | 1-6 | 2-6 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Communication Plan, Channel Matrix, Message Cadence | ADR File, Decision Log, Rationale | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | CommunicationStakeholdersDeliveryPlanning | ArchitectureRationaleDocumentationGovernance | DocumentationStakeholdersArchitecture |