The Difference Between Managing and Leading

Throughout my career, I have worked with many different management styles — some effective, some less so.

A few were genuinely excellent.

A few jobs ago, after working with one particularly good manager, I started wondering what actually made him different. He had a well-deserved reputation for being a great manager, but it was not because he had the loudest voice in the room or because everyone waited for him to make every decision.

It was almost the opposite.

The team worked well because people understood the goal, trusted each other, helped each other, and could keep moving even when the manager was not in the room. Important work did not stop just because one person was away sick. If someone working on something critical was suddenly unavailable, the team self-organised, shared context, and kept the work moving.

As I often do when something interests me, I went down a bit of a rabbit hole. I watched a lot of content about leadership, management, trust, motivation, and high-performance teams. Eventually I came across Simon Sinek's work and a lot of it clicked for me.

I do not want this to be a summary of Simon Sinek's work. He explains his own ideas far better than I could. But his work gave language to things I had already started seeing in practice: people need purpose, trust, safety, and leaders who serve the team rather than control it.

After watching a lot of his content and applying some of those ideas in a brief tech lead role, I have come to a fairly simple conclusion:

A great manager is not really what you want.

What you want is a great coach.

Let me explain.

Command-and-control does not scale

I think a lot of people get into management for the wrong reasons.

Sometimes people get sick of being told what to do, so they decide they want to be the person telling others what to do.

Unfortunately, that does not scale very well.

Imagine you have a team of people who do exactly what you say. That might feel useful at first. You can get more of what you personally want done because everyone is following your instructions.

But what happens when you are away?

What happens when you take leave?

What happens when you are in meetings all day?

What happens when you go out for lunch?

If the team cannot operate without you, then you have not built a high-performance team. You have built a bottleneck.

Even if you are smart, experienced, and well-intentioned, you can only hold so much context. There is only so much one person can control. If every decision needs to come through you, then the team will always be limited by your availability, your knowledge, and your attention.

That is fragile.

A better team is made up of people who understand the goal well enough to make good decisions without constantly needing permission.

You want alignment, not obedience

A high-performance team is not a group of people blindly doing what they are told.

It is a group of people working independently toward the same goal.

There is a big difference.

Obedience means people wait for instructions.

Alignment means people understand the mission, the constraints, the priorities, and the reason behind the work.

This is where I think Simon Sinek's idea of starting with "why" is so useful. People do better work when they understand why something matters. Not just what they have been asked to do, but why the work exists in the first place.

In software teams, this matters a lot.

"Build this endpoint" is a task.

"Customers cannot complete this workflow without support manually fixing it, and we need to remove that bottleneck" is context.

The second version gives people room to think.

Maybe the endpoint is still the right answer. Maybe there is a simpler fix. Maybe the real issue is somewhere else entirely. But if all someone has is a ticket, they will probably just complete the ticket.

That might look productive, but it is not the same as solving the problem.

A coach builds people who can think

A good leader does not want a team of robots.

You want people who can think, challenge, suggest, adapt, and take ownership.

That does not happen if every idea gets shot down immediately. It also does not happen if every decision is dictated from above.

A great leader asks questions.

They challenge assumptions, including their own.

They guide people in the right direction without taking away their ability to think.

If someone comes to you with an idea, there is a huge difference between shutting it down and helping them think it through.

You could say:

No, that will not work.

Or:

Do this instead.

That might be faster in the moment, but it does not help the person grow. It also trains people to come to you for answers instead of learning how to think through the problem themselves.

A better response is usually more curious and more constructive:

Have you considered what happens if this part changes?

Or:

I like the direction. Let’s think through how this fits with what we already have.

Or:

That sounds promising. What risks should we clear up before we go too far down that path?

Those questions still provide direction, but they do it without taking ownership away from the person who brought the idea.

The first response is a wall.

The second response is coaching.

It gives the person a chance to grow. It helps them think more deeply. It also keeps ownership with them instead of turning every conversation into "boss approves" or "boss rejects".

That is important because the goal is not to make people dependent on you.

The goal is to make them more capable.

Trust is the foundation

A team cannot perform well without trust.

If people are scared of looking stupid, they will hide confusion.

If people are scared of blame, they will hide mistakes.

If people are scared of punishment, they will hide bad news until it is too late.

That is how small problems become expensive problems.

A high-performance team needs enough trust for people to say:

I do not understand this.

I think we are solving the wrong problem.

I made a mistake.

I need help.

This plan has a risk.

That does not mean everyone is soft or that standards do not matter. It means the team is strong enough to deal with reality.

One of the ideas from Simon Sinek's work that really resonated with me is the idea that leaders create safety inside the team. Not safety as in "nothing bad ever happens", but safety as in the team does not turn on itself when things get hard.

That matters.

When there is trust, people pull together.

When there is no trust, people protect themselves.

That is when you start seeing people hide information, avoid responsibility, play politics, or quietly let someone else fail because "it is not my problem".

That is not a team. That is just a group of individuals sitting near each other.

Team unity matters

One thing I have seen too often is a team slowly turning into a collection of individuals.

Someone finishes their work and leaves early.

Someone else is stuck and works late.

Nobody helps because everyone is measured by their own task list.

On paper, each person might be doing their job. But as a team, they are failing.

A strong team behaves differently.

If someone is stuck, the team helps.

If something goes wrong, the team works the problem.

If the goal is at risk, people reorganise around the goal.

That is what you want.

Not because everyone needs to be a hero. Not because people should burn themselves out. But because the team understands that the outcome matters more than individual ticket completion.

A team that only optimises for individual tasks will always struggle with shared outcomes.

Motivation does not come from orders

Giving people orders is not a great motivator.

It might get compliance, but compliance is a pretty low bar.

Some people will do exactly what they were told, no more, no less. Then they will go home. Fair enough too, if that is the environment they are in.

But if you want people to do their best work, they need more than instructions.

They need context.

They need ownership.

They need to understand what matters and why.

I have seen this with ticket systems. Someone completes the ticket exactly as described, but leaves a mess behind because the ticket was their objective. They were not thinking about the wider system, the future work, the customer, or the team.

That is not necessarily their fault. Often the system trained them to behave that way.

If you want people to own the problem, you need to give them the problem.

Not just the task.

When people understand the bigger picture, they can spot opportunities. They can see future issues earlier. They can make better trade-offs. They can tell you when the plan does not make sense.

The people closest to the work can often see things that people higher up cannot.

That is only useful if you actually listen to them.

Autonomy still needs direction

There is a trap here.

When people talk about autonomy, it can sound like everyone should just do whatever they want.

That is not what I mean.

A high-performance team still needs direction. It still needs priorities. It still needs standards. It still needs someone to make hard calls when things are unclear.

Autonomy without alignment becomes chaos.

Alignment without autonomy becomes micromanagement.

The goal is both.

People should know:

• What problem are we solving?
• Why does it matter?
• What does success look like?
• What are the constraints?
• What trade-offs are acceptable?
• When should they ask for help?
• Who needs to be involved?

Once those things are clear, let people work.

Give them room to think.

Give them room to solve the problem properly.

Give them room to surprise you.

A leader protects the team

A good leader does not just push work down into the team.

They also protect the team.

They protect the team from unclear priorities, pointless meetings, random scope changes, politics, panic, and fake urgency.

That does not mean shielding the team from reality. The team still needs context. They still need to understand business pressure. They still need to know what matters.

But there is a difference between sharing useful context and spraying chaos over everyone.

A good leader absorbs some of that chaos, turns it into clarity, and helps the team focus.

They unblock people.

They remove obstacles.

They help the team navigate the organisation.

They make sure the team has what it needs to do good work.

That is leadership.

Not status. Not control. Not being the smartest person in every meeting.

Leadership is service.

High performance is a long game

A low-performance organisation often treats work like a scoreboard.

How many tickets did we close?

How many story points did we complete?

How busy does everyone look?

That can create the appearance of progress while quietly damaging the team and the system.

A high-performance team plays a longer game.

They care about delivery, but they also care about quality, trust, learning, maintainability, and whether the team can keep performing without burning out.

There is no point squeezing a team for short-term output if the cost is rework, resentment, poor quality, and people leaving.

Good leadership is not just about getting more work out of people.

It is about building an environment where good work can keep happening.

The manager is not removed

None of this means the manager does nothing.

A coach is not passive.

A good leader still needs to make decisions. They still need to set standards. They still need to deal with poor behaviour. They still need to have hard conversations. They still need to say no.

Sometimes leadership means stepping back.

Sometimes it means stepping in.

The skill is knowing which one is needed.

If the team has context, trust, and capability, get out of the way.

If the team is blocked, help.

If the team is drifting, realign.

If the team is unsafe, protect it.

If the team is avoiding reality, challenge it.

If the team is succeeding, give them credit.

What I think makes a high-performance team

For me, a high-performance team is not a team that just closes lots of tickets.

It is a team that can understand a goal, organise around it, challenge the plan when needed, help each other, adapt when reality changes, and keep delivering without needing constant supervision.

That requires leadership, but not the command-and-control kind.

It requires a leader who can coach, guide, protect, challenge, and serve.

It requires trust.

It requires context.

It requires people to care about the outcome, not just their assigned task.

That is the kind of team I want to work in.

It is also the kind of team I would want to help build.

The kind of leader I hope to be

I am not writing this as someone who thinks they have leadership all figured out.

If I ever get the opportunity, and the courage, to lead a team properly one day, these are the things I hope I remember.

I hope I remember that leadership is not about being the smartest person in the room.

It is not about having all the answers.

It is not about control.

It is about creating an environment where people understand the goal, trust each other, feel safe enough to think clearly, and are supported enough to do their best work.

That is the kind of leadership I have appreciated when I have seen it.

It is also the kind of leadership I would hope to practise myself.

Key takeaways

• Seriously, go read or watch Simon Sinek's material, especially around purpose, trust, and leadership.
• You want a leader and coach, not just a manager who assigns tasks.
• Start with why. Give people the reason behind the work, not just the work itself.
• Build trust so people can ask for help, raise risks, and admit mistakes early.
• Enable your team, unblock them when they are stuck, and guide them without taking ownership away from them.
• Build people who can think, not people who wait to be told what to do.
• Give the team the full picture so they can make better decisions in your absence.
• Create strong team unity so people support each other instead of acting like isolated individuals.
• Encourage feedback and change when the current way of working is not helping.
• Ask questions and challenge thinking rather than simply mandating answers.
• Protect the team from noise, politics, and unclear priorities.
• Play the long game. Sustainable performance matters more than short-term theatre.

Published: 26/06/2026 UTC

Updated: 26/06/2026 UTC

<- Back To Blog