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 SAAM (Software Architecture Analysis Method) |  Business Strategy Business Model Stress Test |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | High | High | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | Half day | 60–90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
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 | Stress Test Report, Action Plan per Scenario | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | StrategyBusiness modelRiskDiagnosis | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
