View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile WSJF |  Innovation Lean Startup |  Architecture Architecture Decision Record |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 45-90 min | Wochen bis Monate je Lernzyklus | 15-45 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-10 | 2-8 | 1-3 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | ADR File, Decision Log, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | LeanEconomicsSequencePrioritization | LeanStartupValidationMVP | ArchitectureRationaleDocumentationGovernance | ArchitectureEngineeringFeedbackValidationTasks |