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 |  Architecture Architecture Decision Record |  Facilitation Decision Jam |  Decision Making Argument Mapping |
|---|---|---|---|---|
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. | 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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-240 min | 15-45 min | 60-90 min | 1-3 h |
Participantsdifferent | 1-6 | 1-3 | 4-10 | 1-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | ADR File, Decision Log, Rationale | Problem Cluster, Prioritized Challenge, Experiment | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureRationaleDocumentationGovernance | FacilitationDecisionProblem solvingWorkshop | SensemakingDecisionRationale |