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 Request for Comments | ![]() Decision Making Decision Rights Mapping |
|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tagsno overlap | LeanStartupValidationMVP | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






