Servant Leadership Isn't Being Nice

Servant leadership got eaten by office posters

I have a problem with servant leadership. Not the idea. The idea is fine. The problem is what we’ve done with it. Somewhere along the way we took a demanding leadership stance and turned it into a motivational poster: be kind, be a good listener, put the team first. All true, all soft, all completely missing the point.

The version that survived is the comfortable one. The leader who serves by being nice. Who runs a warm retro, brings snacks, says “how are you really doing” in the one-on-one. None of that is bad. But if that’s where your service stops, you’re not serving your team. You’re decorating it.

Real service is mostly unglamorous, and a lot of it is hard.

Serving is doing the ugly work the team can’t do for itself

Here’s the test I actually use. Every day, ask yourself one question: what’s blocking my team, and can I clear it today? Not “is my team happy.” Not “did I give enough recognition.” What’s in their way, and is it within my power to move it.

Most of what blocks a delivery team is not technical. It’s a decision stuck three levels up. A dependency on another org that nobody owns. A vague mandate that means six people are quietly building six different things. A stakeholder who keeps reopening a scope that was supposed to be closed. Your engineers can’t fix any of that. You can. That’s the job.

Serving is removing obstacles, not handing out compliments. The compliment costs you nothing. The obstacle costs you a hard conversation, some political capital, and sometimes a night you’d rather have spent doing something else. Guess which one actually helps the team ship.

The leader is a bumper, not a megaphone

The single biggest service you can do for a delivery team is absorb the pressure coming from above so they can keep their focus.

In public-sector delivery the pressure never stops. Steering committees want a date. A director wants a feature moved up because someone mentioned it in a meeting. Another organization wants to know why their request isn’t already done. All of that is real, and all of it is noise to the five people who are heads-down trying to build something that works.

A bad leader is a megaphone. Everything that lands on his desk gets amplified and dumped straight onto the team. “They want this by Friday, they’re asking about that, the director’s nervous, go go go.” Now the team is carrying the anxiety of every person above them, and they can’t think straight.

The leader’s job is to be the bumper. You take the hit, you filter it, you translate it into one clear thing the team can act on, or you make it disappear entirely because it never deserved to reach them in the first place. The team should feel calm precisely because you’re not. That’s not you hiding the truth from them. That’s you doing your job so they can do theirs.

Serving does not mean refusing to decide

This is where the poster version really falls apart. People hear “servant leader” and think it means flat, consensus-driven, hands-off, let the team figure everything out. That’s not service. That’s abdication wearing a nicer shirt.

A leader who serves takes the hard trade-offs onto his own back, so the team doesn’t have to tear itself apart over them. When two priorities collide and somebody has to lose, that’s your call, not theirs. When the budget says you can’t do both and the team is split, you decide, and you own the decision out loud. The worst thing you can do is push a brutal arbitration down to the team in the name of empowerment. All you’ve done is hand them a problem with no authority to solve it, and then watch them fight about it.

Autonomy belongs to the team in the “how.” The direction, the constraints, the calls that create winners and losers across the group: those are yours. Serving means you carry the weight of the decision so they can keep their energy for the work.

The opposite of serving the team is using the team

There’s a cleaner way to spot a fake servant leader. Look at who ends up in the light.

The leader who uses the team turns its output into his personal visibility. The demo goes well, he’s the one in front of the committee taking the warmth. The release lands, his name is on the win. The team becomes the engine of his career, and he’s just steering it toward whatever makes him look good.

The real one does the reverse. He puts the team in front of the people who matter. He names the engineer who cracked the hard problem. He makes sure the director knows whose work that was. When something goes wrong, he’s the one in the room absorbing it, and when something goes right, he steps back and lets them have it.

You can’t fake this for long. Watch any leader through two or three delivery cycles and it’s obvious who’s serving and who’s being served.

Service takes courage, not just empathy

Here’s the part the posters leave out completely. Removing an obstacle often means saying no to someone more powerful than you. It means defending the team when it’s uncomfortable. It means telling a director his pet request is going to wreck the quarter, and holding that line while he’s annoyed at you.

Empathy is the easy half. Anybody can feel for a tired team. Courage is the half that actually changes their week: standing between them and the thing that would have crushed their focus, and taking the friction yourself.

If your idea of servant leadership never once puts you in an awkward conversation with someone above you, you’re not serving anybody. You’re just being pleasant.

Service presumes a direction

One caveat, because it’s the line people cross constantly. Serving a team that has no clear objective and no known constraints isn’t serving. It’s babysitting.

If the team doesn’t know what “done” looks like, doesn’t know the budget, doesn’t know the quality bar, doesn’t know who they have to collaborate with to land it, then clearing their obstacles is pointless. You’re smoothing the road for people who don’t know where they’re going. Comfortable, sure. Useless.

Service sits on top of direction, it doesn’t replace it. The spine is always the same: a crystal-clear objective, constraints everyone knows, real autonomy in the how, and accountability for the result. Once that’s in place, then serving means something. You give them the destination and the guardrails, and then you spend your days removing whatever stands between them and it.

So stop measuring yourself by how kind you are. Measure yourself by what you cleared off your team’s path this week, and by who got the credit when it worked.