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 |  Facilitation Stakeholder Salience Model |  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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Medium | Low | Medium |
Timedifferent | 90-180 min | 60-90 min | 60–90 min | 90-180 min initial, dann laufend |
Participantsdifferent | 3-6 | 3-6 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | GQM Table, Metric Profiles | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes | KPI Tree, Owner List |
Tags1 shared | MetricsMeasurementEngineeringAlignment | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange | MetricsStrategyAlignmentMeasurement |