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) |  Systems Thinking Wardley Mapping |  Systems Thinking Leverage Points |
|---|---|---|---|
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. | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. |
Complexitydifferent | High | Medium | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h | Half day |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
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 | Wardley Map, Strategic Options, Evolution Notes | Leverage Map, Action Strategy |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | StrategySystems thinkingDynamics | Systems thinkingChangeStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
