←Writing
·3 min read

Leadership Style Isn't a Conviction

Most managers arrive with a style already decided and let the team fit around it. That's the wrong order.

Most managers arrive with a leadership style already decided. It isn't that they've assessed the team and concluded this style is the right fit; they formed an idea of what good management looks like before they ever sat down with the people they'd be managing, so the style comes first and the team fits around it. I think that's the wrong order.

I did this myself in my founding years at Vendo.ma. The style that had worked through the early stages was to stay close to the work, make decisions quickly and keep everyone pointed at the same target, and it carried us a long way. As the team grew, the context shifted. The people around me were capable and autonomous, and what they needed from me had changed, but I kept leading the way I always had, close to execution when the team needed me further out. The style that built the company wasn't the style that could grow it.

Leadership style isn't a conviction you carry into every room. It's a response to what you find when you get there, and the first thing to look at is team maturity, by which I mean how the team operates, whatever the seniority on paper says. Do people own outcomes, or just tasks? Does the team self-organize, or does it wait to be told? Is quality maintained because people care about it, or because someone is watching? If you look for them, the answers are there within a few weeks; most managers just don't look for them explicitly enough.

When the team is mature, the right posture is high autonomy paired with genuine support. You coach through the hard decisions and clear the path, you make sure people have the context they need, and then you trust them to use it. Most of the value you add is invisible: the team moves, and you made that movement easier without standing in the middle of it.

If you apply that same posture to a team that's still building its ownership instincts, where collaboration hasn't settled and quality isn't yet internalized, the autonomy lands as ambiguity. The hands-off posture reads as absence, and the team doesn't accelerate; it drifts.

The opposite mistake costs just as much. Apply a directive style to a team that's already self-directing and you signal distrust without meaning to. The team that was maintaining quality because it cared about it starts maintaining it because it's being checked, which is a different thing, and harder to undo than it looks.

Neither posture is right in itself; what makes either of them work is the match. And the mismatch tends to be invisible to the manager who creates it, because they never stopped to ask what the team needed before deciding how to show up.

The question worth asking more often, and more explicitly, isn't "how should I lead?" but "what does this team need from me right now?" Most managers never ask it. I don't think that's because they don't care; it's because they already have an answer, and they had it before they ever met the team.