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 |  Decision Making OODA Loop |  Facilitation Stakeholder Mapping |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-60 min je Zyklus | 60–90 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | 1-8 | 2-8 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Situation Assessment, Decision Loop, Action Updates | Stakeholder Map, Engagement Plan, Risk Notes | Decision Rights Matrix, Agreement |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | DecisionChangeLearningStrategy | StakeholdersAlignmentFacilitationChange | DecisionGovernanceAlignmentResponsibility |