What a Military Command Structure Knows About Decisions That a Boardroom Doesn't

When a real disruption hits a supply chain, the first cost is rarely the disruption itself. It's the time spent figuring out who is actually allowed to decide what happens next.

Watch it happen inside most organizations facing a genuine crisis, a supplier failure, a shipping route closing, a freight cost doubling overnight, and the pattern is remarkably consistent. Someone raises the alarm. A meeting gets scheduled, sometimes urgently, sometimes not urgently enough.

The people in that meeting discuss the problem clearly, often intelligently, and then reach the real bottleneck: nobody in the room is quite sure whether they're actually authorized to approve the response being discussed, so it escalates further, to someone who wasn't in the first meeting and now needs to be briefed from the start. By the time authority and information finally meet in the same room, the cheapest, fastest response window has usually already closed.

This isn't a competence problem. The people involved are almost always capable. It's a structural one, and it's worth naming precisely: most commercial organizations decide who is allowed to decide during the crisis, not before it.

A Different Model, Built for the Opposite Problem

Military command structures were built to solve exactly this failure, because in that environment, the cost of decision paralysis isn't a missed delivery window, it's measured in lives. The doctrine that emerged from that pressure is generally known as mission command, and its core principle is simple to state and genuinely difficult to build: a subordinate commander is given clear intent, the actual objective, and a pre-defined boundary of authority, and is then expected to act immediately within that boundary, without escalating every decision back up the chain first.

The authority isn't negotiated in the moment. It's assigned in advance, calmly, before anyone is under real pressure, specifically so that when pressure does arrive, the only open question is what to do, never who gets to decide it.

What This Actually Looks Like Outside a Military Context

I spent time building exactly this structure in a civilian, public-sector procurement environment, not as a theoretical exercise, but because the organization had none of it. Every purchasing decision, regardless of size or urgency, routed through the same narrow approval chain, because no one had ever formally defined who was authorized to approve what.

The fix wasn't more oversight. It was less centralized oversight, applied more precisely. Authoring formal delegation-of-authority thresholds, clear, written boundaries defining exactly what value and category of spend could be approved at which level, without escalation, meant that routine and moderate-risk decisions could be made immediately, by the person closest to the actual problem, while genuinely high-risk or high-value decisions still escalated, deliberately, to where they belonged.

That's the entire principle of mission command, translated directly into procurement governance: not the absence of control, but control that has already made its decisions about where authority sits, before the moment it's actually needed.

The Illustrative Comparison Worth Sitting With

Picture two organizations, both facing the identical disruption, a key supplier suddenly unable to deliver. Organization A has never defined who can approve an emergency alternative sourcing decision above a certain value. Organization B has a pre-agreed threshold: category leads can approve emergency substitutions up to a defined limit immediately, with only genuinely major decisions escalating further.

Organization A loses two, sometimes three days simply establishing who is allowed to say yes, while the actual disruption compounds in the background. Organization B has often already resolved the immediate problem in the same window, not because its people are better, but because the organization had already answered the authority question before it needed the answer.

This is playing out at real scale right now. Much of the freight volatility currently running through GCC supply chains, tied to Hormuz and Red Sea routing disruptions, is being met by organizations discovering, in real time, whether they actually know who's allowed to approve an emergency alternative. Some do. Most, based on how long these responses typically take, clearly don't.

Why This Belongs in a Strategy Conversation

This isn't really a procurement or logistics question, and treating it as one understates what's actually at stake. It's a question about how an organization designs authority itself, whether decision rights are a living, pre-built structure the organization can rely on under pressure, or an improvised negotiation that only gets sorted out live, expensively, in the middle of the exact moment when speed matters most.

The honest audit worth running isn't "do we have a crisis response plan." Almost every organization has one of those, usually a document. The question is: does the person actually facing the next disruption already know, today, calmly, exactly what they're authorized to decide without asking anyone, or will that boundary only get discovered live, under pressure, the next time it's tested.

Most organizations have never actually answered that question in writing and the ones that have usually aren't the ones losing three days to figure out who's allowed to say yes.