View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Product Strategy OKRs |  Team Design Spotify Model Mapping |  Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When strategic direction needs to become measurable, it connects ambition with checkable results. It makes goals connectable to focus and review. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 1-2 h Setup | 90-180 min | 90-180 min |
Participantsdifferent | 3-12 | 2-20 | 5-15 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | OKR set, Measurement plan, Review cadence | Spotify Model Map, Action List | GQM Table, Metric Profiles |
Tags1 shared | AlignmentStakeholdersTeam | GoalsAlignmentOutcomesMeasurement | TeamOrganizationAlignmentDiagnosis | MetricsMeasurementEngineeringAlignment |