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 Discovery Working Backwards | ![]() Engineering Goal Question Metric | ![]() Facilitation Stakeholder Salience Model | ![]() Product Strategy KPI Tree |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 4-8 h, mehrere Iterationen | 90-180 min | 60-90 min | 90-180 min initial, dann laufend |
Participantsdifferent | 2-6 | 3-6 | 3-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | GQM Table, Metric Profiles | Salience Diagram, Strategy per Class | KPI Tree, Owner List |
Tags1 shared | VisionNarrativeAlignment | MetricsMeasurementEngineeringAlignment | StakeholdersFacilitationAlignmentGovernance | MetricsStrategyAlignmentMeasurement |



