A leader pulls up the team's latest survey results. Motivation: 3.6 out of 5. Not great, not terrible. Tab closed, a mental note to "work on engagement," and on to the next meeting. Six weeks later, the team's two strongest people have stopped speaking up in meetings and started turning down new work. The results had been pointing at the problem all along. The leader just never read past the top number.
If you've measured the three needs that drive motivation with a survey that surfaces real answers, you have results like these. What matters is what you do with them. Here's how to read them at the right depth and turn them into action.
The headline score tells you how, not why
That 3.6 is the team's Motivation score: how energized and committed people feel about the work. It's the outcome, and on its own it's a dead end. It says the team is somewhere in the middle, not what's holding them there.
Whether 3.6 is even good depends on context the number can't supply: how it compares to a benchmark of thousands of teams, and to your own team's last cycle. A 3.6 climbing from 3.0 means something very different from a 3.6 sliding down from 4.2.
Three scores underneath it explain the outcome. Needs is whether the team has the autonomy, belongingness, and competence that motivation runs on. Leadership and Environment are the two levers that feed or starve those needs. These scores rest on Self-Determination Theory. What Keeps Teams Motivated explains the science; here, we just read the results.
What you see first
The outcome. Looks unremarkable.
Why
Leadership is in crisis. The outcome score hid it.
Read together, the three scores tell a story the 3.6 buried: needs and environment are healthy, leadership is in crisis. A team with strong needs and a weak manager calls for a different fix than a team with the reverse, and the outcome score can't tell them apart.
The team was poorly led. The Motivation score didn't say so. The scores beneath it did.
Zoom into the metrics
A low score tells you where to look, not what to fix. Leadership at 2.8 could mean the manager doesn't show understanding when people struggle, doesn't encourage effort, or doesn't listen. Each is a different problem with a different fix. To find which one, read a level deeper, into the metrics.
Leadership score
Something is wrong. But what?
The metrics
Encouragement is the problem. Now you know what to fix.
The specific metric changes everything. This leader needs to work on one thing: how they respond to effort. The team pushes through a hard week and hears nothing. Mistakes trigger problem-solving before anyone says "good try." Progress goes unremarked. The daily signal is that effort doesn't register, and people who feel unrecognized stop putting it in.
One metric, one behavior to change. The hard part is resisting the urge to trust your gut about which one.
Your instincts will mislead you
When leaders see a low score, they default to the fix that matches their own values: the one who prizes autonomy grants more freedom, the one who prizes connection schedules social events. The instinct is fast and confident, and it reflects what the leader would want, not what the data says the team needs. One manager threw team lunches at a problem that was really closed-door decision-making. Another granted more freedom when what the team was missing was any sign their work mattered. Both meant well. Both made the problem worse. Your team's needs are in the data, not your gut.
Build a focused plan
Pick one score. Before deciding what to do, share the full results with the team. They have context the numbers can't capture. A leader might read "encouragement: 1.9" as "people want more praise," while the team says it's about how mistakes are handled: when something goes wrong, the first response is blame, not support. That conversation often reveals more than the scores themselves.
Then choose concrete actions aimed at the specific metric. Small, visible, sustainable: habits you can keep, not programs that fade after a month.
- Low encouragement → name effort explicitly in 1-on-1s and standups, not just outcomes
- Low autonomy → remove the approval step on routine decisions
- Low belongingness → a weekly 15-minute peer check-in, no agenda required
That last line matters most. When a leader makes the plan visible and asks to be held to it, the dynamic shifts: the team isn't just supplying data, they're part of the response. Feedback stops being something the leader reads in private and becomes a shared commitment with a visible trajectory.
Close the loop
Re-survey in 8–12 weeks and check the one metric you targeted. That leader reworked their 1-on-1s around a single change: opening with "what went well this week?" instead of "what's blocked?" They named specific contributions in standups instead of jumping to the next task. Eight weeks later, encouragement had climbed from 1.9 to 3.1. The team felt the shift in the room before the data confirmed it.
If the score doesn't move, don't jump to a new one. Try a different action on the same metric: the diagnosis was right, the intervention needs adjusting. Surveying on that cadence keeps the cycle tight enough to catch drift without wearing people out.
One cycle is the start, not the finish. What Changes After a Team Actually Acts on Survey Results follows three teams across several cycles: what moved, how fast, and what the later cycles unlock.
How Motiro does the hard parts
Two steps here are the ones leaders aren't trained for: naming what's really behind a low score, and choosing a fix that fits. Guessing tends to go wrong. Motiro's AI does both. When a survey closes, it reads the scores together and surfaces the specific issue behind each one: not "leadership is low," but "people don't feel their effort is acknowledged when something goes wrong." Then, as you build the plan, it checks each action against what motivation research says works, and flags a mismatch before you commit.
The rest is shared by design: everyone on the team sees the results and how their own answers compare to the group, the plan lives in a Journey the team can follow, and each person gets a private report tying it back to what they reported. The cycle stops depending on one leader's discipline.
What's next
To see how this works inside Motiro, start with the full walkthrough: How Motiro works. For deeper reading: once you've read your scores, What Changes After a Team Actually Acts on Survey Results follows three teams cycle after cycle. For the science underneath, read What Keeps Teams Motivated, and Why Leaders Misread It. And to run a survey that surfaces real answers in the first place, see How to Uncover What Your Team Won't Tell You.