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 Request for Comments |  Innovation Lean Startup |  Decision Making Decision Rights Mapping |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Wochen bis Monate je Lernzyklus | 90-180 min | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 4-12 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Decision Rights Matrix, Agreement | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | LeanStartupValidationMVP | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance |