View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Stakeholder Mapping3-Circle Venn DiagramSAAM (Software Architecture Analysis Method)Stakeholder Salience Model
| Criterion | ![]() Facilitation Stakeholder Mapping | ![]() Facilitation 3-Circle Venn Diagram | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | When three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 60–90 min | 15-45 min | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min |
Participantsdifferent | 2-8 | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Stakeholder Map, Engagement Plan, Risk Notes | Venn Diagram, Overlap Notes, Differentiators | 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 | Salience Diagram, Strategy per Class |
Tagsno overlap | StakeholdersAlignmentFacilitationChange | ComparisonFacilitationAlignment | ArchitectureChangeAnalysisComparisonQuality | StakeholdersFacilitationAlignmentGovernance |



