On Management and Leadership — They're Not the Same Thing
I've been thinking about this a lot lately. Not in the MBA-textbook way, but in the quiet, 2 AM kind of way — when you're replaying a conversation and wondering if you handled it right.
Here's what I've come to believe:
Management is a role. Leadership is a behavior.
You can be a manager without leading. And you can lead without managing anyone at all.
The Manager's Job
A manager deals in systems. Schedules, budgets, processes, performance reviews. The manager asks: Is this on track? Is this within budget? Is this meeting the spec?
These things matter. Without them, teams drift. Projects stall. Chaos creeps in.
But here's the trap: you can be excellent at managing and still have a team that's disengaged, uninspired, and quietly looking for the exit.
Because management is about things working. Leadership is about people wanting to make things work.
The Leader's Job
A leader deals in meaning. Vision, trust, courage, vulnerability. The leader asks: Why are we doing this? What kind of team do we want to be? What's the right thing to do here, even if it's hard?
Leadership shows up in small moments more than grand ones:
- Admitting you were wrong in front of the team
- Giving credit for an idea that wasn't yours
- Having the conversation everyone is avoiding
- Protecting someone's time when the organization pushes back
- Saying "I don't know" without feeling diminished
I've met brilliant managers who couldn't lead. They hit every metric but bled talent. And I've met natural leaders with zero formal authority who held teams together through sheer trust.
The Uncomfortable Middle
Most of us live somewhere in between. We have the title of manager and the aspiration of leader, and we stumble through the gap daily.
Some days I get it right. I ask the right question. I shut up and listen. I trust someone with something I desperately want to control.
Other days I fall back into managing — tracking tasks instead of clearing blockers, reviewing output instead of developing people, optimizing for efficiency instead of energy.
The difference between a good day and a bad day is usually one thing: where my attention goes.
When I'm focused on the system — the sprint board, the metrics, the deadlines — I manage.
When I'm focused on the people — their growth, their frustrations, their ideas — I lead.
A Few Things I've Learned
1. Leadership is not charisma.
The most impactful leader I ever worked with was quiet, almost reserved. She never gave speeches. She just consistently showed up, asked thoughtful questions, and made people feel heard. That's it. That was enough.
2. Management without leadership is exhausting for everyone.
If you only manage, you become the engine. Everything runs through you. Every decision, every conflict, every priority call. That's not sustainable — not for you, and not for the team.
But if you lead — if people understand the why and trust the how — they start making decisions on their own. They resolve conflicts without you. They prioritize based on shared understanding, not your approval.
3. You don't need permission to lead.
I spent years waiting for someone to give me the title before I started leading. That was a mistake. Leadership isn't granted. It's practiced. You lead by doing the things that leaders do — regardless of where you sit in the org chart.
4. The best leaders are constantly uncertain.
This sounds counterintuitive. Aren't leaders supposed to be confident? Decisive?
Sure. But confidence doesn't mean certainty. The best leaders I know are deeply uncertain about most things — and that uncertainty is exactly what keeps them curious, humble, and open to being wrong.
The worst leaders are the certain ones. Certain they're right. Certain their way is the only way. Certainty is the death of learning.
The Vietnamese Context
Growing up in Vietnam, I absorbed a particular model of leadership: hierarchical, top-down, respect-the-elder. The boss speaks, everyone listens. The boss decides, everyone executes.
That model works in certain contexts. Military operations. Crisis management. Situations where speed and compliance matter more than creativity and ownership.
But in knowledge work — in building software, in creating products, in solving problems that don't have clear answers — that model fails. It fails because it assumes the person at the top has the best information. And in a complex, fast-moving environment, they almost never do.
The best information lives at the edges. With the engineer debugging the system at midnight. With the designer who just talked to twenty users. With the new hire who sees things the veterans have gone blind to.
Leadership in this context means creating the conditions for that information to surface. It means building a culture where the intern can challenge the CTO's assumption — and be thanked for it.
That's a hard cultural shift. I'm still working on it myself.
The Question I Come Back To
When I'm unsure about how to handle a situation — and that's most of the time — I ask myself one question:
What would help this person grow?
Not: what would make this project succeed. Not: what would make me look good. Not: what's fastest.
What would help this person grow?
Sometimes the answer is direct feedback. Sometimes it's stepping back and letting them struggle. Sometimes it's shielding them from organizational noise so they can focus. Sometimes it's having a conversation that has nothing to do with work.
It's not a perfect compass. But it's the best one I've found.
No Conclusion
I don't have a neat ending for this. Management and leadership are messy, overlapping, constantly shifting things. Some days you get it right. Most days you don't.
But I think the trying matters. The noticing. The 2 AM reflection about whether you handled that conversation well.
If you're asking the question, you're probably doing better than you think.
Written on a Saturday afternoon, somewhere between a second coffee and a long overdue walk.