View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)OODA LoopBusiness Model Stress TestForce Field Analysis
| Criterion | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Decision Making OODA Loop | ![]() Business Strategy Business Model Stress Test | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 15-60 min je Zyklus | Half day | 45-90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-8 | 3-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Situation Assessment, Decision Loop, Action Updates | Stress Test Report, Action Plan per Scenario | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | DecisionChangeLearningStrategy | StrategyBusiness modelRiskDiagnosis | ChangeDecisionStrategy |



