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 Intervention Mapping | ![]() Decision Making Pareto Analysis | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. | 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. |
Complexitydifferent | High | Low | High |
Timedifferent | 1-5 Tage | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 4-12 | 1-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Pareto Chart, Top Causes, Focus List | 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 |
Tagsno overlap | ChangeSystems thinkingCapability | PrioritizationQualityFocusRoot cause | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






