View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Lean Startup |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | Medium | Medium | Low | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | 2–4 h review as a planning range; preparation and evaluation additional | 15-30 min | 1-4 h |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | LeanStartupValidationMVP | ArchitectureEngineeringFeedbackValidationTasks | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |