View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Facilitation Stakeholder Mapping |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | 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 | Low | Low | High |
Timedifferent | 20–45 min | 60–90 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | Small cross-functional group | 2-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Stakeholder Map, Engagement Plan, Risk Notes | 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 | RiskDecisionFailurePlanning | StakeholdersAlignmentFacilitationChange | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
