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 |  Innovation Lean Startup |  Operations 5 Whys |
|---|---|---|---|---|
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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-240 min | 15-45 min | Wochen bis Monate je Lernzyklus | 15-30 min |
Participantsdifferent | 1-6 | 1-3 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | ADR File, Decision Log, Rationale | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Root cause notes, Countermeasures |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureRationaleDocumentationGovernance | LeanStartupValidationMVP | Root causeIncidentLeanProblem solving |