View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Pareto AnalysisSAAM (Software Architecture Analysis Method)Alignment MappingStakeholder Mapping
| Criterion |  Decision Making Pareto Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation Alignment Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 | Low | High | Medium | Low |
Timedifferent | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h | 60–90 min |
Participantsdifferent | 1-6 | Architecture experts and stakeholders for scenarios and weighting | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | PrioritizationQualityFocusRoot cause | ArchitectureChangeAnalysisComparisonQuality | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |