View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Decision Making Cynefin Workshop |  Architecture Architecture Decision Record |  Decision Making DACI |
|---|---|---|---|---|
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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-240 min | 60-180 min | 15-45 min | 30-60 min |
Participantsdifferent | 1-6 | 4-20 | 1-3 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Cynefin Map, Domain-specific Actions, Sensemaking Notes | ADR File, Decision Log, Rationale | DACI Matrix, Decision Owner, Decision Log |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ComplexitySensemakingDecision | ArchitectureRationaleDocumentationGovernance | DecisionRolesGovernanceAlignment |