View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordHypothesis-Driven TroubleshootingLean StartupA3 Problem Solving
| Criterion |  Architecture Architecture Decision Record |  Engineering Hypothesis-Driven Troubleshooting |  Innovation Lean Startup |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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 systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 30-240 min | Wochen bis Monate je Lernzyklus | 45-90 min |
Participantsdifferent | 1-3 | 1-6 | 2-8 | 2-5 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TroubleshootingProblem solvingDiagnosis | LeanStartupValidationMVP | LeanProblem solvingCoachingOperations |