There is a genre of leadership advice that borrows its authority from military service, and most of it borrows the wrong things. It emphasizes intensity, hierarchy, physical hardship, and a particular register of motivational language. It is popular, it sells, and it transfers poorly, because it has taken the aesthetic of military practice while leaving behind the parts that actually produce results.
I spent more than twenty years on active duty in the United States Coast Guard. What I would tell you is that the useful inheritance is almost entirely unglamorous. It consists of a small number of instruments for finding out what actually happened, and a professional culture in which using them honestly is an obligation rather than a virtue. None of it involves raising your voice.
What does not transfer
It is worth being direct about the limits, because a coach who claims that military experience confers general authority is making a claim that will not survive examination.
Rank does not transfer. In an operational setting, direction produces action because the structure guarantees it. A civilian client can listen politely to every recommendation, implement none of them, and hire someone more agreeable. This constraint is healthy — it means a method has to earn its authority on the merits, in every engagement — but it means the habits built inside a chain of command require deliberate translation.
Physical hardship as a teaching device does not transfer, and it is where the genre goes furthest wrong. Military training uses controlled adversity for specific purposes: to establish that a recruit can function while uncomfortable, to build group identity under shared stress, and to screen. None of those purposes is served by a business audience being told to wake at four in the morning. Discomfort is not itself instructive. It is instructive only when it is paired with a debrief, and the debrief is the part that gets omitted.
Urgency as a permanent operating condition does not transfer either. Emergency response is episodic by design, with recovery built between operational periods. A business or an individual run at emergency tempo indefinitely does not become resilient; it becomes depleted, and the depletion is usually mistaken for a personnel problem.
The first instrument: the After Action Review
The single most valuable transferable practice is the structured debrief, known across military services as the After Action Review. Its structure is four questions, and its power is entirely in the discipline of asking them in order.
- What was supposed to happen?
- What actually happened?
- Why was there a difference?
- What will we do differently?
Every organization believes it does this. Very few do, and the difference is visible in the first question. An AAR requires a documented statement of intent that predates the event, which means the plan has to have been specific enough to be compared against. Most business reviews cannot answer question one, because the plan said something like improve customer retention, and any outcome is consistent with that. Without a specific answer to question one, question two has no reference point and question three becomes an exercise in narrative construction.
The second thing that distinguishes a real AAR is the framing, which has to be stated aloud at the start and then defended when the room drifts: the review evaluates the plan, not the people. This sounds like a soft framing and it is the opposite. It is what makes the review productive, because the moment participants believe they are being evaluated, they begin managing their exposure, and information stops flowing. A review that produces only defensible accounts has told you nothing you did not already know.
The underlying premise is worth stating explicitly, because it is genuinely counterintuitive to most managers: a gap between intent and outcome is information about the plan's design at least as often as it is information about the executor's effort. When a plan required nine hours a week from a calendar with four available, the person who missed five hours did not lack discipline. The plan was defective, and the defect was in the room when it was written.
The second instrument: the honest short report
The Situation Report — SITREP — is a brief, regular, standardized account of current status. In operations it answers what has been accomplished, what has not, what has changed in the environment, and what support is required. Four questions, submitted on a fixed cadence.
Two design features make it work, and both are routinely violated when organizations adopt the idea.
It is short. A report that takes an hour to compile will not be submitted during a difficult week, which is precisely the week the report matters most. Ten minutes is the design target, and if the format cannot be completed in ten minutes, the format is wrong. I have seen organizations adopt weekly reporting, build a template requiring forty minutes of data assembly, and conclude within two months that their people lack accountability. Their people were making a rational decision about a badly designed instrument.
And it is explicitly not a progress performance. The SITREP's value is highest when the news is bad, because that is when a course correction is available and cheap. This requires a culture where reporting an unmet commitment carries no penalty beyond a diagnostic conversation — which in turn requires the recipient to demonstrate, repeatedly, that bad news produces help rather than consequences. That demonstration takes months and can be destroyed in one exchange.
A case worth describing: a division president submitted SITREPs consistently late and consistently vague. The obvious reading is disengagement, and the obvious response is escalation. Treating the pattern as data instead produced a different finding. The report format required three metrics his systems could not generate weekly, so every submission involved manual assembly he had begun to resent. The instrument was broken, not the executive. Redesigned around numbers his dashboards already produced, submissions became prompt and specific. Escalating on adherence would have damaged the relationship and fixed nothing.
The third instrument: bounded planning cycles
Operational planning works in operational periods — bounded intervals with their own objectives, assignments, and review. Nothing is planned indefinitely. Every commitment has a horizon, and at the end of that horizon there is a formal look at what happened and a deliberate decision about what comes next.
Business and personal planning tend toward the opposite: annual objectives, quarterly checkpoints, and continuous initiatives with no defined end. This produces a specific pathology. When a plan has no bounded review point, adjustment happens either never or continuously. Never means the plan is defended past the point where evidence contradicts it. Continuously means there is no plan, only a series of reactions.
A four-to-six week cycle is long enough to produce real evidence and short enough that a wrong plan is not expensive. In practice, the effect on individual clients is disproportionate to how mundane the change sounds. A twelve-month objective is a source of ambient guilt and cannot be evaluated until it is too late to matter. A six-week block with three objectives is executable, and its result is known in six weeks.
FEMA's doctrine on incident action planning is explicit about this structure. The process is drawn as a letter P: the leg of the P holds the steps performed once at the start of an incident, and once those are complete, management shifts into a cycle of planning and operations, informed by ongoing situational awareness and repeated each operational period. The cycle is the normal state of things. The linear sequence is only the entry.
The fourth instrument: the obligation to say it
This one is cultural rather than procedural, and it is the hardest to transplant.
In a well-functioning operational unit, identifying a problem is an obligation rather than an act of courage. If you see a hazard, a defect, or a plan that will not work, you are required to say so, and saying so to someone senior is expected rather than brave. This is not because military organizations are populated by unusually forthright people. It is because the consequences of unspoken problems are immediate, physical, and attributable, so the culture has been forced to build the obligation in.
Most civilian organizations have not been forced to. The consequences of unspoken problems arrive slowly and diffusely, so silence remains locally rational for the individual even while it is collectively expensive. Everyone in the meeting knows the initiative will not work. Nobody's quarterly review will be affected by not saying so.
For a coach or consultant this becomes a specific professional obligation, and I write it into every client agreement rather than leaving it as a matter of temperament. If a client's plan is not working, they will hear it in plain language, with the evidence, and with a proposed correction. A consultant who protects the relationship at the expense of the finding is charging for company.
It matters that this obligation is documented on the consultant's side of a mutual agreement. It converts directness from a personality trait the client has to tolerate into a term of service they have purchased. And it gives the client standing to hold the consultant to it, which changes the relationship in a way that mere intention does not.
Why these four and not the rest
The common property of the four instruments above is that each is a mechanism for reducing the gap between what is believed and what is true. The AAR reduces the gap about the past. The SITREP reduces it about the present. Bounded cycles reduce it about the future by making forecasts short enough to be checked. The obligation to speak reduces it about everything, continuously.
That is the entire military inheritance worth having. Not intensity — intensity is abundant and cheap, and most of my clients arrive with a surplus of it. What is scarce is an accurate account of what is actually happening, and every one of these instruments exists to produce one.
The genre that sells military leadership as toughness has it precisely inverted. Operational competence is not primarily about enduring difficulty. It is about knowing your situation well enough that difficulty is anticipated rather than discovered. Everything else follows from that, and none of it requires anyone to shout.