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 TroubleshootingArgument MappingDecision Rights MappingArchitecture Decision Record
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Decision Making Argument Mapping |  Decision Making Decision Rights Mapping |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 30-240 min | 1-3 h | 90-180 min | 15-45 min |
Participantsdifferent | 1-6 | 1-8 | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Argument Map, Evidence Gaps, Decision Rationale | Decision Rights Matrix, Agreement | ADR File, Decision Log, Rationale |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | SensemakingDecisionRationale | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance |