Engagement measurement / manager action
Gallup Q12 Engagement Model
Gallup’s twelve questions measure the conditions of engagement — from "I know what is expected of me" to "I have opportunities to learn and grow" — ordered as a hierarchy from basic needs to growth.
Its power is managerial: every item is something a team’s manager can actually change.
- Problem
- Engagement measurement / manager action
- Altitude
- Team to enterprise
- Effort to run
- Light
- Evidence base
- Strong
Theory & origin
Gallup distilled the Q12 from decades of workplace interviews and meta-analyses covering millions of employees, selecting the twelve items that best predict business outcomes — productivity, retention, safety, profitability. The items form a rough hierarchy: basic needs (expectations, materials), individual contribution (recognition, doing what I do best), teamwork (opinions count, mission, friends at work), and growth (progress talks, learning). The deliberate constraint is actionability at team level: the unit of engagement is the manager, not the company — which is also the model’s critique of glossy company-wide engagement programmes.
Explore the model
How a consultant runs it
- 01 Run the twelve items and report at team level; company averages hide exactly what the model is built to expose.
- 02 Read results against the hierarchy: a team failing on basic needs cannot be fixed with growth conversations.
- 03 Make managers the owners of their own scores — HR facilitates, managers act, or nothing changes.
- 04 Pick two items per team per cycle, not twelve; engagement moves through focused habits, not action-plan documents.
- 05 Re-measure on a rhythm and tie manager development to movement, not to the absolute score they inherited.
When to use
- 01 Measuring engagement in a way managers can act on team by team
- 02 Diagnosing why attrition or quality problems cluster in specific teams under specific managers
- 03 Replacing a bloated 80-question annual survey nobody acts on
When not to use
- 01 As a company scoreboard divorced from manager action — measurement without ownership breeds cynicism
- 02 When leadership wants the score but has ruled out acting on managers; declining the survey is kinder
- 03 For diagnosing pay or workload problems the twelve items are not designed to catch
Worked example
An operations division of 120 runs the Q12: overall 3.4, unremarkable. Team-level cuts tell the real story — three teams under one senior manager score 2.4 on recognition (Q4) and 2.1 on development encouragement (Q6) while their basic needs score fine. Exit data confirms those teams drive 60% of regretted attrition. The intervention is surgical: recognition rituals and quarterly growth conversations for that manager’s group, coached for two cycles. The three teams recover to 3.6+ within a year; nothing was spent on the teams that were already healthy.
Common pitfalls
- 01 Reporting a company average and calling it insight — the variance between teams is the finding
- 02 Survey-action gap: measuring annually, acting never; scores fall below never-measuring at all
- 03 Treating the score as the goal, inviting managers to campaign for ratings instead of conditions
- 04 Ignoring the hierarchy and prescribing growth conversations to teams missing basic tools
Sample deliverable
One real engagement, end to end — watch the numbers travel from raw input, onto the chart, into the artifact.
Input — raw data
- Q1 — expectations clear4.3 / 5
- Q10 — friend at work3.8 / 5
- Q4 — recognition (7 days)2.4 / 5
- Q6 — development encouraged2.1 / 5
Process — mapped
Item scores are cut by team; the low items against the hierarchy locate the fix
Q12 pulse — Branch Operations, Jakarta region (n=120)
- Cluster3 teams, one senior manager
- Link60% of regretted attrition
- Fixrecognition + growth talks, coached