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 |  Engineering Fault Isolation |  Architecture Request for Comments |  Facilitation Decision Jam |
|---|---|---|---|---|
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. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-240 min | 30-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min |
Participantsdifferent | 1-6 | 1-6 | 3-20 Reviewer | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | TroubleshootingDiagnosisEngineering | ArchitectureDecisionAsyncGovernance | FacilitationDecisionProblem solvingWorkshop |