The Team Engine

Self-Determination Theory holds that everyone runs on some mix of three needs — Autonomy (the need to act on your own terms), Competence (the need to visibly get better at something hard), and Relatedness (the need to feel connected to the people around you). None of the profiles this test names describes how much of any single need a person has in absolute terms; each describes which needs are pulling hardest relative to the others. For the Team Engine, Relatedness and Competence are running out front together, and Autonomy has fallen behind both. That ordering — not a raw score on any one dimension — is the whole profile, and it is easy to misread: a comparatively lower Autonomy does not mean this person lacks drive or waits to be told what to do. It means the drive is pointed at being excellent inside a group rather than at deciding, alone, where the group should go.

You can watch the wiring in an ordinary stand-up. A Team Engine spends their two minutes on what they shipped and who they unblocked, not on trying to redirect the sprint. Put them on a surgical team, a trading desk, a writers' room, or an engineering pod, and they gravitate to the seat where their specific skill closes a gap the group actually has — the second violin who tunes the section before the conductor has to ask, the scrub nurse who has the next three instruments staged before the surgeon reaches for them, the mid-level associate who quietly becomes the person three other associates route their hardest questions to. None of that requires being the one who decided what the case, the score, or the sprint should be. It requires being reliably good, in public, with other people counting on that goodness.

This also explains what a Team Engine actually needs from autonomy, which is not none — it's simply not the lever that gets them out of bed. Handed a clear brief inside a team they respect, they will run further and faster than a looser, more open-ended mandate would get them, because ambiguity that would energize an Autonomy-led colleague reads to them mostly as time not spent building or belonging. What genuinely derails a Team Engine isn't too little control over direction. It's a team that stops being competent — the standard slips, the collaboration turns political, or the person setting direction stops being someone whose judgment they trust. Take away the team, or take away the skill, and the motivation goes with it; take away who's in charge, and very little changes.

It's worth being precise about how this differs from The Self-Starter, built on the same three needs in a different order — Autonomy and Competence outranking Relatedness. A Self-Starter wants to own the direction and be excellent at it, company optional. A Team Engine wants to be excellent at it and have company, direction optional. Put both on the same project and the difference shows up fast: the Self-Starter drafts the plan and looks for buy-in afterward, most comfortable disappearing to solve the hard piece alone; the Team Engine waits to see what the group converges on and then executes it better than almost anyone else in the room, and would find the Self-Starter's solo-first instinct faintly baffling — why solve the interesting problem without the people who'd make solving it better? Neither is the more ambitious profile. They are ambitious about different things.

Organizationally, this is the profile that makes a strong pod stronger and a weak one bearable for longer than it probably should be. Team Engines tend to do well inside hospital units, research labs, agencies, delivery teams, and any structure where competence is visibly shared and everyone's output touches everyone else's. They do less well in flat, ownership-obsessed cultures that score people by the initiatives they personally originated — a Team Engine can carry an enormous share of the actual work and still read, on paper, as though they contributed less than the person who called the meeting and named the project after themselves. The fix isn't teaching them to want autonomy more. It's making sure the systems that hand out credit can see contribution that never needed to be someone's personal project in order to matter.