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) |  Business Strategy GAP 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 2-8 |
Formatsame | Workshop + async | Workshop + async | 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 | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | LeanStartupValidationMVP | ArchitectureEngineeringFeedbackValidationTasks | StrategyAnalysisPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
