Servant Leadership: The Model That Actually Works in Tech
I've been managing engineers for a good chunk of my career now. And if there's one thing I've learned the hard way, it's this: the moment you start acting like a boss, you stop being a leader.
The Problem With Traditional Management
When I first stepped into a management role, I did what most people do — I tried to control things. Set deadlines. Assign tasks. Track progress. Review output. The classic command-and-control model that looks great on paper and falls apart the moment you're dealing with creative, autonomous knowledge workers.
Engineers don't respond well to micromanagement. And honestly? Neither do most humans.
What Servant Leadership Actually Means
Robert Greenleaf coined the term back in 1970, but the idea is simple:
A servant-leader focuses primarily on the growth and well-being of people and the communities to which they belong.
In practice, this means flipping the traditional hierarchy:
| Traditional Manager | Servant Leader |
|---|---|
| Sets direction from the top | Aligns direction with the team |
| Monitors and controls | Removes blockers and enables |
| Evaluates performance | Develops growth paths |
| Hoards information | Shares context freely |
| Takes credit | Gives credit |
How I Practice It Daily
1. Start every 1-on-1 with "How can I help?"
Not "What's your status?" — that's surveillance disguised as caring. When you ask how you can help, you're putting yourself in service of their work. Most of the time, the answer is removing some organizational friction they shouldn't have to deal with.
2. Share context, not just tasks
Engineers make better decisions when they understand the why. I share business metrics, customer feedback, and strategic direction openly. When people understand the problem, they often find solutions I never would have thought of.
3. Protect the team's time
One of the most impactful things a leader can do is say "no" on behalf of their team. Shield them from unnecessary meetings, scope creep, and organizational noise. Your job is to create a bubble where they can do their best work.
4. Invest in their growth, not just their output
I regularly ask my team: "Where do you want to be in two years?" Then I work backwards to create opportunities that align with both their goals and the company's needs. It's not altruism — it's the best retention strategy that exists.
The Results Speak for Themselves
Teams I've led with this approach consistently show:
- Lower turnover — people stay where they feel valued
- Higher quality output — ownership leads to pride in work
- Better problem-solving — shared context leads to creative solutions
- Stronger culture — trust compounds over time
The Hard Parts
Servant leadership isn't all sunshine. It requires:
- Patience: Results take time. You're building a culture, not shipping a feature.
- Ego management: You have to be okay with not being the smartest person in the room.
- Tough conversations: Serving people sometimes means giving them honest feedback they don't want to hear.
- Boundaries: Being a servant leader doesn't mean being a doormat. You still need to make hard decisions.
My Take
I was born in '91. I grew up in an era where information became free and hierarchy started losing its grip. The best leaders I've admired — both in tech and beyond — were the ones who made me feel like I mattered. Not because they said it, but because they showed it through their actions every single day.
That's the kind of leader I try to be. Not because it's trendy, but because it works.
If you're a new manager reading this: stop trying to prove you deserve the title. Start proving you deserve the trust.