View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Goal Question Metric |  Decision Making Force Field Analysis |  Product Strategy KPI Tree |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 90-180 min | 45-90 min | 90-180 min initial, dann laufend | 1-2 h |
Participantsdifferent | 3-6 | 3-12 | 3-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | GQM Table, Metric Profiles | Force Field Map, Change Levers, Risk Notes | KPI Tree, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | ChangeDecisionStrategy | MetricsStrategyAlignmentMeasurement | AlignmentStakeholdersStrategyFacilitation |