When a senior leader says team lacks initiative, they often frame it as a behavioural failing. They complain that people do not want to work hard anymore or that nobody takes personal accountability. The reality is quite different. When people refuse to step up, it is almost never an individual problem. It is a structural issue. We talk endlessly in corporate circles about empowerment, yet we trap our people in an architecture of permission.
We still design businesses using an old industrial model of hierarchy. We make a single manager the central node of all information and decision-making on a quiet Tuesday. This architecture feels comfortable in calm waters. However, when the volume of decisions exceeds the cognitive capacity of that single human being, the system bottlenecks.
The sheer speed of modern knowledge work has far outpaced the processing capability of any individual manager. If you have spent years reprimanding staff for bypassing the chain of command, you cannot suddenly expect them to act like dynamic entrepreneurs during a crisis. Retreating into narrow lanes is a rational survival response to an environment that punishes structural deviation. We need systems where the people closest to the work have the information and autonomy to execute on behalf of the whole.
Learning from the Hive
A colleague recently explored a biological metaphor that challenges our bias towards hierarchy. We automatically assume a beehive has a boss. We call the central figure the queen, implying executive authority. A honeybee colony does not rely on a conventional manager allocating each task. The queen does not direct day-to-day operations; she provides a biological anchor while remaining completely removed from operational decision-making.
The real work is entirely distributed. When foragers find a rich source of nectar, they return and perform the waggle dance to communicate the direction and approximate distance of the resource. Other foragers use this pure data sharing for their own evaluation. They do not simply accept instructions blindly; they use shared intelligence to assess the resources themselves. It is a masterclass in alignment without executive command.
This distributed capability is clearest during a crisis. Imagine a scorching summer afternoon where the temperature inside the hive rises dangerously. The colony does not convene a crisis management committee. Instead, workers instinctively increase fanning at the entrance to improve ventilation, while water collectors increase activity to aid evaporative cooling. The response emerges from workers changing behaviour based on shared environmental cues.
The Human Equivalent
Now look at the human equivalent. A major commercial product launch is failing on a Friday afternoon. The servers are crashing, payments are failing, and social media is angry. In a poorly aligned corporate structure, people wait for instructions. Software engineers point to infrastructure; marketing blames technical. The cognitive load on the senior leader becomes crushing as they act as a frantic dispatcher bridging hostile departments.
In a highly aligned team built on shared ownership, the response mimics the hive. A junior engineer diagnoses the application programming interface and updates the company in a public channel. A marketing manager reads that data and proactively pauses paid advertising. They do not wait for the chief executive. They feel the heat, understand the ultimate goal, and execute using their own judgement.
In my book Enhanced Leadership, I examine this exact tension between individual autonomy and strategic clarity. We say we want self-regulating networks, but we fail to provide the structural mechanisms to make them possible. This creates an apprentice gap in a distributed workforce. How do we teach junior members to interpret the environment accurately so they know when to act?
It is tempting to look at artificial intelligence as a magical shortcut. We rush to implement large language models, expecting technology to act as a digital waggle dance that solves communication overnight. Technology only ever amplifies the system you already have in place. It does not fix broken leadership. If your organisation is structurally siloed and driven by a culture of blame, AI will simply execute the wrong decisions much faster, automating dysfunction at scale. We must use these tools to strip away administrative burdens, freeing human capacity for the high-judgement work that actually drives a business forward.
Implications for Leaders
How do we stop directing traffic and start building lasting structural capability? You have to move away from being the central processor of all information and become the architect of the system.
Audit your bottlenecks Look at every approval that crossed your desk in the last 30 days. Identify the structural blockages preventing your team from exercising their own judgement. Pushing authority down to where the information actually lives is essential. If you are consistently signing off on minor expenses while expecting your team to manage huge commercial client portfolios, you are actively infantilising them.
Engineer radical information transparency The biological network works because the workers have access to the same high-quality data. If strategic priorities and commercial pressures are locked in a boardroom, your team is navigating in the dark. Give them the commercial data they need. You cannot expect an employee to think like an owner if you treat them like a tenant.
Allow non-fatal failures You must deliberately allow for non-fatal failures to build long-term capability. When a team member makes a decision you would have made differently, do not immediately overturn their call. Review the data they had, explore their thought process, and coach their judgement.
Implications for Coaches
When working with senior leaders, pay attention to the language they use to describe their teams. If they frequently complain about a lack of initiative, explore their approval processes. Ask them to map out a recent crisis response. Who made the first move? Who waited for permission? Challenge them to identify where they might be acting as a dispatcher rather than an architect. Help them design small experiments to step back from operational decision-making and test the system’s resilience.
Operating at the Correct Altitude
The queen bee operates exclusively at the macro level. She anchors the system and trusts it to function. As leaders, we have to learn to operate at the correct altitude. Are you constantly dipping down into your team’s daily work, checking their maths, rewriting their emails, or asking for granular updates?
Experiment for one month by setting the conditions for success, ensuring the health of the organisation, and then getting out of the way. Are you building a team that requires your constant direction to function, or are you designing a system capable of solving problems you have not even anticipated?
Until next time, keep leading, keep learning, and keep levelling up!
Follow on LinkedIn - Spotify - YouTube - Apple