A team of eight scored 2.8 on competence, the lowest score on their survey. The work was solid, but it vanished the moment it shipped: nobody downstream said whether it helped, results surfaced months later if at all, and a careful job drew the same silence as a rushed one.
Ten weeks later, competence had climbed to 3.8, and the team's work no longer disappeared the moment it left their hands. Skeptics say surveys change nothing. For a survey that sits in a dashboard, they're right. A survey a team acts on tells a different story.
How did the team know what to change? That question separates a survey that helps from one that gathers dust. Motiro measures motivation as the outcome of a small machine. That score captures how wholeheartedly people work, not how hard. Three psychological needs are the engine: autonomy, belongingness, and competence. Two levers feed or starve them: the leadership around the team, and the work environment. So a low need score is a symptom, not a diagnosis. The low 2.8 competence score showed that need was being starved, but not what was starving it. The cause is in one of the levers, which is where a leader can actually act.
Finding the right lever is where instinct misleads. When a survey closes, Motiro reads the team's scores, cross-references them, and names the specific issue behind a low number, with the evidence for it. You shape your action plan from there. Let's explore three stories where the survey pointed to the real lever and the team moved it.
Competence: from invisible work to visible progress
An eight-person client-services team scored 2.8 on competence. The puzzle was why: these were capable people doing solid work. What they lacked was any signal that it mattered. Projects left their hands and the team rarely heard what happened next, and recognition for a job done well was just as rare.
That score was the symptom. To find the cause, Motiro's AI cross-referenced the team's scores. The leadership lever was healthy, with a supervisor who was present and supportive, so the drag was on the environment lever, where returns and rewards sat low: effort produced no visible result, and good work drew no recognition. The AI flagged the connection: competence is a felt sense, fed by the work answering back, and here it never did. With that clue, the leader saw it: people couldn't feel themselves getting better because nothing told them they were.
The suggested fix was to make the work visible, and the leader built that loop for the team: a short monthly review where each project's outcome was traced and named, what it changed for the client, what it taught the team. Careful work and rushed work stopped drawing the same silence. People could finally see their effort produce something, and within weeks they were taking on harder problems on their own.
Ten weeks later, the re-survey put a number on it:
Autonomy: from escalation to ownership
A ten-person operations team scored 2.4 on autonomy. Every process followed a rigid script. Anything outside the standard workflow got escalated, not because it was hard, but because deviating required approval. People had stopped solving problems and started routing them.
Again the AI cross-referenced the scores and put the drag on the leadership lever, not the environment: the team didn't feel free to decide how its own work got done. What the numbers couldn't show, the leader could: every routine call waited on their sign-off, authority funneled through one desk.
So the leader changed the habit, not the team, defining the outcome for each process and letting the team redesign the path to it. No new scripts, just boundaries. "Delivery within 48 hours, client confirms satisfaction" replaced a twelve-step procedure manual. The team rebuilt its own workflows and handled edge cases instead of passing them up. Escalation emails stopped well before the re-survey.
Twelve weeks later, the score caught up:
Belongingness: from silos to early warnings
A nine-person project coordination team scored 2.5 on belongingness. The easy guess was distance or weak tools. The AI pointed elsewhere, to the leadership lever. The specific reason was the team's to name: when a project slipped, the first response from the top was "whose responsibility was this?" People worked in silos because isolation was protection: depend on no one, and no one can blame you when something breaks.
The fix lived in how setbacks were handled, so that is what changed. The leader stopped asking "who dropped the ball?" and started asking "what would have prevented this?" In team meetings, the leader named their own mistakes first: "I underestimated the timeline here, and it put pressure on the handoff." Blame lost its grip, and the silos lost their purpose. People began flagging risks early. A coordinator caught a resource conflict two weeks out and raised it, instead of letting it surface later as a missed deadline with a name attached.
Ten weeks later, the re-survey agreed:
One honest note these clean wins can hide: the first action doesn't always move the score. When it stalls, rework the action on the same lever before abandoning the diagnosis.
The compounding effect
The first survey cycle produces cautious answers. People test whether honesty is safe, giving fair scores but holding back their sharpest observations. When a leader acts on the results visibly, the next cycle shifts: "things are fine" becomes "I don't get feedback after I finish a project, and I wonder if anyone noticed."
By the third cycle, the survey is no longer data the leader reads; it is a shared diagnostic. People bring solutions with their problems, sometimes naming the lever before the leader opens the results. Teams that survey without acting get the opposite: perfunctory answers and a sense that feedback goes nowhere.
Motiro tracks the trajectory
Most survey tools show a snapshot. Motiro shows the arc. When a team re-surveys after acting, it tracks how each score shifted, which action moved which lever, and by how much. No more remembering what changed between cycles, or guessing whether an initiative worked.
This lives in the Journey that opens the moment a survey closes. The team follows the plan and the movement across cycles, not just the opening scores. "Competence was 2.8, we started naming what each project changed, now it's 3.8" becomes a record rather than a story told from memory. Over several cycles, the pattern emerges: which actions move a lever fastest, and where the team's real leverage sits.
What's next
To see how this works inside Motiro, start with the full walkthrough: How Motiro works. For deeper reading: to understand the science behind autonomy, belongingness, and competence, read What Keeps Teams Motivated, and Why Leaders Misread It. To collect feedback honest enough to act on, start with How to Uncover What Your Team Won't Tell You. And to read a fresh set of scores at the right depth, see Your Survey Results Are In. Now What?.