A team hits a problem, not a dramatic one, not yet, a delay, a missed handover. A decision that should have been made an hour ago. People wait. One person speaks first because they know the system better than anyone else in the room. They’re experienced, they’re sharp and they’re respected, so everyone follows.
It feels safe.
This is not always leadership.
In infrastructure organisations, technical strength matters. It matters a lot.
You need people who understand risk, process, systems, compliance, delivery, timing, consequence. You need people who can read a situation fast and know what’s at stake.
No sensible leader would argue with that. But this is where many organisations get caught out. We see deep technical capability and assume leadership comes with it. We promote the expert, we lean on the most knowledgeable person in the room and we let confidence stand in for clarity, then we let authority rest on experience alone. (We’ve seen it in countless organisations from professional practices, lawyers and accountants, as well as in power stations and defence contractors).
The pressure rises, communication tightens, uncertainty grows, and something awkward becomes obvious. The person everyone depends on may know the work, but that does not mean they know how to lead people through it.
This is not a criticism of technical experts, it’s a warning to organisations that confuse one strength for another.
Leadership is behavioural, it shows up in how people create clarity, how we handle pressure, how we respond to challenge, how we make decisions visible, how we build trust, and how we set a standard others can follow.
None of that appears by magic because someone knows more than everyone else. You’ll have seen this for yourself.
A technically brilliant manager who gives vague direction, a subject matter expert who shuts down challenge without realising it, a senior operator who knows the answer but leaves everyone else dependent on them, or even a respected specialist who becomes the centre of every decision, slowing the team because nobody else feels safe to move.
These are not rare cases. They’re common. They are often tolerated because the person is valuable. Sometimes they’re even admired because they can rescue bad situations at the last minute. But rescue is not the same as leadership. In fact, repeated rescue often hides weak leadership.
It creates a culture where teams wait for the expert, defer too quickly, escalate too late, and stop building confidence of their own. Over time, that does real damage. It narrows thinking. It slows decisions. It reduces challenge. It makes the team less resilient than it looks.
Ask yourself a blunt question:
In your organisation, are people building leadership capacity, or are they building dependence on a few capable individuals?
This question matters more than most people want to admit. In high consequence environments, poor leadership rarely announces itself with a single big failure. It appears in smaller patterns first:
- Meetings end without clear ownership.
- People leave with different interpretations of the same decision.
- Tension stays hidden because nobody wants to challenge the person with the strongest technical authority.
- Standards drift because behaviour is inconsistent.
Teams stop speaking plainly.
Colleagues learn to read mood rather than direction. At that point, the issue is no longer technical. It’s social, it’s behavioural, it’s leadership.
This is why some organisations struggle even when they are full of talented people. They invest heavily in knowledge, systems and compliance, but they fail to give equal attention to how leadership is practised in live settings.
They assume the right process will carry the day.
They assume the most technically able people will naturally create good team behaviour.
They assume experience will produce trust.
It does not work like that.
People do not follow knowledge alone, we follow signals, we watch who speaks first, we watch how disagreement is handled, we watch whether challenge is welcomed or punished, we watch whether leaders stay calm, become defensive, or avoid the hard call.
Then we watch whether standards apply evenly or shift with personalities and watch whether mistakes become learning, blame, or silence.
This is how culture forms. Not from leadership statements. Not from values on a wall. Not from a slide-deck about expectations. Culture forms when people decide what is safe, what is risky, what gets rewarded, and what gets ignored.
This is where technical strength can accidentally become part of the problem.
A highly competent expert may not mean to dominate discussion, but others will often defer to them anyway. A senior specialist may not realise their tone shuts people down, but the team will feel it.
A manager may solve every difficult issue themselves because it is faster, but that can teach the team not to think, not to own, and not to grow. The result is an organisation that looks strong on paper and feels fragile in practice. That gap matters.
Especially in infrastructure, where leadership affects not just performance, but trust, judgement, co-ordination and public confidence. In those settings, you do not need leaders who simply know the work. You need leaders whose behaviour helps other people do the work well, under pressure, without confusion, without delay, and without fear.
So, what should organisations do first?
Start by dropping the assumption that technical excellence naturally develops leadership excellence. Treat them as related, but separate.
- Measure both.
- Develop both.
- Reward both.
Then look harder at the behaviours your strongest people model every day.
- Do they create clarity, or dependence?
- Do they make challenge easier, or harder?
- Do they build confidence in others, or absorb all authority into themselves?
- Do they set a repeatable standard, or force everyone to work around their personal style?
These questions are not soft. They are operational. They tell you whether your leadership model is strengthening the system or quietly narrowing it. Because when pressure rises, teams do not only need the right answer. We need the right conditions around that answer.
- We need trust.
- We need clarity.
- We need visible ownership.
- We need behaviour they can rely on.
- We need leaders who can hold the room steady, not just solve the problem in front of them.
Knowledge is vital. Nobody sensible disputes that. But knowledge alone does not create leadership. And when organisations confuse the two, they usually find out at the worst possible moment.
Being right is not the same as being followed.
Expand your community. The TEG Newsletter introduces you to…