Commander's Intent
Set the end state, leave the how to your people
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 78%
Commander's Intent is the core of military mission command: a leader communicates the desired end state and the reason behind it, then leaves the method entirely to the individual. Because the 'how' belongs to the doer, they take genuine ownership and work through obstacles rather than clocking off. A second benefit is unpredictability: if a leader dictated every move, an enemy who learns the pattern can ambush; distributed decision-making keeps behaviour varied and adaptive. The mechanism runs on a common language of intent rather than orders, so trust and relationship replace rank. Yapp contrasts this with the myth of command-and-control militaries, noting that if you have to pull rank you have already failed to build the relationship that makes people deliver.
Origin
Roderic Yapp learned this as a Royal Marines officer running combat teams in Afghanistan and counter-piracy operations off Somalia, then carried it into corporate leadership coaching through his firm Leadership Forces.
Core principles
- 01Define the future you want, not the route to it
- 02Ownership grows when people own the method
- 03Predictable is exploitable; leave room for judgment
- 04Rank is a fallback, not a leadership tool
- 05Support and resource, don't micromanage
How to run it
- 1
Define the end state
Tell the person the specific future you want them to reach. Frame it as an outcome to achieve, not a task list.
Pro tip Say it in one sentence they could repeat back to a third party.
- 2
Explain the intent behind it
Give the reason the end state matters so they can make aligned judgment calls when reality shifts.
Watch out Skipping the 'why' forces people back to you for every deviation.
- 3
Hand over the how
Explicitly make the method theirs. Tell them the route is up to them and you are not going to prescribe it.
Watch out Prescribing the method after saying it's theirs destroys the ownership you were trying to create.
- 4
Offer support and resource
Make clear they can come back for help or extra resource without penalty. Availability is not the same as interference.
Pro tip Position yourself as there to help them succeed, not to check up on them.
- 5
Judge the outcome, not the path
Assess whether the end state was met. Resist grading the route they chose if it worked.
Pro tip When their method beats yours, say so publicly.
Watch out Retro-critiquing a successful method teaches people to ask permission next time.
In the wild
Yapp needed to book a hire car to visit a firing range in Castle Martin. Rather than being told exactly what to book, a corporal asked where he was going, then arranged for the car to arrive the night before so he could leave early, included the bridge toll tag, and upgraded to a bigger car for comfort. By seeking the underlying intent, the subordinate delivered far more value than a literal instruction would have produced.
→ A routine task was executed better than specified because the doer owned the how.
Common mistakes
Prescribing the method
Telling people exactly how to do it strips ownership and makes them stop thinking, so they deliver the letter of the order and nothing more.
Relying on rank to get compliance
If you have to say 'because I'm your commanding officer,' you have already failed to build the trust that makes intent-based leadership work.
Is it for you?
Best for
Leaders managing capable people in fast-moving or chaotic conditions where central control breaks down.
Not ideal for
Life-or-death moments needing an immediate directive, or people not yet trained to standard.
From the transcript
“This is the end state that I set you. This is the future that I want you to get to. How you achieve that, totally…”
“I think if you have to rely on your rank in the military, you failed somewhere along the line to build trust.”
From the episode
Lessons From Afghanistan & Capturing Somali Pirates - Roderic Yapp - #133
Roderic Yapp