Commander's Intent: The North Star That Survives First Contact

By William "Jax" Jackson

In the military, we know that no plan survives first contact with the enemy.

Maps get outdated. Comms go down. The enemy moves. If you're relying on a script, you die.

That's why we use Commander's Intent.

It's the single most important paragraph in any operation order. It describes the Endstate—what victory looks like—without dictating every single micro-step of how to get there.

It tells the troops why we're here and what we need to achieve. The how is up to them.

If the bridge is out, but the Intent is "Secure the high ground," you don't call HQ to ask for permission to swim. You find a way across the river. You adapt. You execute.

The Civilian Problem: Process Paralysis

The civilian world is addicted to "Process."

Corporate job descriptions are laundry lists of tasks. "Must be able to use Excel. Must attend weekly meetings. Must manage email."

They focus on the what, but they rarely explain the why.

This is why so many veterans struggle when they transition. We're used to operating with a clear mission. When we land in a corporate environment where the only "mission" is "follow the process," we feel lost. We feel micromanaged. We feel like we're suffocating.

But the bigger problem is how you're approaching your transition.

You're treating your job search like a checklist.

Write resume.
Apply on LinkedIn.
Wait.

That's a process, not an Intent. And when the process fails—when you don't get a call back—you freeze. You don't know what to do next because the checklist didn't tell you.

You need to stop following a process and start operating with Commander's Intent.

The Ghost in the Machine (A Navy Lesson)

I learned the difference between Process and Intent the hard way inside the Combat Information Center (CIC).

We were running a complex anti-submarine warfare drill. The screen was a waterfall of data—sonar contacts, bearings, ranges. The pressure was on.

Suddenly, the main tactical console died. The screen went black.

The room froze.

My junior sailors immediately scrambled for the technical manual. They were flipping pages, looking for the specific error code, trying to follow the "Troubleshooting Process." They were following the rules.

But while they were reading the manual, the "enemy" submarine was closing in. We were losing the fight because my team was focused on fixing a machine instead of fighting the ship.

The Chief didn't look at the manual. He looked at me and asked one question: "What's the Intent, OS1?"

I snapped out of it. "To track and neutralize the target, Chief."

"Then why are you staring at a blank screen? Get on the voice circuit and plot it manually."

He was right. The Process (the computer) had failed. But the Intent (track the sub) was still valid.

We abandoned the broken console. We grabbed grease pencils and headsets. We plotted the solution by hand. It was ugly. It was slow. But we tracked the target, and we won the drill.

If we had stuck to the process, we would have died with the manual in our hands.

The Amazon Pivot (A Corporate Lesson)

Years later, I saw the exact same dynamic play out at Amazon.

I was leading a recruiting team tasked with finding high-level software architects. These were the "Purple Squirrels"—recruiter slang for candidates so rare and perfectly qualified that they might as well be mythical. Every company on earth wanted them. None of them were job hunting.

The Process said:

Post the job.
Screen 100 resumes.
Message 50 people on LinkedIn.
Conduct 20 phone screens.
Submit 5 candidates.

My team was following the process perfectly. They were hitting their metrics. They were making the calls.

But we were failing. We weren't hiring anyone. The high-level architects weren't replying to our templated messages.

We were "doing the job," but we weren't winning.

I pulled the team into a room and erased the metrics from the whiteboard. I wrote one sentence: "Commander's Intent: Secure the architects who will build the next generation of AWS. We don't chase numbers; we hunt impact."

That shift changed everything.

We stopped spamming people. We stopped worrying about "100 screens a week." Instead, we researched the candidates deeply. We found out what projects they were working on. We sent hyper-personalized messages that spoke to their ego and their technical ambition.

We made fewer calls, but the calls we made worked.

The Process said "Volume." The Intent said "Quality." Once we aligned with the Intent, we started winning.

The Sam's Club Breakthrough (A Life Lesson)

You can apply this to the lowest level of the grind, too.

Back at Sam's Club, on the night shift, the "Process" was simple:

Truck arrives.
Forklift driver unloads pallets.
Stockers put items on shelves.

One night, the forklift driver called out sick.

The process was broken. No driver meant the truck couldn't be unloaded. If the truck wasn't unloaded, the shelves wouldn't be stocked. If the shelves weren't stocked, the store would fail the morning inspection.

My team was standing on the dock, waiting. They were following the process: "Wait for driver."

I looked at the Intent: "The store opens at 0700 fully stocked."

The Intent didn't care about the driver. The Intent demanded the pallets move.

I had a choice. I could call the manager and complain (Process). Or I could solve it (Intent).

I grabbed a certified operator from the tire department. "Teach me the controls. Right now."

I spent twenty minutes learning the basics—how not to tip the lift, how to engage the forks. It wasn't pretty. I wasn't "authorized" in the traditional sense. But I got certified on the spot, jumped in the seat, and unloaded the truck myself.

We finished stocking at 0645. The store opened on time.

The process failed. Commander's Intent won.

Drafting Your Commander's Intent

You need a Commander's Intent for your transition.

If you don't have one, you will get distracted by every shiny object that comes along. You'll apply for jobs you don't want just because they're open. You'll waste time on certifications that don't matter.

A good Intent statement has two parts:

The Purpose: Why are we doing this?

The Endstate: What does victory look like?

The Formula: "My intent is to [PURPOSE] in order to [ENDSTATE]. Success looks like [SPECIFIC OUTCOME]."

Bad Example (Vague):

"I want to get a good job and make more money."

This is weak. It gives you no direction. A "good job" could be anything.

Good Example (Zero Fluff):

"My intent is to secure a GS-13 Program Manager role in the federal government to stabilize my family's finances and continue serving the country. Endstate: I am hired, onboarding, and earning $110k+ with federal benefits by December 31st."

See the difference?

The second one is a filter.

Should you apply for a sales job at a car dealership? No. It violates the Endstate.

Should you spend Saturday fixing your federal resume? Yes. It supports the Intent.

Your Mission: Write Your Intent

Stop reading. Grab a pen.

Write your Commander's Intent for the next 90 days.

The Purpose: Why are you transitioning? Is it for money? Stability? Influence? Location? Be honest.

The Endstate: Be specific. What is the role? The salary? The industry? The timeline?

Write it down. Tape it to your mirror.

From this moment on, every decision you make gets tested against this statement. If an action doesn't move you closer to the Endstate, you don't do it.

Mission Brief

Principle: Commander's Intent defines victory without dictating every step. It's your filter for every decision.

The Proof:

• CIC drill: The console died, but the Intent (track the sub) survived. We won by adapting.
• Amazon: The process said volume. The Intent said quality. We started winning when we aligned with Intent.
• Sam's Club: No driver. Intent said the store opens stocked. I learned to drive a forklift in 20 minutes and solved it.

The Formula: "My intent is to [PURPOSE] in order to [ENDSTATE]. Success looks like [SPECIFIC OUTCOME]."

Your Task: Write your Commander's Intent for your 90-Day Mission. Purpose. Endstate. Specific outcome. Tape it where you'll see it daily.

Drop the fluff. Lock the Intent. Move out.

Lock on. Execute. Win.

Ready to start your 90-Day Mission? Learn more about the 90-Day Mission framework and use the Daily 3-1-0 Generator to execute your Intent daily.