
Hard-learned leadership lessons from both the military and the corporate world
Leadership isn't a title; it's a responsibility.
Most leaders would probably describe themselves as reasonably connected to their team. People talk to them. Meetings are productive. Problems get discussed. There are conversations, familiarity and perhaps even friendship. But proximity isn't necessarily connection. Nor is agreement.
The quality of a relationship becomes much easier to see when there is something at stake.
These moments tell people considerably more about their relationship with a leader than an open-door policy ever will.
Perhaps connection is best thought of as a form of credit. Every interaction either increases or reduces what people are prepared to risk with us. When someone brings bad news, challenges our thinking or admits a mistake, they're spending some of that credit.
How we respond determines whether they'll spend it again.
People learn what kind of relationship they have with a leader by discovering what that relationship can withstand.
Here are eight behaviours that influence that calculation.
Leadership requires enough confidence to make decisions without universal agreement.
It also requires enough self-awareness to recognise when defending a decision has become more important than examining it.
Those two things can look remarkably similar from inside our own heads. Teams notice how leaders respond to challenge. If disagreement consistently produces defensiveness, justification or an attempt to win the conversation, people adapt. Not necessarily by agreeing. Often by saying less.
That creates an interesting contradiction. The leader experiences less resistance and assumes greater alignment, when the team may simply have concluded that challenging them isn't worth the effort. Being challenged doesn't mean the leader is wrong. But being the leader doesn't mean they're right either.
A leader who always needs to win the conversation may eventually find themselves surrounded by people willing to let them.
There is often a considerable difference between how work appears from above and how it is experienced by the people doing it.
The process looks straightforward. The timeline appears reasonable. Responsibilities seem clear. Then there are competing priorities, difficult stakeholders, systems that don't behave as intended and dozens of small workarounds keeping everything moving.
A dashboard is a map. Useful, necessary and considerably easier to read than the terrain. The problem begins when leaders confuse the map with the ground their people are actually walking over.
Leaders don't need to insert themselves into every operational detail. Doing so creates a different problem. But distance can distort reality. Spend enough time around the work to understand what people are actually dealing with, rather than relying exclusively on what eventually makes its way into a report.
There is a point at which strategic distance simply becomes distance.
Micromanagement isn't always driven by a desire for control. Sometimes it comes from responsibility.
The leader is accountable for the outcome. They can see a potential mistake coming. They know how they would approach the problem. Stepping in feels sensible. And occasionally it is. But micromanagement can become a self-fulfilling prophecy.
A leader holds the handlebars because they don't trust the team to steer. The team never properly learns to steer because the leader won't let go. Eventually, the wobble becomes evidence that holding on was necessary all along.
Give people responsibility while retaining every meaningful decision and they'll eventually stop exercising judgement. Instead, they'll start seeking permission. The leader then sees a team reluctant to make decisions and concludes that greater oversight is required. The cycle completes itself.
Sometimes the capability gap a leader is trying to manage is partly the capability gap their management has created.
Trust requires some tolerance for people doing things differently. Different isn't necessarily wrong.
Leaders often underestimate how much information they possess that other people don't. They've attended the meetings. Spoken with stakeholders. Seen the competing options. Watched the problem evolve. They know which options have already been rejected and why. By the time a decision reaches the team, the leader may have spent weeks thinking about it.
The team hears the conclusion on Tuesday morning. Then we wonder why they don't immediately see what seems obvious.
Clear communication requires more than transmitting the final answer. People need enough context to understand what is being attempted, why it matters, where the constraints sit and what should take priority when two reasonable options compete. That last part matters.
Leadership rarely occurs in a world where one option is obviously right and everything else is obviously wrong. Often, people are choosing between competing priorities, imperfect information and consequences that cannot all be avoided. Context gives them something instructions cannot. Judgement.
Instructions work while reality behaves as expected. Context matters when it doesn't.
There is an uncomfortable inefficiency built into developing people. It is usually faster to do something ourselves. Making the decision is faster than explaining how to make it. Taking over can be faster than watching someone struggle. Fixing a mistake can feel considerably easier than allowing someone to work through it.
In the short term, the leader looks very effective. In the long term, nobody else becomes more capable. That's the contradiction.
The leader who continually proves how capable they are can inadvertently prevent everyone around them from proving the same thing.
Development requires exposure to decisions, responsibility and consequence before circumstances make that exposure unavoidable. That means accepting that learning will occasionally be slower, messier and different from how we would have done it ourselves.
If leaders continually rescue people from difficulty, they shouldn't be surprised when those people struggle without them.
Recognition doesn't need to become theatre. People can usually distinguish between genuine acknowledgement and praise being distributed because somebody read that recognition improves engagement. Notice contribution. And not only the obvious outcomes.
There is a signalling effect in what leaders recognise. Praise only outcomes and people learn that outcomes matter. Recognise honesty, judgement, accountability and service to others, and people learn that how the result was achieved matters too.
What leaders consistently notice tells people what is valued. So does what they consistently overlook.
Most leaders say they want people to speak openly. The interesting part happens afterwards.
They're spending some of that relational credit. What happens next determines whether they do it again.
If uncomfortable information repeatedly produces blame, embarrassment or defensiveness, people don't necessarily stop noticing problems. They stop volunteering them. That creates one of the more dangerous illusions in leadership:
Silence can look remarkably like agreement.
The room becomes easier to manage. Meetings become less contentious. Decisions encounter less resistance. The leader might even conclude that the team is finally aligned. Perhaps. Or perhaps people have simply calculated the cost of honesty and decided the return isn't worth it.
The absence of disagreement isn't evidence of alignment. Sometimes it's evidence that disagreement has become too expensive.
Listening is relatively easy when someone is confirming what we already believe.
It becomes considerably harder when they're questioning our judgement, criticising something we've built or presenting information that complicates the decision we wanted to make. That's also when listening becomes most useful.
Listening doesn't require agreement. It requires enough curiosity to entertain the possibility that the other person knows something we don't.
And sometimes the useful information isn't contained in what people explicitly say.
Leaders can have enormous access to information while remaining surprisingly disconnected from reality. Being surrounded by people who talk to us is not the same as being surrounded by people who tell us what they think.
Relationships with teams are built incrementally, often in moments the leader barely remembers but the other person does.
None of these interactions independently determines the relationship. Together, they establish a pattern. And people are remarkably good at recognising patterns.
Leadership positions naturally create distance. Authority changes conversations. People become more selective about what they say, how they say it and when they say it. That isn't necessarily dysfunction. It's human behaviour.
The leader's job isn't to pretend the power difference doesn't exist. It's to understand how their behaviour affects what people are prepared to risk despite it. Because connection isn't demonstrated by how comfortable the relationship feels when everything is going well.
It's demonstrated by what people are still willing to say when it isn't.
(07) 2114 9072
Drawn from lessons learned in the military, and in business, we make leadership principles tangible and relatable through real-world examples, personal anecdotes, and case studies.
© Copyright 2023 The Eighth Mile Consulting | Privacy