Why Your Team Isn't Following You (And It's Not Motivation)

Years ago, I was appointed manager of IT while I was still manager of finance. Two departments, one of which I understood, and one where my knowledge of the intragoogles was sketchy at best. I could run a budget forecast in my sleep. It came as a great surprise to learn a firewall is not, in fact, a physical wall.

I braced for the team to see through me in a week. Instead, that team ended up performing better than I expected, and better than I deserved credit for.

I couldn't fake technical credibility, so I didn’t try. In every conversation I described the problem in front of us as plainly as I could, and I described where we needed to get to, and then I stopped talking. I didn't pretend to know the path between the two. I didn't need to. They knew it far better than I ever would, and because I wasn’t in their way, they just ran with it. My job was naming the gap and holding the aspiration steady. Theirs was closing it.

That arrangement held for the rest of my time in the role, and it reminded me of something about why people actually follow a leader. I knew that team wasn't following me because I'd inspired them or because IT was suddenly a thrilling place to work. They were following because I'd been honest about what I didn't know, clear about what mattered, and out of their way on how to deliver it. That's not motivation. That's a rational response to a leader who isn't pretending. Once that trust was there, the energy that used to go into working around a leader went into the actual problem instead.

Most leaders treat followership as an emotional problem. Get people excited enough, inspired enough, "bought in" enough, and they'll move. It's a comforting theory because it puts the fix entirely in the leader's hands, a better speech, a bigger vision, a punchier value statement, none of which require you to admit what you don't know.

But followership isn't emotional. It's structural. People follow leaders who give them two things: an honest read of the problem, and enough room to bring their own expertise to it. Take either one away and no amount of enthusiasm covers the gap. If you fake competence you don't have, your team spends their energy managing you instead of the problem. If you hoard the "how" because you think that's what leadership looks like, you've hired experts and then told them their expertise doesn't count. Either way you've made followership harder, not easier, and you've done it in the name of trying to look like a leader.

The practical version of this is simpler than most leadership advice, which is probably why it gets skipped. State the current problem in plain terms, no softening, no jargon borrowed from a domain you don't own. State where you need to land, specifically enough that people know what "done" looks like. Then hand the middle to the people who actually know it, because you know you're unable to bring further clarity or technical know-how. Notice when you're about to weigh in on something you don't understand, and don't.

This is uncomfortable for capable people, because most of us got promoted by having answers, not by admitting we'd run out of them. But a leader who can say "I don't know how, you do" builds more trust in that sentence than in a year of engagement initiatives. Your team isn't grading whether you can do their job. They're grading whether you'll get in the way of them doing it.

I see the same three things show up consistently with the leaders I work with. All three are uncomfortable, but they'll build buy-in faster than a motivational poster and a tray of free muffins ever will.

The Relevance Trap

More often than anyone wants to admit, being needed matters more to a leader's identity than the team actually succeeding. Ouch! It shows up as the leader who's still in every decision, still the one signing off on things the team is entirely capable of running without them. Not sure if this is you? Count how many decisions this month genuinely needed you versus how many just went through you out of habit. If the second number's bigger, that's not diligence. That's protecting your own relevance at your team's expense.

Trust's Evil Twin

Delegation and abdication look identical from the outside, and most leaders can't honestly tell you which one they're doing. Followership survives real delegation, because the team knows you're still there if it goes wrong. It doesn't survive abdication, because the team learns you'll disappear the moment it's convenient, and stops counting on you at all. "I trust my team to run with it" sounds the same either way. The difference shows up later: real delegation means you stay available and clear the roadblocks that land in your lane. Abdication means you vanish until something breaks, then show up asking why nobody told you. If you hear it from your team, that's delegation. If you hear it from a peer, that's abdication. Get this wrong often enough, and your team stops bringing you the problem at all, which is the same ending as every other way of losing them.

The Vulnerability Tax

Vulnerability gets punished in most organisations, even the ones with a values poster that says otherwise. Every leadership program tells you to admit what you don't know. Plenty of workplaces will discreetly mark you down for it, especially the higher you get, where certainty gets mistaken for competence. That's a real risk, not a mindset problem, and pretending otherwise just sets leaders up to get burned the first time they try it. The fix isn't blind vulnerability. It's picking your moments: be honest about your limits with the people whose respect you actually need, and build enough credibility elsewhere that one admission doesn't become the whole story people tell about you.

I didn't lead that IT team by learning IT. I led it by being clear about the problem, honest about my limits, and quiet enough for the people who actually knew the answer to give it. That wasn't motivation. It was just leadership doing the one thing it's actually for.

That's the shift I'm asking you to make: from being the answer to being the person who names the problem clearly enough that someone else can be.

If you're reading this and quietly wondering whether you're the leader in the relevance trap, or running abdication dressed up as trust, that doubt is not a weakness. In fact it's better insight than most people in leadership roles ever develop.

Spend the next month watching yourself. Look out for the times you intervene unnecessarily, the moments you speak up in a meeting because the silence makes you feel like you're not doing anything. That's when you're suffocating the expertise the room needs. Noise dressed up as value kills credibility. Clearing obstacles and managing strategic senior relationships is different, that's leadership, and it's worth celebrating because it makes things easier for your team. Notice the gap between the two. Then adjust your approach with your team first, before you take it anywhere else.

If you try that and still can't get traction, you're not walking into a conversation with your manager empty-handed. You're not showing up to announce you don't feel cut out for this. You're showing up with something specific: "I'm trying to learn to be more leader than solution owner. I've tried A, B, and C and only seen marginal improvement. I want to be able to X, Y and Z. I'd like your support with that."

Your team was never waiting to be inspired. They were waiting to see if you'd trust them enough to let them lead the parts you couldn't.