How to Empower Teams to Act Without Constant Approval

The fastest teams succeed not through superior individual talent but by ensuring the person closest to a problem has the authority to solve it. When decision-making power sits at the point of action rather than the top of a hierarchy, an organisation gains the agility to outpace competitors who remain trapped in traditional approval loops.

The key things to understand about decentralised leadership

• Pyramid hierarchies fail in complex environments because information cannot travel to the top and back fast enough to remain relevant.
• Shared consciousness creates a common mental map that allows separate teams to coordinate without constant oversight.
• Choke points in a process are usually the result of concentrated authority rather than a lack of skill or effort.
• Delegating authority requires a leader to push power down until they feel uncomfortable, as that discomfort signals the right level of trust.
• Trust between disconnected departments is best built through deliberate personal connections and cross-functional immersion.

Why traditional hierarchies fail in a fast-moving world

A traditional pyramid structure is designed to send decisions up to the top and instructions back down to the bottom. This model was perfected during the industrial age when the world moved slowly and the future was largely a repetition of the past. In a stable environment, a single brilliant mind at the peak of the pyramid can effectively manage every significant variable. However, this structure becomes a terminal bottleneck when conditions change faster than a decision can climb the corporate ladder and return.

The core problem is that a single leader, no matter how capable, cannot pre-plan a response to a situation that nobody predicted. When an organisation produces the same product year after year, the hierarchy provides order. When that same organisation faces a volatile market or a rapid technological shift, the hierarchy provides only delay. The friction of waiting for permission becomes a greater threat than the risk of a local mistake. A structure that prioritises control over speed will eventually be outpaced by any network that has pushed decision-making authority down to the people closest to the work.

The most useful realisation for any leader is that the rules designed to protect information are usually the same rules that slow the entire organisation down. Shifting away from this model is a structural change rather than a personal one. You do not necessarily need better people or a harder-working executive team. You need a system where authority sits closer to the problem and where every team member is empowered to act on what they see in real time.

Connecting separate teams into a unified network

Creating an agile organisation does not mean merging every department into one giant, formless group. Efficiency still requires specialised units with distinct skills. The goal is to build a network where these separate and capable units stay distinct but link into a single, cohesive system. In this model, intelligence gathered by one team becomes instantly available to every other team in the network, removing the silos that typically hide critical information.

The cost of operating without this connection is high. In many large organisations, different elite units or departments operate in the same space without sharing what they know. Vital intelligence can sit unread in a digital folder or a supply closet for weeks simply because the people who found it are not the people who can act on it. The capability to succeed exists within the building, but it cannot be combined. Combination is where the competitive advantage lives, and a network architecture is what makes that combination possible.

Consider the common friction between product development and sales. When these teams have no real-time connection, sales staff may promise features that the product team cannot build, while the product team builds tools that customers do not actually want. This happened at Scott’s Miracle-Gro, where the two functions were so separate that they essentially worked at cross-purposes. A network fixes what a stack of separate boxes cannot by ensuring that every part of the business is responding to the same reality.

Establishing shared consciousness through radical transparency

Most organisations run on a “need to know” default setting. Information only reaches people if a manager has identified a specific reason for them to have it. While this sounds prudent for security or focus, it is the primary cause of organizational silos. You cannot predict in advance who will need which piece of information to solve a problem that has not happened yet. To move fast, you must move from “need to know” to “ready to share.”

Shared consciousness is a common understanding of what is happening and what the group is trying to achieve, held at every level of the company. It is built by sharing far more information than feels comfortable. This might involve a daily all-hands meeting where the price of admission is contributing real, raw information, including problems and failures, rather than a polished status update. When thousands of people share the same picture of the environment, they begin to self-organise. They make good calls without waiting to be told because they understand the context as well as the CEO does.

The meeting itself is not the goal. The goal is the shared mental map that the meeting produces. Once people carry that map, the need for constant coordination meetings disappears. They already know what their colleagues are doing and why it matters. This transparency builds a level of trust that allows for rapid, independent action. If everyone sees the same data, they are likely to reach similar conclusions, which reduces the friction of decentralised decision-making.

Leading with intent rather than instructions

Shared information requires a shared story to hold it together. This narrative should be an honest account of where the organisation stands and a clear direction of travel. Honesty is the most important element here. Aspirational language that has no grounding in the daily reality of the staff breeds cynicism rather than commitment. People need to know the truth of the situation if they are expected to take responsibility for the outcome.

A key tool in this shift is the concept of Commander’s Intent. This means explaining the purpose behind a task rather than just the task itself. When a team understands the “why” behind their orders, they can adapt sensibly the moment conditions change. If the original plan becomes impossible, they don’t freeze and wait for new instructions. They use their understanding of the intent to improvise a new path toward the same goal. The purpose of the mission travels with them into the field.

To ensure this intent is actually understood, leaders can use the brief-back technique. This involves asking a team to repeat what they understood the mission to be after they have been briefed. It is a simple check that catches misunderstandings before any resources are committed. It might cost five minutes at the start of a project, but it can save months of wasted effort. It ensures that the autonomy you are giving your team is grounded in a clear, shared objective.

Pushing authority to the point of friction

None of the communication or transparency matters unless the authority to act actually moves down the hierarchy. Choke points, where work backs up and coordination fails, are almost always a symptom of decisions being concentrated at the wrong level. If a frontline worker has to ask three managers for permission to fix a customer’s problem, the organisation is choosing control over its own survival. To fix this, you must name the small handful of decisions that genuinely must stay at the top and then push everything else down in writing.

A useful rule for this transition is to delegate until you feel uncomfortable, and then go one more level. That feeling of discomfort is not a sign that you are doing something wrong (it is a sign that you are successfully releasing control). When authority reaches the right place, the people doing the work feel the weight of responsibility and the freedom to excel. This shift often reveals that employees are far more capable and cautious than their managers assumed.

One major retailer famously allowed staff to spend a significant sum to resolve any customer issue without seeking prior approval. When given this freedom, employees did not abuse the budget. Instead, they used their judgement to solve problems efficiently, often spending much less than the allowed limit. Trust, when offered clearly and structurally, tends to be repaid with high performance. Helping a team move past the fear of making a mistake is the most important work a leader can do during this transition.

Building trust through deliberate immersion

Silos are rarely the result of people trying to be difficult. They form through simple habit and the natural human tendency to communicate mostly with people we already know. Over time, these habits harden into walls. Each department begins to view other departments as obstacles rather than partners. Because these silos look like healthy, cohesive teams from the inside, they are difficult to spot until they start causing project failures.

You cannot wait for trust to grow organically between disconnected teams. You have to manufacture it. One effective method is to embed members of one team into a rival or distant department for several months. These “liaison officers” build real personal relationships and learn the language and pressures of the other group. When they return to their original team, they act as a bridge. When a crisis hits, people can call a human being they know and trust instead of sending a formal request to a faceless department.

This is especially critical for remote or cross-functional teams. If interaction is limited to functional tasks and status reports, the personal trust required for fast collaboration slowly disappears. Deliberate effort must be made to create personal connections across the organisation. Trust is the lubricant that allows a network to move at high speed without grinding itself to pieces. It turns a group of separate units into a single, responsive entity.

Using data to inform but not replace human judgement

A fast-moving team must be able to sense threats before they arrive. This can be modelled on the human immune system, which constantly scans for and neutralises thousands of hazards every day without needing a conscious decision from the brain. In a business context, this means using technology and data to sense market shifts and internal inefficiencies. However, every piece of data must be tested against direct experience and common sense before action is taken.

Data should inform a decision, but it should never be allowed to quietly make the decision for you. There are famous instances where automated systems provided false alerts of catastrophic threats, and only the intervention of a human officer who trusted his own judgement prevented a disaster. As automated tools and AI become more prevalent in the workplace, the habit of applying human oversight becomes more important, not less. We use the machines to see the patterns, but we use our character and experience to decide what they mean.

Two specific exercises can help sharpen this collective judgement. The first is a red team, which is a group with no stake in a particular plan who are tasked with finding ways to defeat it. The second is a pre-mortem, where a team assumes a project has already failed and works backward to explain why. Both of these techniques release the social pressure that usually stops people from voicing concerns. They allow a team to surface risks while they are still cheap and easy to fix, ensuring that the speed of the team is matched by its stability.

The role of character in a decentralised system

A decentralised system relies entirely on the character of the people within it. Character can be defined as convictions multiplied by discipline. A belief in the mission means nothing if there is no daily discipline to act on it when things get difficult. In a team where decisions are pushed down, every person is expected to act like a leader. This requires an internal commitment to the goal and an honest reckoning with personal and collective failures.

This reckoning must include the ability to handle setbacks. In a high-speed environment, failure is inevitable. The key is to treat every setback as a starting point for the next attempt rather than an ending. When a team is built on trust, a mistake becomes a data point for the whole network to learn from, rather than a reason to hide information. This culture of accountability is what allows a leader to step back and let the team run.

Ultimately, a team that can act without permission is a team of people who have learned to trust themselves. When you remove the barriers of hierarchy and the fog of siloed information, you allow the natural talent of your people to surface. Leadership in this environment is not about making every call. It is about building the system, nurturing the culture, and then having the discipline to get out of the way so the team can do what they were hired to do.

Creating a culture of autonomous action

Moving away from a command-and-control structure is a significant undertaking that requires more than just a change in the org chart. It requires a fundamental shift in how information is shared and how trust is granted. By focusing on shared consciousness and empowered execution, you create an environment where the fastest possible response is also the most informed one. This doesn’t just make the organisation more efficient; it makes it more resilient to the unexpected shocks of a complex world.

The transition starts with a commitment to transparency and a willingness to accept the temporary discomfort of delegating power. As the network begins to form and the silos begin to break down, the speed of the entire organisation will naturally increase. The goal is a team where leadership is a shared responsibility, and where the collective intelligence of the group is fully utilised. When everyone knows what needs to be done and has the authority to do it, the need for permission simply disappears.