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) |  Decision Making Decision Framing Workshop |  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. | When a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins. | 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 | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-120 min | 60–90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 4-10 | 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 | Decision Frame, Decision Question, Criteria List, Evidence Plan | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Decision framingAlignmentCriteriaOptions | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
