Nobody forced you into leadership. Choosing the position meant choosing responsibility for the people who came with it. From the moment you cross the gate, the job is asking what your team needs today, where they are stuck, and what decision they are waiting on. Most culture problems are unnamed leadership problems.
When leaders ask me how to build a strong team, the conversation usually gets complicated fast. How do we fix the culture? How do we get people to work better together? What programme should we roll out?
I tend to start somewhere much simpler. Did anyone make you come to work today? Did anyone force you into this leadership role?
The answer is almost always no
I have asked that question in rooms full of leaders. Nobody has ever told me they were forced.
You chose it. And when you chose the position, you also chose the responsibility that comes with it, including the people.
That second part is where the gap usually sits. People accept a role understanding the authority, the scope, and the compensation. Far fewer consciously accept that a group of people now depends on them, and that this dependency is not an optional extra you attend to when the operational work is finished.
What crossing the gate should mean
Here is the expectation I give leaders.
When you drive through the gate, park the car, and walk into the building, you are there to lead. From that moment your focus is your team. Whether that is the leadership team, a department, or a shift, it is the same obligation.
I use the physical version of it deliberately, because it is concrete. There is a specific moment each day where you cross from being a person with your own concerns into being someone other people are relying on. Naming that moment makes it much harder to drift through a week reacting to whatever arrived in your inbox.
It also means paying attention to the people counting on you, which is a different activity from monitoring their output.
The questions to ask about your team today
If your focus is meant to be the team, the practical version is a short set of questions, asked daily rather than quarterly:
- What does my team need from me today?
- Where are they stuck?
- What decision are they waiting on?
- Who needs clear direction?
- Who needs me to remove an obstacle?
- What can I do today that puts them in a better position to succeed tomorrow?
The third one is worth dwelling on. In most operations there is someone waiting on a decision that would take a leader four minutes to make, and that wait is costing days. Leaders rarely know which decision it is, because nobody wants to chase them.
Asking them daily matters more than asking them well. A leader who runs through that list every morning will be wrong about some of the answers and will still be far ahead of one who holds a thorough quarterly conversation and nothing in between.
The last question is the one that compounds. Handled consistently, it is the difference between a team that gets through the week and a team that is measurably more capable in six months.
Why the complicated answer is so tempting
When a leadership team decides the culture needs work, the instinct is to reach for something with a name. A programme. A framework. A survey with a dashboard behind it.
I understand the appeal. Those things are visible, they can be scheduled, and they let everyone point at an initiative when asked what is being done. The simple version has none of that. It is one leader, every day, asking what their people need and then acting on the answer.
The trouble is that the complicated answer often lets everyone avoid the uncomfortable one. It is easier to roll out a programme than to tell a manager that they took the authority and never took the people.
I am not against structure. Expectations, training, and support all matter, and without them you are relying on individuals to work it out alone. But structure laid on top of leaders who have not accepted the responsibility does not produce a culture. It produces a programme that people comply with and quietly ignore.
Most culture problems are leadership problems
A lot of what gets described as a culture problem inside a company is a leadership problem that nobody has named.
Someone took the authority that came with the job and never fully took ownership of the people who came with it. The work still gets done, decisions still get made, and the part that quietly does not happen is anyone attending to whether the team has what it needs.
That is rarely deliberate. It is usually a leader who was promoted for being excellent at the work, who was never told the job had changed, and who is doing exactly what made them successful before.
It is worth saying plainly because it changes what you do about it. You do not fix that with an engagement survey or a values exercise. You fix it by being explicit about what the role actually obligates someone to, and by supporting them while they learn a job nobody taught them.
The part nobody explains at promotion
Think about how most people become leaders. They were good at the work. They were reliable. A position opened and they were the obvious candidate.
What happened next was usually a conversation about scope, reporting lines, and pay. What usually did not happen was a conversation about the people, and about the fact that their success is now measured by what other people produce rather than by what they produce themselves.
That is a genuinely difficult transition, and we hand it to people with almost no preparation. Then we are surprised when they keep doing the work themselves, because the work is the thing they know how to be good at.
Our piece on frontline leadership and retention in manufacturing covers what that layer needs to hold, and Heather's account of being told her team was afraid of her shows how expensive the gap can get before anyone says it out loud.
Giving that person the language for what changed is often the whole intervention. Many of them are relieved, because they had sensed the job was different and had no way to describe it.
You accepted responsibility for the people
You accepted responsibility for the people the day you accepted responsibility for the position. Those arrived together, whether or not anyone said so at the time.
I find that framing useful because it removes the sense that attending to your team is something extra, generous, or optional. It is the job you agreed to do. On a week when production is behind and three things are on fire, that distinction is what determines whether the team gets led or merely managed.
It is also, I think, a more respectful way to talk to leaders about this than most of what is written on the subject. Nobody needs to be told to care more. They need to be told clearly what they signed up for.
What it looks like when a leader has accepted it
You can usually tell within a week of walking a floor.
People bring problems to that leader early, while the problems are still small and boring, because experience has taught them that something happens when they do. Decisions do not sit. When you ask someone what they are waiting on, they can answer, and the answer is rarely their own manager.
The team can also describe what good looks like for their own role without hedging. That only happens when someone has taken the time to tell them, and then kept telling them as the work changed.
Where it is not working, the signs are just as legible. Questions get routed around the manager. People wait to be told rather than deciding. The manager is visibly busy and mostly busy doing the work itself.
Neither picture is about how much anyone cares. Both are about whether someone understood what the position obligated them to and was given help learning it.
Where to start tomorrow
Pick the crossing point. For most people it is genuinely the car park, and the walk from the car to the door is long enough to ask one question.
What does my team need from me today?
Then find the answer before lunch rather than at the end of the week. Ask two people directly what they are waiting on. Make one decision that has been sitting. Remove one obstacle that is not yours but is in their way.
Do that consistently for a month and you will have changed more about how your area runs than any programme would have. Not because the actions are remarkable, but because the people around you will have worked out that you actually meant it.
Frequently Asked Questions
What does accepting a leadership position actually commit you to?
The authority and the people arrive together. Most people consciously accept the scope, reporting lines and compensation, and never consciously accept that a group of people now depends on them, which is not an optional extra once operational work is done.
What should a leader ask themselves daily?
What does my team need from me today, where are they stuck, what decision are they waiting on, who needs clear direction, who needs an obstacle removed, and what can I do today that puts them in a better position tomorrow.
Why are culture problems often leadership problems?
Because someone took the authority that came with the job without taking ownership of the people. The work still gets done and decisions still get made, while nobody attends to whether the team has what it needs. It is usually not deliberate.
Why do newly promoted managers keep doing the work themselves?
Because they were promoted for being excellent at the work and were never told the job changed. Their success is now measured by what others produce, and that transition is handed to most people with almost no preparation.
Where should a leader start?
Pick the moment you cross into work and ask what your team needs from you today. Then answer it before lunch: ask two people what they are waiting on, make one decision that has been sitting, and remove one obstacle in someone's way.