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 Systems Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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 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 | Medium | High | Low |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | 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 | Force Field Map, Change Levers, Risk Notes |
Tags1 shared | Systems thinkingMappingBoundariesChange | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
