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 |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Force Field Analysis |
|---|---|---|---|
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. | 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 | Low | High | Low |
Timedifferent | 20–45 min | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | Small cross-functional group | Architecture experts and stakeholders for scenarios and weighting | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | 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 |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
