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 TroubleshootingArchitecture Decision RecordDecision JamRequest for Comments
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture Architecture Decision Record |  Facilitation Decision Jam |  Architecture Request for Comments |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-240 min | 15-45 min | 60-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-6 | 1-3 | 4-10 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | ADR File, Decision Log, Rationale | Problem Cluster, Prioritized Challenge, Experiment | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureRationaleDocumentationGovernance | FacilitationDecisionProblem solvingWorkshop | ArchitectureDecisionAsyncGovernance |