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 Views and Beyond | ![]() Decision Making OODA Loop | ![]() Architecture Request for Comments | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Tage | 15-60 min je Zyklus | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h |
Participantsdifferent | 1-4 | 1-8 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Situation Assessment, Decision Loop, Action Updates | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | DocumentationStakeholdersArchitecture | DecisionChangeLearningStrategy | ArchitectureDecisionAsyncGovernance | AlignmentStakeholdersStrategyFacilitation |



