A team of eight scored 2.7 on competence—the lowest dimension on their survey. People were handling client projects beyond their training with no support structure. Every new request felt like a test they might fail. Seeing this, the team leader began pairing experienced members alongside those tackling unfamiliar work, and when deliverables missed the mark, asked "what did we learn?" instead of "what went wrong?"
Ten weeks later, competence hit 3.8. But the number wasn't the real shift. People started volunteering for work they used to avoid. Skeptics say surveys don't change anything—and for surveys that sit in a dashboard, they're right. Surveys that lead to action tell a different story.
Competence: from avoidance to volunteering
The client services team above had a pattern common in growing organizations. Workload expanded faster than skills. New project types kept arriving—data visualization, automation requests, deliverables nobody had ever done. People could have learned on the job, but mistakes were treated as performance problems. The unspoken rule was that struggling meant you weren't up to the job.
All of that showed up as a 2.7 on competence. The team didn't feel effective, not because they lacked talent, but because every unfamiliar task was a risk. The metric-level breakdown told the rest of the story: not skill gaps, but the daily feeling of being in over your head with no safety net.
So management created a net. Pairing someone who'd done a project type before with someone who hadn't—with the understanding that both would learn—ensured nobody faced unfamiliar work alone. Mistakes were no longer evidence of incompetence. Within weeks, the two senior members who'd been absorbing all the unfamiliar requests stopped being the default—others started picking up stretch work on their own.
Autonomy: from escalation to ownership
A ten-person operations team scored 2.4 on autonomy. Every process followed a rigid script. When a client situation didn't fit the standard workflow, the team escalated—not because the problem was hard, but because deviating from the script required approval. People had stopped thinking about how to solve problems and started thinking about how to route them.
The leader tried something uncomfortable: defined outcomes for each process and let the team redesign how they got there. No new scripts—just boundaries. "Delivery within 48 hours, client confirms satisfaction" replaced a twelve-step procedure manual. The team rebuilt their own workflows over the next month, and when edge cases appeared, they handled them instead of passing them up.
Twelve weeks later, autonomy moved from 2.4 to 3.6. The shift showed up before the re-survey: daily escalation emails stopped. Problems that used to queue in someone's inbox got solved at the source.
Belongingness: from silos to early warnings
A nine-person project coordination team scored 2.5 on belongingness. The root cause wasn't distance or poor communication tools—it was blame. When a project slipped, the first response was always "whose responsibility was this?" People had learned to work in silos because isolation offered protection. If you didn't depend on anyone, nobody could point at you when something went wrong.
The leader stopped asking "who dropped the ball?" and started asking "what would have prevented this?" In team meetings, they owned their mistakes first: "I underestimated the timeline on this one, and it put pressure on the handoff."
Ten weeks later, belongingness moved from 2.5 to 3.7. People started flagging risks early. A coordinator noticed a resource conflict two weeks out and raised it in a team meeting—something that would have stayed hidden before, surfacing only as a missed deadline with someone's name attached.
The compounding effect
The first survey cycle in any team produces cautious answers. People test whether it's safe. They give honest-enough scores but hold back the sharpest observations—especially about leadership. When the leader acts on results visibly, the second cycle shifts. Responses get more specific. "Things are fine" turns into "I don't get feedback after I finish a project, and it makes me wonder if anyone noticed"—because people saw the first round lead to real change.
By the third cycle, teams stop treating the survey as data the leader reads and start treating it as a shared diagnostic. People bring solutions alongside problems. A team member flags "belongingness dropped—I think it's because we stopped doing cross-project check-ins after the reorg" before the leader even opens the results. Teams that survey without acting see the opposite—perfunctory answers, declining quality, the survey becoming evidence that feedback goes nowhere.
Motiro tracks the trajectory
Most survey tools show a snapshot. Motiro shows trajectory. When a team re-surveys after acting on results, it tracks how each dimension shifted—which interventions moved which metrics, and by how much. A leader doesn't have to remember what changed between cycles or guess whether that autonomy initiative worked. The data shows the arc.
The Journey makes the commitment visible over time. When a leader identifies issues and builds an action plan, the whole team follows the progress—not just the initial scores, but the movement across cycles. "Competence was 2.7, we paired people on unfamiliar work, now it's 3.8" becomes a concrete record, not a story someone tells from memory. Over multiple cycles, patterns emerge: which types of interventions produce the fastest shifts, which dimensions prove most resistant, where the team's real leverage sits.
What's next
To understand the science behind autonomy, belongingness, and competence, read What Keeps Teams Motivated, According to 40 Years of Research. To learn how to run a survey that surfaces real answers, start with How to Uncover What Your Team Won't Tell You. If you have your scores and want to act on them, see Your Survey Results Are In. Now What?.