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 |  Facilitation Stakeholder Mapping |  Product Strategy KPI Tree |
|---|---|---|---|---|
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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 90-180 min | 45-90 min | 60–90 min | 90-180 min initial, dann laufend |
Participantsdifferent | 3-6 | 3-12 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | GQM Table, Metric Profiles | Force Field Map, Change Levers, Risk Notes | Stakeholder Map, Engagement Plan, Risk Notes | KPI Tree, Owner List |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | ChangeDecisionStrategy | StakeholdersAlignmentFacilitationChange | MetricsStrategyAlignmentMeasurement |