View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Soft Systems Methodology |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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 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 | 0.5-3 Tage | Preparation, scenario analysis, and findings review; effort depends on scope | 60–90 min |
Participantsdifferent | 5-15 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | 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 | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | ArchitectureChangeAnalysisComparisonQuality | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
