What Twenty-Five Years in Uniform Taught Me About Execution

In the military, a plan that only exists on paper is not a plan. It is a hypothesis, and hypotheses do not survive first contact. That mindset, built over more than two decades of service, shaped how I think about execution in every environment since.

Planning and execution are not sequential

Corporate strategy often treats planning and execution as two phases: first you decide, then you do. Military planning treats them as continuous. A plan is built with execution in mind from the first draft, which means every objective is paired with a clear owner, a resourcing reality, and a decision point for when conditions change.

That continuity is not a stylistic preference. It comes from operating in environments where the cost of a plan that cannot survive contact with reality is measured in far more than a missed quarterly target.

Command intent, translated

One of the more transferable concepts is command intent: the practice of ensuring that everyone several levels down the chain understands not just their specific task, but the purpose behind it, so they can make sound decisions when the original plan no longer fits the situation. Most organizations issue instructions. Far fewer issue intent, which means when conditions change, people default to waiting for new instructions instead of acting on judgment.

What carries over to enterprise leadership

The specific tools of military planning do not map directly onto corporate transformation. But the underlying discipline does: build plans that assume they will need to adapt, communicate purpose deeply enough that people can act without waiting for permission, and treat execution as inseparable from strategy rather than as strategy's afterthought.

That discipline, more than any specific framework, is what twenty-five years in uniform actually taught me. Enterprise leaders spend a great deal of energy on strategic clarity. The organizations that also invest in this kind of execution clarity tend to be the ones whose plans survive contact with reality.

A plan is a hypothesis until it meets reality

Military planning treats a plan as a starting hypothesis, built with the explicit expectation that conditions will change and the plan will need to adapt without losing its underlying purpose. Corporate strategy, by contrast, often treats a plan as a fixed commitment, something to be defended and delivered as originally written. That difference in posture, plan as living hypothesis versus plan as fixed commitment, has significant consequences for how organizations respond when reality inevitably diverges from the plan.

Command intent as a transferable concept

One of the more useful ideas from military planning is command intent: making sure people several levels down the chain understand not just their specific task but the purpose behind it, so they can make sound decisions when the original plan no longer fits the situation on the ground. Most corporate organizations issue detailed instructions. Far fewer issue genuine intent, which means that when conditions shift, people default to waiting for new instructions rather than acting on judgment grounded in a shared understanding of the goal.

What actually transfers to enterprise leadership

The specific tools of military planning do not map directly onto enterprise transformation, and I am careful not to overstate the parallel. But the underlying discipline transfers cleanly: build plans that assume they will need to adapt, communicate purpose deeply enough that people can act without waiting for permission, and treat execution as inseparable from strategy, not as an afterthought to it once the strategy has been approved.