The GTM Field Manual
Part I · The Operating System · Chapter 4
Part I · The Operating System · Chapter 4

Command & Control

Tell people what you want and why. Then get out of their way.

The GTM Field Manual · Chapter 4 of 24 · ~4 min read

The micromanagement tax

When a leader doesn't state intent clearly, the team can't act on its own. So it asks. So the leader answers. So the leader, in practice, runs every decision. It feels like control. It's actually the most expensive tax in the organization: the whole company runs at the speed of one person's attention.

1
The team can't act on its own
No intent, no latitude. Every move needs a decision from above because the why was never stated.
2
So it asks
Every question is a small stop. In a week, those stops add up to the team's entire capacity for judgment.
3
So you answer
Each answer feels like control. In practice, you're now the bottleneck on every decision in the business.
4
The company runs at your speed
One person's attention becomes the ceiling for the whole operation. That's not leadership, that's a queue.

The military principle: intent, two levels up

Commanders solve this with a clear statement of purpose, given two levels up. Every person understands not just what to do, but why, and what success looks like from above.

A
Order without intent
People get the what but not the why. When the situation shifts, they can't adapt, so every decision bounces back to you.
B
Intent, two levels up
Purpose stated so clearly that anyone can improvise toward the same end. The payoff is written into the doctrine: in the absence of orders, take the initiative.
When someone knows the intent, they don't need the order.

Purpose first, tactics second

Every plan, brief, and project starts with the purpose: one or two sentences on what success is and why it matters. Not the tactics. The intent.

🎯
Purpose first
What success is and why it matters, framed two levels up. One or two sentences at the top of every brief.
🤲
Tactics second
Trust the team to find the how. The person doing the work owns the method, and with it, the judgment.
📏
Outcomes, not methods
Supervise by checkpoint: milestones, adjustments, then get out of the way. Check the result, not the keystrokes.

A brief carries the intent at the top

brief.dashboard
IntentOwn the ICP signal engine · 30 meetings this quarter
End stateCampaigns live · tracked in CRM · weekly report
BoundariesMax $5K · don’t touch pricing
HowDelegated · your method, your call

The procedure: state intent, then delegate

Five steps. The first three take ten minutes. The last two are the discipline.

1
State the intent
What are we trying to accomplish, and why does it matter two levels up? Write it before the tactics exist.
2
Define the end state
What does done look like, in one or two observable terms? If you can't observe it, you can't supervise it.
3
Give the boundaries
Constraints, not instructions. Don't spend more than X. Don't touch the core offer. Freedom inside the fence.
4
Delegate the how
Let the person own the method. The moment you start dictating steps, you've bought the tax back.
5
Supervise by checkpoint
Check at milestones, adjust, then get out of the way. Hovering is not supervision, it's the tax in new clothes.
🗝️
The test
If a task keeps bouncing back for a decision, the intent wasn't stated. Rewrite the intent, not the person.

Where it applies

Intent is how autonomy and scale coexist. Without it, you get to choose: be the bottleneck, or be the ceiling.

📄
Every brief
Campaign, client deliverable, internal project: intent at the top, so anyone can act without asking.
🤝
Delegation
The reason you micromanage is an unstated intent. Write it down, and delegation becomes possible.
🏗️
Systems
A clearly stated intent lets the work run without you. That's the whole point of building a system instead of a job.

Intent two levels up, then delegate the how. Supervise outcomes, not methods.

Koka Sexton
The GTM Field Manual

A written operating system for go-to-market: military doctrine translated for business. One chapter publishes at a time. The frameworks are public. The operating rules behind them are not.

Part I · The Operating System
Chapter 1 · Reconnaissance Pull READ NOW
Chapter 2 · The Estimate READ NOW
Chapter 3 · The Decisive Point READ NOW
Chapter 4 · Command & Control READ NOW
Chapter 5 · Sustain READ NOW
Part II · Tempo & Tactics
Chapters 6-8 · The OODA Loop, The Ambush, Precombat ChecksCOMING SOON
Part III · Read the Battlefield
Chapters 9-14 · Terrain, Center of Gravity, Warfare, Positioning, Counter-Recon, InflectionCOMING SOON
Part IV · Multiply & Adapt
Chapters 15-19 · Force Multipliers, Branches, Main Effort, After Action Review, RehearsalsCOMING SOON
Part V · The Operator
Chapters 20-23 · Simplicity, The Reverse, Negotiation, Defense in DepthCOMING SOON
← Previous: The Decisive Point
Up Next · Chapter 5

Sustain

How the whole system keeps running and compounds instead of decaying.

Read Chapter 5

Get each chapter as it publishes

The collection grows one framework at a time. Start with Chapter 1, or apply the doctrine to your own go-to-market.

Explore the Field Manual Apply this to your GTM
The frameworks are public. The operating system behind them is not.