View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)OODA LoopRequest for CommentsForce Field Analysis
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making OODA Loop |  Architecture Request for Comments |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 15-60 min je Zyklus | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-8 | 3-20 Reviewer | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Situation Assessment, Decision Loop, Action Updates | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | DecisionChangeLearningStrategy | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy |