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 arc42 |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-12 | 2-8 | 1-4 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Decision Rights Matrix, Agreement | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | DecisionGovernanceAlignmentResponsibility | LeanStartupValidationMVP | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance |