Results Driver: you push the group toward action
You push the group toward action and results: it’s hard for you to watch a stalled task without stepping in to move it forward.
When a conversation drags on without any concrete decisions, you’re usually the one asking, “so, what are we actually doing?”
Task versus climate: Bales’s distinction
In 1950, social psychologist Robert Bales observed small groups in discussion and coded every contribution with his Interaction Process Analysis. That work produced a distinction still in use today: there are behaviors in the task area (suggesting, giving opinions, orienting, deciding) and behaviors in the socioemotional area (supporting, releasing tension, showing agreement or disagreement).
“Results driver” is the name our test uses, not a role defined by Bales. What it does take from his work is that orientation: this profile’s main contribution is keeping momentum toward the goal, even when everyone else gets stuck in discussion.
Belbin’s Shaper
This profile’s closest relative in the management literature is the Shaper role that Meredith Belbin described in Management Teams (1981), after years of watching teams in business simulation games at Henley Management College in the UK.
Belbin describes it as a challenging, dynamic role that thrives under pressure and has the drive to overcome obstacles. And, as he does with every role, he assigns it an “allowable weakness”, the reasonable price of its strength: it can be quick to rise to provocation and may hurt people’s feelings without meaning to.
Belbin is best read with due caution. His model is very popular in companies, but when Furnham, Steele and Pendleton (1993) analyzed his self-perception inventory, they found unconvincing reliability coefficients and a factor structure that didn’t reproduce the proposed roles well. It’s a useful vocabulary for talking about contributions to a team, not a precise measure of them.
How this role shows up
- You actively step in to steer long conversations toward a concrete decision.
- Execution takes priority over prolonged discussion, especially when the deadline is tight.
- You quickly spot stalled tasks and propose, without waiting for someone else to, how to unblock them.
- The team’s energy tends to rise when this role is present and active.
An example: a team preparing a website launch has spent two meetings debating the color of the main button. The results driver proposes a one-week A/B test and sets the decision date. The team leaves the meeting with a task, not with a third meeting.
Speed and psychological safety
This role’s blind spot is pace, and Amy Edmondson’s research helps explain why it matters. In a study of 51 teams at a manufacturing company, published in 1999, Edmondson defined psychological safety as the shared belief that the team is safe for interpersonal risk-taking: asking a question, admitting a mistake, raising a doubt.
Teams with more psychological safety showed more learning behaviors (asking for feedback, discussing errors, seeking information), and those behaviors in turn accounted for their better performance.
For the results driver, the implication is direct: when every objection is experienced as a brake, the team learns to keep its doubts to itself, and some of those doubts were exactly the ones that would have prevented a costly mistake. A short question before closing (“does anyone see something we’re missing?”) protects speed, because the setbacks that come later usually cost more than the two minutes it takes to ask.
Along the same lines, coach Marshall Goldsmith describes how the traits that lead to success (in this case, drive) can become an obstacle as responsibility grows; we explore this in the inspirational leader profile.
If your main contribution to the team is more about tending the climate and relationships than pushing toward results, check out the cohesion builder role.
You can go back to your full result in the What’s My Team Role? test.
Sources
- Bales, R. F. (1950). Interaction Process Analysis: A Method for the Study of Small Groups. Addison-Wesley.
- Belbin, R. M. (1981). Management Teams: Why They Succeed or Fail. Heinemann.
- Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999
- Furnham, A., Steele, H. & Pendleton, D. (1993). A psychometric assessment of the Belbin Team-Role Self-Perception Inventory. Journal of Occupational and Organizational Psychology, 66(3), 245-257. https://doi.org/10.1111/j.2044-8325.1993.tb00535.x
- Goldsmith, M. & Reiter, M. (2007). What Got You Here Won’t Get You There: How Successful People Become Even More Successful. Hyperion.
Want to know more about yourself?
Discover your result with one of our related tests.
Frequently asked questions
Where does the distinction between task-oriented and people-oriented roles come from?
From Robert Bales's pioneering work (1950) on small-group dynamics, which separated two broad areas of behavior in any team: the kind oriented toward moving the task forward and the kind oriented toward tending the group's climate. The name "results driver" is a label from our test; its closest relative in the management literature is Meredith Belbin's Shaper role (1981).
Does a team always need someone in this role?
It almost always helps: without someone pushing toward action, teams with a lot of discussion and little decision-making can easily stall out.
Can this role come across as annoying to others?
It can, if the push toward results doesn't leave room for process or for other team members' legitimate doubts.
Is this the same as being the team's leader?
Not necessarily. You can drive results from any position on a team, without holding the formal leadership role.
Is Belbin's team-role model scientifically validated?
Only partly. It's widely used in companies, but psychometric analyses of its original inventory, such as the one by Furnham, Steele and Pendleton (1993), found modest reliability and an unclear factor structure. It works as a vocabulary for talking about contributions to a team, not as a precise measure.