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