View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Impact Mapping |  Decision Making Force Field Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 45-90 min | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 20–45 min |
Participantsdifferent | 3-8 | 3-12 | Evaluation team, architects, and relevant stakeholders | Small cross-functional group |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | Force Field Map, Change Levers, Risk Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | ChangeDecisionStrategy | ArchitectureQualityRiskTradeoffsStakeholders | RiskDecisionFailurePlanning |