View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Impact Mapping8D Problem SolvingArchitecture Decision RecordATAM (Architecture Tradeoff Analysis Method)
| Criterion | ![]() Product Strategy Impact Mapping | ![]() Operations 8D Problem Solving | ![]() Architecture Architecture Decision Record | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 45-90 min | 1-6 Wochen | 15-45 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 4-10 | 1-3 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | ADR File, Decision Log, Rationale | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | QualityProblem solvingRoot cause | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskTradeoffsStakeholders |



