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 |  Product Strategy KPI Tree |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Engineering Goal Question Metric |
|---|---|---|---|---|
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. | When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 45-90 min | 90-180 min initial, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 90-180 min |
Participantsdifferent | 3-8 | 3-8 | Evaluation team, architects, and relevant stakeholders | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | KPI Tree, Owner List | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | GQM Table, Metric Profiles |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | MetricsStrategyAlignmentMeasurement | ArchitectureQualityRiskTradeoffsStakeholders | MetricsMeasurementEngineeringAlignment |