Why I Rarely Had to Tell My Team What To Do

When people imagine leadership, they often imagine direction.

They picture the leader setting priorities, making decisions, solving problems and providing answers. The larger the team becomes and the greater the responsibility, the more important those activities appear to be. It is easy to conclude that successful leadership is primarily about having the right answers at the right time and ensuring that everyone else follows the plan.

For a long time, I believed something similar.

When strong teams need less direction

As my career progressed, the scale of the challenges certainly increased. Customers became larger. The environments became more complex. The financial and operational impact of decisions became more significant. More people became involved, more stakeholders had opinions and more situations required judgement rather than simple process adherence.

What surprised me was not how much leadership changed as those responsibilities increased.

What surprised me was how often the strongest teams seemed to require less direct leadership than the weaker ones.

That observation felt counterintuitive at first. Surely the most successful teams would depend heavily on strong leadership. Surely the leader would be at the centre of every important decision, providing direction and ensuring the organisation stayed on course.

Yet when I look back at the teams that impressed me most throughout my career, that is not what I remember.

I rarely remember the instructions I gave.

Instead, I remember the moments when instructions were unnecessary.

I remember customer issues that were already being investigated before they reached me. I remember risks that were identified, analysed and escalated with recommendations already attached. I remember difficult stakeholder conversations being handled professionally by people who understood the situation well enough to act without waiting for permission. Again and again, I found myself working with teams that seemed capable of moving forward without constant guidance.

At first, I assumed this was simply a reflection of experience. Talented people tend to perform well. Experienced people tend to require less oversight. That explanation made sense, but over time it began to feel incomplete.

The pattern appeared too consistently.

Some teams seemed capable of producing ownership, accountability and sound judgement regardless of which individuals happened to be part of them. New people joined and gradually adopted the same behaviours. Standards remained relatively stable despite changes in personnel. The team appeared to have a way of operating that extended beyond any single individual.

The more I observed it, the more I began to question my assumptions about what I was actually seeing.

The environment teaches people how to operate

One of the most important clues came from watching new people enter established teams.

Like many leaders, I spent years believing that high-performing teams were primarily built through strong hiring decisions. Bringing in capable people obviously matters. Experience matters. Technical expertise matters. Good judgement matters. Nobody builds a successful team by accident.

However, there was something else happening that hiring alone could not fully explain.

New team members often adapted much faster than expected.

They still had to learn systems, customers, processes and internal relationships, but many of the behaviours that made the team effective seemed to transfer surprisingly quickly. People who had only recently joined would begin demonstrating the same ownership, preparation and accountability as colleagues who had been there for years.

Nobody was forcing these behaviours.

Nobody was issuing daily reminders.

In many cases, nobody had even formally explained them.

The environment itself appeared to be teaching people how to operate.

When meetings were consistently well prepared, new people started preparing thoroughly for meetings. When issues were escalated early rather than hidden, new people learned to escalate concerns before they became problems. When accountability was treated as normal rather than exceptional, ownership gradually became part of how people approached their work.

Looking back, this seems obvious.

At the time, it was a significant shift in how I thought about leadership.

I had spent years focusing on the quality of individuals. Increasingly, I found myself paying attention to the quality of the environment surrounding them.

Strong teams were not simply collections of strong people.

Strong teams created conditions that encouraged strong behaviours.

That distinction sounds subtle, but it changes how leadership is viewed.

If performance is primarily the result of individual talent, then leadership becomes largely a hiring exercise. Find good people and stay out of their way.

If performance is heavily influenced by environment, culture and expectations, then leadership becomes something different. It becomes the deliberate creation of conditions that make desired behaviours more likely to emerge.

What teams learn from behaviour

The longer I spent in leadership roles, the more I noticed that teams paid remarkably close attention to behaviour.

Far more attention than they paid to presentations, values statements or leadership messaging.

Most organisations can articulate what they stand for. They can describe their values, define their culture and explain how people are expected to behave. There is nothing wrong with that. Clear expectations are useful.

What matters far more, however, is whether those expectations survive contact with reality.

Teams notice inconsistencies immediately.

If transparency is encouraged but bad news is punished, people learn that transparency is risky. If accountability is celebrated but standards are applied differently depending on who is involved, people learn that accountability is conditional. If ownership is encouraged but every meaningful decision requires approval, people learn that ownership has limits.

These lessons are rarely taught directly.

They are absorbed through observation.

People watch how leaders react under pressure. They observe which behaviours are rewarded, which behaviours are ignored and which behaviours create opportunities. Over time those observations become assumptions, and those assumptions gradually become culture.

This is one of the reasons I have become increasingly interested in leadership as a systems problem rather than a personality problem.

Many leadership discussions focus on individual traits. Confidence, communication skills, decisiveness and emotional intelligence all matter. However, the strongest teams I have encountered were rarely built solely on the personality of a single leader.

They were built on systems of trust, expectations and behaviours that remained visible long after the leader had left the room.

Trust as an operational capability

Trust is perhaps the clearest example of this.

It is also one of the most misunderstood.

Trust is often discussed as a relationship quality, something that improves morale, engagement and teamwork. While those outcomes are important, I have often found that the operational impact of trust is even more significant.

The first sign of declining trust is rarely emotional.

The first sign is usually friction.

Decisions that once required a short conversation begin requiring multiple meetings. Email chains grow longer as more people feel the need to be included. Straightforward questions are escalated because individuals no longer feel comfortable making decisions independently. More effort is spent creating evidence, documenting conversations and protecting positions than solving the underlying problem.

From the outside, the organisation often appears productive. Calendars remain full. Discussions continue. Work is still being completed.

Yet momentum gradually slows.

The same outcomes require more effort, more coordination and more oversight than before.

Over time, the cost becomes substantial.

This is why trust has always felt less like a soft skill to me and more like an operational capability. Trust influences the speed at which decisions are made, the willingness of people to raise concerns, the confidence they have in exercising judgement and the amount of unnecessary friction that exists within a system.

The absence of trust creates work.
The presence of trust removes it.

Creating capability, not dependence

Looking back, I no longer believe the primary purpose of leadership is directing people.

Direction will always matter. Decisions will always matter. Accountability will always matter.

What has changed is my understanding of where the greatest leverage exists.

The strongest leaders I have worked with were not creating dependence. They were creating capability.

They invested time helping people understand how decisions were made rather than simply announcing decisions. They encouraged judgement rather than compliance. They built trust deliberately, applied standards consistently and created environments where ownership felt natural rather than forced.

As a result, the teams around them became increasingly self-sufficient.

Problems surfaced earlier. Decisions moved faster. Difficult conversations happened before they became crises. Leadership remained important, but its role gradually shifted from controlling outcomes to shaping the conditions that influenced those outcomes.

When I think about the teams that achieved the most throughout my career, I rarely remember the moments when a leader stepped in and saved the day.

I remember the moments when they didn't have to.

Those moments were never accidental. They were the result of trust, ownership and shared expectations built patiently over time.

The longer I spend in leadership, the more convinced I become that leadership is not measured by how many decisions flow through a leader.

It is measured by how many good decisions continue to happen when the leader is not there.