Build Teams That Move Fast Without Waiting for Permission

A pyramid-shaped hierarchy makes every decision climb to the top before anyone acts on it. That works in a stable, predictable world. The alternative is a team of teams. It connects separate, capable units into one network, so information moves freely and decisions happen at the point of action. Every part of the organisation sees the full picture and acts on it directly, on its own initiative.

Push Authority to the People Who Can Act on It Fastest

• Run a daily, all-hands meeting where the price of admission is contributing real information, including problems and failures.
• Replace the "need to know" default with radical transparency, sharing information broadly with every level.
• Build shared consciousness, a common understanding held across every level, so people can decide fast without waiting for instructions.
• Write a one-page narrative combining an honest current-state account with a clear future direction.
• Share the purpose behind every task, not just the task, so a team can adapt on its own when conditions change.
• Map which decisions can only be made at the very top, then put everything else in writing for the level below.
• Manufacture trust between disconnected teams deliberately, by embedding people from one unit inside another.

Why Connected Teams Outpace a Single Chain of Command

A team of teams connects separate, capable units into one network. Intelligence gathered anywhere becomes instantly available everywhere. Each unit still keeps its own specific capability. This is not the same as merging distinct teams into one undifferentiated group. It means what one team learns becomes the whole organisation's advantage.

The cost of getting this wrong is concrete. Special-operations raids (military missions to capture or gather intelligence on a target) in Iraq produced documents, computers, and phones. Those went into a supply closet, because translators and analysts were too overloaded to process them in time. By the time anyone reviewed the contents, the intelligence was weeks old and worthless. Each unit was excellent within its own function. Collectively they were ineffective, because none of them shared what they knew. The opposing network, by contrast, used commercial cell phones and the internet to coordinate faster than far more expensive official systems could match.

How Radical Transparency Replaces Need-to-Know Thinking

Sharing information broadly produces faster, better decisions than restricting it. No one can predict in advance who will need a given piece of information. So the old "need to know" default, which reaches only people with an identified reason, quietly blocks the awareness that makes an organisation fast.

A daily, all-hands video call became the operating picture for an entire organisation. It reached thousands of participants, from front-line operators to the people supporting the mission elsewhere. The call worked because the norm was explicit. Every participant was expected to contribute, not just receive. Direct, open-ended questions made a short non-answer visibly insufficient. Over time, contributing substance became the expected standard rather than a brief, reassuring status update. People who watched colleagues elsewhere struggle with the same mission began to feel its shared weight. "We're all in this together" stopped being a slogan and became a felt reality.

Turn Shared Awareness Into a Narrative Everyone Can Act On

Shared consciousness is the common contextual understanding that lets people self-organise without waiting for top-down direction. It depends on a clear organisational narrative. The right format is one page, not ten. A vision document too long to hold in mind cannot guide daily decisions.

That one page combines two things. First, an honest account of where the organisation actually stands. Second, a clear direction for where it is going. Aspirational language disconnected from reality produces cynicism, not alignment. One striking example reframed a routine infrastructure upgrade, replacing pipes under a city, around a four-word mission that connected every disrupted street to something residents cared about. Commander's Intent works the same way for a single task. It names not just what to do but why. So if the original plan becomes impractical, the team can ask what else achieves the underlying purpose, instead of waiting for new instructions.

Push Real Decision-Making Authority Down the Organisation

A leader who names which decisions only they can make usually finds the honest answer is a small handful, three or four at most. Everything else gets written out. Then people at every level know exactly what they are authorised to decide without asking. This directly resolves choke points, the places where coordination stalls and work backs up. Those are usually a symptom of decisions concentrated at the wrong level, not any individual failing at their job.

The evidence is practical. A well-known hotel chain let any employee spend up to three thousand dollars to resolve a guest problem without approval. The data showed employees spent closer to two thousand five hundred dollars when warranted. People closest to a problem make responsible decisions when trusted with real authority. The rule for how far to push authority down is simple. Keep going past the point where it feels comfortable, then go one level further. That discomfort is the signal authority is finally reaching the people closest to the problem.

Manufacture Trust Instead of Waiting for It to Grow

Trust between teams that rarely interact can be built deliberately. Embed people from one unit temporarily inside another. They form personal relationships. Then they can call a known person directly instead of contacting a faceless department. Departmental silos form naturally, through habit and the tendency to communicate mainly with people you already know, not through bad intent. They stay invisible from the inside, because each silo looks like a well-functioning team on its own terms.

The 9/11 Commission found that every piece of information needed to prevent the attacks already existed somewhere inside government agencies. It simply never crossed organisational boundaries. That is the cost deliberate trust-building is designed to prevent. Remote or distributed teams need the same trust, built through deliberate non-work conversation and personal disclosure. Treating every interaction as purely functional erodes the relational fabric fast collaboration depends on. A practical test for connection is simple. Can you name a specific priority for another team right now? If not, invite someone from that team into an informal conversation and learn what matters to them.

Build a System That Detects Threats Before They Become Crises

A working risk-detection system is modelled on the human immune system. The body faces an estimated 15,000 daily threats, and the immune system continuously identifies, assesses, and neutralises them. An organisation needs the same continuous early warning. Technology and data extend its ability to sense market shifts at a scale no individual could observe directly. The discipline that makes this reliable is one rule. Test every automated or AI-generated output against direct experience and common sense before acting on it.

One example shows why. In 1983, a Soviet officer monitoring a nuclear early-warning system saw an alert reporting five incoming missiles. He delayed passing it along. A genuine first strike would never arrive as only five. His hesitation prevented a possible retaliatory launch against a false alarm.

The same discipline applies to confirmation bias, the habit of weighting information that confirms existing beliefs and discounting what challenges them. It intensifies inside groups of similar people who reinforce each other's assumptions. Two exercises counter it. In a red team, a group with no stake in a plan is tasked with finding ways to defeat it. In a pre-mortem, a group assumes a plan has already failed and works backward to explain why. Both create room to voice real concerns before the cost of being wrong becomes real. Genuine diversity of perspective helps too. It means different professional training, not demographic variation alone. That is what lets an organisation see a threat from an angle a uniform group would never notice.

Act Decisively When the Moment to Adapt Arrives

Adaptability is the willingness to respond to a threat. Timing is the discipline of acting when the moment is right. These are distinct capacities. Together they determine whether a strong position survives a shift in the market.

One video-rental chain with thousands of locations declined an early offer to buy a small mail-order DVD competitor for fifty million dollars. It dismissed the smaller company's casual culture. Within a decade the chain was bankrupt. The competitor it had turned away grew to a market value of five hundred billion dollars. Treating inaction as a deliberate choice, not a safe default, is what protects a strong position from this kind of reversal. The same logic applies to bold, deliberate risk. An elite military force once committed two-thirds of its strength to a single region at once. That pace was unsustainable and risked breaking a capability that takes roughly a decade to rebuild. The call was made anyway, because not acting represented the greater danger. Playing not to lose is its own path to loss.

Build the Character That Holds Under Real Pressure

Genuine convictions produce reliable behaviour only when paired with the daily discipline to act on them. The formula is that character equals convictions multiplied by discipline. That discipline can be built deliberately, by anyone, at any stage. It does not depend on a fixed trait some people are born with and others are not.

A struggling young cadet came close to expulsion in his second year. His trajectory turned around after a mentor told him directly what he was capable of becoming, rather than cataloguing what he had failed at. The shift in attitude was almost immediate. Character carries no external reward, only internal commitment and the respect of people who matter. That is why the discipline to act on stated values when no one is watching separates character that holds from character that quietly erodes. The most important time to do what is right is when it is difficult. Naming in advance which lines you will not cross is what makes it possible to hold them once real pressure arrives.

Use Setbacks as the Starting Point for What Comes Next

Public failure, even career-ending failure, can become the foundation for a new direction. The condition is treating it as a starting point rather than dwelling on it. A leader who accepts responsibility for an organisation's failure, regardless of personal fault, is owning the conditions subordinates operate in. From there they can rebuild, using everything already accumulated in discipline, values, and experience.

After action reviews examine outcomes honestly. They apply equally to successes and failures. A lucky win left unexamined teaches the wrong lesson just as easily as an unexamined loss does. The real test after any setback is a single question. Does the lower standard become the new normal? Or is the honest response to look clearly at what went wrong and commit, not to perfection, but to doing better tomorrow?

Go deeper with what matters to you

The source works through several mechanics in step-by-step detail. It walks through the exact "find, fix, finish, exploit and analyse" targeting cycle. That cycle measures choke points in real time. It details the brief-back technique for confirming a team understood an assignment. It also recounts one high-stakes operation, the defining test of distributed trust.

Maybe you are weighing how far to push decision-making down in your own team. You can bring that exact situation into the chat below. The same applies if you are trying to build trust with a department you rarely interact with. Or you might be working out whether a piece of data deserves your trust or your scepticism. Bring the specifics of your organisation and work through them against the principles in this source.

Where these ideas come from

These ideas come from Battlefield Tactics for Business Success, an online course published in September 2025. It is taught by retired four-star General Stanley McChrystal (a senior US Army officer who later led the country's most elite counterterrorism units). He commanded the United States' Joint Special Operations Command (the umbrella command overseeing those elite units) and all coalition forces in Afghanistan. He built and tested the team of teams model under live operational pressure in Iraq. He then applied the same principles as a leadership consultant to organisations including Intuit, Pfizer, Bank of America, and Airbnb, and as a teacher at Yale.

What you read here is our own source, an independent work built from those ideas. Every concept has been studied and then rewritten from scratch and reshaped so it can answer your questions alongside other refined sources. Nothing from the reference work has been copied. The knowledge has been transformed, not reproduced. The reference is named clearly because the ideas deserve proper credit and because this work stands on its own merits.