View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Innovation Lean Startup |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
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. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | Wochen bis Monate je Lernzyklus | 15-30 min | 1-4 h |
Participantsdifferent | 1-3 | 2-8 | 2-6 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanStartupValidationMVP | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |