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 |  Operations 8D Problem Solving |  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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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 | High | Medium |
Timedifferent | 90-180 min | 1-6 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-12 | 4-10 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Decision Rights Matrix, Agreement | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | DecisionGovernanceAlignmentResponsibility | QualityProblem solvingRoot cause | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
