The best leaders can’t answer “What’s your leadership style?”
The question I stopped trying to answer
“What’s your leadership style?”
I’ve been asked that question in interviews, leadership programs, and conversations with other managers more times than I can remember.
For years, I thought there had to be a good answer.
Servant leadership.
Transformational leadership.
Coaching leadership.
Democratic leadership.
The more books I read, the longer the list became. It felt like every great leader had found their label, and I was supposed to find mine.
Today, I honestly don’t know how to answer that question.
The way I lead a brand new team isn’t the way I lead a mature one.
The way I lead during a production incident isn’t the way I lead when we’re exploring a new product.
The way I lead a junior engineer isn’t the way I lead someone who’s spent fifteen years building software.
Even within the same team, my approach changes over time. A team that needs structure today may need autonomy six months later.
If you watched me across those situations, you could easily think you were looking at different leaders.
Sometimes I’m very direct.
Sometimes I spend most of the meeting asking questions.
Sometimes I slow everything down.
Sometimes I push the team to move faster than they’re comfortable with.
Years ago, that bothered me.
I thought good leaders were supposed to be consistent.
Eventually I realized I had been trying to answer the wrong question.
The real question isn’t:
“What’s your leadership style?”
It’s:
“How do you decide what your team needs right now?”
That changed the way I think about leadership.
Leadership is problem-solving
If leadership were mostly about expressing your personality, having one fixed style would make sense.
But leadership isn’t self-expression.
Leadership is problem-solving.
That’s why I’ve never been comfortable introducing myself as a servant leader, a coaching leader, or any other label.
Those labels describe behavior.
They don’t explain how someone thinks.
Imagine asking a surgeon about their surgical style.
You probably wouldn’t feel comfortable if they answered:
“I’m a minimally invasive surgeon. That’s just who I am.”
You’d expect something different.
“It depends on the patient, the diagnosis, the risks, and the outcome we’re trying to achieve.”
Leadership works the same way.
Every team has different constraints.
Some teams don’t trust each other.
Some trust each other but avoid difficult conversations.
Some move too slowly because every decision needs another meeting.
Others move so fast that quality starts falling apart.
Treating all of those teams the same in the name of consistency doesn’t sound authentic.
It sounds like someone applying the same solution to different problems.
The same team changes over time.
The manager they need during their first month together is rarely the manager they’ll need a year later.
Looking back, I don’t think I ever had one leadership style.
I had a habit of trying to understand the problem before deciding how to respond.
It took me years to realize those are two very different things.
The team that changed my mind
One experience made this painfully obvious.
I joined a team after leading another one that responded really well to a coaching approach.
I spent a lot of time asking questions.
Helping people arrive at their own conclusions.
Creating space for discussion.
It worked.
So naturally, I walked into my next team assuming I’d lead the same way.
Within a couple of weeks, something felt off.
The team wasn’t lacking ideas.
They weren’t lacking ownership.
They weren’t lacking technical ability.
They were lacking decisions.
People had spent months discussing the same topics without moving forward.
Everyone was waiting for someone else to create clarity.
The team didn’t need another coach.
They needed someone willing to make decisions, remove ambiguity, and accept the responsibility that comes with it.
So my behavior changed.
Meetings became shorter.
Decisions became faster.
I became much more directive than I had been with my previous team.
A few months later, once the team found its rhythm, I slowly stepped back again.
If someone had observed me in those two teams, they probably would have described two completely different leadership styles.
The interesting part is that I wasn’t trying to change my style.
I was trying to solve a different problem.
The mental model that gave me a language for it
A few years later, I came across a way of thinking that finally gave me a language for what I had been doing.
It’s called first principles thinking.
The idea is more than two thousand years old.
Aristotle described first principles as the most fundamental truths you can’t reduce any further. They’re the foundation everything else is built upon.
Scientists have relied on this approach for centuries.
When physicists study the world, they don’t begin with tradition.
They begin with fundamentals.
They ask what they know to be true before building explanations on top of it.
The concept became widely known in business because Elon Musk often talked about it while building SpaceX.
People asked him how a new company could possibly compete with an industry where rockets cost hundreds of millions of dollars.
Most people accepted the assumption that rockets were simply expensive.
He didn’t.
Instead, he broke the problem apart.
What materials make up a rocket?
How much do those materials actually cost?
Which part of today’s price comes from physics?
Which part comes from manufacturing?
Which part comes from assumptions the industry had accepted for decades?
Once the problem was reduced to its basic components, it became possible to question almost everything else.
That story stayed with me.
Because leadership is full of assumptions too.
Weekly one-on-ones.
Daily stand-ups.
Career ladders.
Performance reviews.
Delegation frameworks.
Feedback models.
Most of us inherit these practices from previous managers, books, podcasts, conferences, or companies we admire.
Very few of us stop and ask:
What problem is this practice actually solving?
That question changed the way I make leadership decisions.
Asking better questions
Today, whenever I’m facing an important leadership decision, I try to slow myself down.
Instead of asking:
“What’s the best practice?”
I ask:
What problem am I actually trying to solve?
Why does this problem exist?
What would success look like?
Which constraints are real?
Which ones am I accepting simply because they’ve always existed?
Only after answering those questions do I start thinking about solutions.
Sometimes the answer looks almost identical to the conventional advice.
Sometimes it’s completely different.
Take one-on-ones…
People often say every manager should have weekly one-on-ones with every engineer.
That’s reasonable advice.
Until you ask one more question.
Why?
What problem are those meetings solving?
For one engineer, they’re building trust.
For another, they’re providing coaching.
For someone new, they’re creating psychological safety.
For someone who’s been consistently delivering for years, they may become repetitive status updates that nobody enjoys.
The meeting was never the goal.
The outcome was.
The same thing happens with delegation.
Managers ask:
“Should I delegate more?”
Again, that’s a solution pretending to be a problem.
The real questions are different.
What’s preventing this person from owning this independently?
Do they lack confidence?
Context?
Experience?
Or am I the bottleneck because I keep stepping in?
Each answer leads somewhere completely different.
Even feedback changes.
Some people need direct feedback immediately.
Others need time to process.
Some lose trust if you’re too soft.
Others shut down if you’re too blunt.
Trying to behave consistently across all those situations isn’t leadership.
Understanding the problem is.
Maybe leadership styles are conclusions
This is the part I keep coming back to.
Leadership styles are useful descriptions.
They’re just poor starting points.
They’re conclusions.
The thinking that produced them matters much more than the label itself.
If you copy someone else’s conclusion without understanding how they arrived there, it’ll work for a while.
Eventually you’ll run into a team, a company, or a situation where the same approach quietly stops working.
For a while now I’ve stopped trying to build a recognizable leadership style.
I’d rather build a reliable way of thinking.
One that starts with understanding the problem before reaching for the solution.
A different answer
If someone asks me about my leadership style today, I’ll probably disappoint them.
I don’t have a short answer.
Some days I’m highly directive.
Some days I mostly listen.
Some days I spend hours coaching.
Some days I make a difficult decision in five minutes because clarity matters more than consensus.
If you watched me for a week, you might put one label on me.
If you came back six months later, you’d probably choose another.
And you’d probably be right both times.
The consistency isn’t in my behavior.
It’s in the questions I ask before deciding how to behave.
So if someone asks me:
“What’s your leadership style?”
My honest answer is this.
I don’t start with a style.
I start with the problem.
The style reveals itself after that.