The Three Things Your Team Needs From You (And Which One You're Probably Ignoring)
You gave them a good job.
Real ownership. Clear direction. You protected their focus, went to bat for them in the resourcing conversations, and made sure the work actually mattered. By every measure you'd have named, you were giving this person what they needed. So when they told you they were leaving — or just quietly stopped bringing the extra — it didn't compute. You weren't neglecting them. You were, if anything, giving them more of exactly the thing you'd have wanted in their seat.
That last part is the tell. You were giving them more of the thing you'd have wanted. Which is not always the thing they needed.
What teams actually run on
In February 2026, a meta-analysis in Stress & Health pulled together 192 studies on what drives durable motivation at work. The finding is unusually clean for this kind of research: when leaders support three basic psychological needs, employee engagement and well-being go up — and when they don't, no amount of perks or pay closes the gap.
The three needs are autonomy (my judgment is trusted, not just my output), competence (I'm effective and getting better, with feedback I can actually use), and relatedness (I'm seen by the people I work with, and the work connects to something). When all three are covered, you rarely have to manage motivation at all; it shows up on its own. When one slips (not craters, just slips), the extra effort is the first thing to go, and what remains is a capable person doing precisely the job and no more.
None of that is new to anyone who's managed for a while. The useful part isn't the list. It's what the list reveals about you.
Your strongest need is a map to your blind spot
Here's the pattern that doesn't get talked about: leaders don't distribute these three needs evenly. You have one you're wired to deliver almost without thinking — the one that matches how you prefer to be led. And because it's effortless for you, you tend to over-invest in it, assume it's what everyone wants, and quietly under-build the other two.
The need you're best at isn't just your strength. It's the clearest clue to the one you're starving. Not because you don't care about the others, but because the one that comes naturally crowds them out of your attention.
That's why the departure blindsides you. You weren't ignoring your team. You were fluent in one language and assumed everyone spoke it.
Three rough portraits. You'll probably recognize which one is yours faster than you'd like.
If competence is your native language, you lead by making people better. You give sharp, specific feedback. You care about craft, standards, and whether the work is actually good. Your team gets sharper working for you — that's real, and people stay for it. What tends to go thin is autonomy. Because you can see the better version of almost any piece of work, you edit, redirect, and tighten the approval loop, all of which reads to a capable person as you don't trust my judgment. You built the skill. You forgot to hand over the wheel.
If relatedness is your native language, you lead through connection. People feel seen by you. Your 1:1s are real conversations, your team likes each other, and the room is warm. That's not soft — it's a genuine retention engine. What tends to go thin is competence, specifically the hard-feedback half of it. The same instinct that makes you attuned makes you reluctant to say the thing that stings, so people feel supported but stop growing. Warmth without stretch has a ceiling, and your best people hit it first.
If autonomy is your native language, you lead by getting out of the way. You hand over the outcome, resist micromanaging, and give people room to run. High performers love working for you. What tends to go thin is relatedness — and sometimes the scaffolding side of competence. "I trust you, go" is the right message for someone already established, and a lonely one for someone still finding their footing. Space you experience as respect, they can experience as absence.
Finding the one you're missing
The move isn't to overhaul how you lead. It's to name the need you deliver on instinct, then treat the other two as the ones that need deliberate attention — because they will not happen on their own for you the way the first one does.
Practically: pick the portrait that fits and look at its blind spot. If you're competence-first, find one decision this week you'd normally shape and hand it over whole — the outcome, not just the task. If you're relatedness-first, deliver one piece of feedback you've been softening, cleanly, because the person is good enough to handle it. If you're autonomy-first, add one touchpoint that isn't about status — a check on the person, not the work.
One aimed adjustment a week does more than an occasional overhaul. And once you're pointed at the right need, it responds faster than you'd guess.
The hard part is that none of this is visible from the inside. Your strongest need feels like good leadership, because from where you sit, it is. The bill lands in someone else's behavior, weeks later, wearing a disguise. Which is exactly why the leaders who catch it early are the ones who get honest about their own pattern before their team has to spell it out for them.
If you want a clearer read on which need your style delivers by default — and which one it's most likely leaving on the floor — the quiz takes about three minutes.
Sources: Hagger & Star — Self-Determination Theory Meta-Analysis of 192 Studies (Wiley / Stress & Health, February 2026) | APA — Self-Determination Theory at 25 Years (March 2026) | Springer / Motivation and Emotion — SDT Special Issue (2026)
