← The library

Engagement measurement / manager action

Gallup Q12 Engagement Model

Gallup's twelve questions measure the conditions for engagement, from "I know what is expected of me" to "I have opportunities to learn and grow," ordered as a hierarchy from basic needs up to growth.

Its real power is that every single 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, picking the twelve items that best predict business outcomes like productivity, retention, safety, and profitability. The items form a rough hierarchy: basic needs (expectations, materials), individual contribution (recognition, doing what I do best), teamwork (opinions counting, mission, friends at work), and growth (progress talks, learning). The deliberate design choice 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 programs.

Key components

The parts at a glance. Click any term for the full definition, a field example, and the common failure, in the model below.

Explore the model

How a consultant runs it

  1. 01 Run the twelve items and report them at team level. Company averages hide exactly what the model is built to expose.
  2. 02 Read results against the hierarchy. A team failing on basic needs cannot be fixed with growth conversations.
  3. 03 Make managers the owners of their own scores. HR facilitates, managers act, or nothing changes.
  4. 04 Pick two items per team per cycle, not twelve. Engagement moves through focused habits, not through action-plan documents.
  5. 05 Re-measure on a rhythm, and tie manager development to movement, not to the absolute score they inherited.

When to use

  1. 01 Measuring engagement in a way managers can actually act on, team by team
  2. 02 Diagnosing why attrition or quality problems cluster under specific teams and specific managers
  3. 03 Replacing a bloated 80-question annual survey nobody ever acts on

When not to use

  1. 01 As a company scoreboard divorced from manager action. Measurement without ownership just breeds cynicism.
  2. 02 When leadership wants the score but has already ruled out acting on managers. Skipping the survey is kinder.
  3. 03 For diagnosing pay or workload problems. The twelve items were not designed to catch those.

Worked example

An operations division of 120 people runs the Q12 and gets an unremarkable overall score of 3.4. Cutting the data by team tells 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 over two cycles. The three teams recover to 3.6 or better within a year. Nothing was spent on the teams that were already healthy.

Common pitfalls

  1. 01 Reporting a single company average and calling it insight. The variance between teams is the actual finding.
  2. 02 The survey-action gap: measuring every year, acting on it never. Scores end up worse than never measuring at all.
  3. 03 Treating the score itself as the goal, which just invites managers to campaign for ratings instead of fixing conditions
  4. 04 Ignoring the hierarchy and prescribing growth conversations to teams that are still missing basic tools

Sample deliverable

One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.

Q12 pulse: Branch Operations, Jakarta region (n=120)

Input

  • Q1: expectations clear4.3 / 5
  • Q10: friend at work3.8 / 5
  • Q4: recognition (7 days)2.4 / 5
  • Q6: development encouraged2.1 / 5

Process

Item scores are cut by team, and the lowest items against the hierarchy locate the fix

OutputDeliverable

Q12 pulse: Branch Operations, Jakarta region (n=120)

  • Cluster3 teams, one senior manager
  • Link60% of regretted attrition
  • Fixrecognition plus coached growth talks

Sources

Next in the library Recruiting Funnel