Say Why, Then Step Back: Leading With Intent So Your Team Can Decide

Today is Veterans Day. Before anything else, I want to say thank you to everyone who has served, and to the families who served alongside them.

I'm writing about an idea that comes from military doctrine, and I want to be careful with it. I'm not going to pretend that leading a company is anything like what service members carry. But there is one idea from the U.S. Army's published doctrine that I think every owner should understand, because it goes straight at the question so many of us live with: why does everything still come back to me?

The idea is called commander's intent.

The question behind every question

When someone on your team brings you a decision, they're rarely asking what to do. They're asking what you want.

Should we give this customer the discount? Can we push the delivery a day? Is it OK to bring in a temp for the busy week? Each of those sounds like a request for an answer. Underneath, it's a request for your reasoning. They don't know what matters most to you here, so they come and find out.

And because you know, you answer. Thirty seconds, done. Then it happens again tomorrow, with a slightly different situation, and you answer again.

From the ground, that feels like being responsive. From altitude, it looks like a company that has your instructions but not your intent.

What intent actually means

The Army's newest manual on leading its forces, ADP 6-0, published in July 2026, puts it in one line: "The commander's intent succinctly describes what constitutes success for the operation."

What constitutes success. Not every step to get there.

The doctrine is clear about where the steps belong. Orders written this way, it says, are "not an extended list of every task" a unit might need to perform. The leader describes the result and the purpose, and the people closest to the work decide how to get there.

When I read that, I think about how many of us lead the opposite way. We hand out detailed tasks and keep the purpose in our heads. Then we're frustrated when the plan meets reality and nobody knows what to do next.

Why your team keeps asking

I don't believe most teams lack judgment. I believe most teams lack three things their leader never said out loud.

They don't know why. You know this account matters because it could lead to three more. They think it's just another order. So when something goes sideways, they can't weigh it the way you would.

They don't know what done looks like. "Take care of it" means something very specific in your head. In theirs, it's a guess. When you're not sure you've finished, the safe move is to check with the boss.

They don't know where the line is. Nobody told them which calls are theirs and which ones you want to see. So the careful people bring you everything, and the confident ones occasionally go too far. Either way, you end up back in the middle.

None of that is a people problem. It's a clarity problem. And clarity is the leader's job.

The four things I'd put in writing

Here's how I'd translate intent for a growing company. It fits on half a page, and it's for any piece of work you'd normally hover over: a new customer, a big project, a launch, a new hire's first months.

Why it matters. One or two sentences on what this work is really for. Not the task. The reason.

What has to happen. The two or three results that make it count. If you're listing ten, you're writing a procedure, not intent.

What done looks like. Something they can see for themselves. "The customer signs off on the first month." "The new lead runs the Monday meeting on her own." Not "things go well."

Where the line is. What they decide without you. What they decide after talking to someone. What still comes to you, and why.

Then add one more line: when you'll check in. That's what lets you step back without disappearing.

Write it yourself. Say it in person.

Two lines in the doctrine stopped me. The first: "Commanders develop their intent statement personally."

Not the assistant. Not the operations manager. The leader. Intent is the one piece of direction you can't hand off, because it's the part only your seat can see. Writing it is how you climb above the daily work long enough to say what actually matters.

The second: "Face-to-face delivery ensures shared understanding by allowing immediate clarification of specific points."

That's worth taking seriously. A written intent statement gives your team something to come back to. A conversation gives them a chance to ask, "What if this happens?" before it happens. Do both. Hand it over, talk it through, and invite the hard questions while they're still cheap.

Does pushing decisions down actually work?

It's a fair question. Letting go feels risky, especially when times are hard.

There's research that speaks to exactly that. Research in the American Economic Journal: Applied Economics (2021) drew on management data from firms in ten countries and U.S. manufacturing plants, before and after the Great Recession. Companies that had given local managers more decision-making power came through the hardest-hit sectors in better shape than companies that kept decisions at headquarters. The researchers concluded that decentralization "does appear to be beneficial for the average firm during bad times," while also noting it isn't the right answer everywhere.

These were large manufacturing firms, not companies like most of ours. But the reason they gave is one I recognize: when things are changing fast, the people closest to the problem see things the top can't. Give them room to act on it, and the whole company adjusts sooner.

So when it feels least safe to let go, that may be when it matters most that you already have.

Letting their call stand

This is where most leaders stumble.

You write the intent. Your team takes it seriously. Then someone makes a call inside the lines that isn't the one you would have made. And the temptation is to fix it.

Here's what that fix costs you. One reversal teaches the whole team that "this is yours to decide" didn't really mean it. Next time, they'll ask first. And you're back at the center.

If the decision served the purpose and stayed inside the lines, let it stand. Then ask, "Walk me through how you thought about it." You'll learn how they see the work. They'll learn what you would have weighed. Both of you get better at the next one.

If the decision crossed a line, that's a different conversation, and usually a sign the line wasn't clear enough. Fix the intent, not just the outcome.

An honest self-check

Go through these honestly. Yes, partly or no.

1. For the work you care most about right now, have you told the people leading it why it matters, in your own words?
2. Could each of them describe what finished looks like, without asking you?
3. Do they know which calls are theirs to make?
4. Do they know exactly when you want a phone call?
5. Have you let a reasonable decision stand this month, even though you'd have done it differently?
6. Could someone two levels below you tell you what this year is about for the company?
7. If you stepped away for a week, would your most important projects keep moving?

Every "no" or "partly" is a spot where your team has your instructions but not your intent. The last question is the honest one. If work would wait for you, the purpose is still living in your head.

What changes when intent lands

You'll notice it in small ways first. A question that used to come to you gets answered without you. A manager brings you a decision she's already made, with her reasoning, instead of a question. A problem gets solved while you're in another meeting, and you hear about it after.

That's what altitude looks like in practice. You're still setting the direction. You're just no longer the only one who can steer.

And something shifts for you, too. When the purpose is clear and shared, you stop spending your days answering the same question in fifty forms. You get your thinking time back, the time to look past this quarter and see where you're really going.

Your Monday move

Pick one piece of work that keeps landing back on your desk. Just one.

On half a page, write why it matters, the two or three results that make it count, what done looks like and where the line is. Then sit down with the person leading it, in person if you can, and talk it through. Set a check-in two weeks out.

When that check-in comes, ask what they decided and why, before you share what you would have done.

That's where it starts.

Frequently asked questions

What does commander's intent mean for a leader? It's a few lines that give your team the reason behind the work, the finish line and the limits. The term comes from U.S. Army doctrine. For a company leader, it's the difference between handing someone a task and handing them the reasoning to carry it through surprises.

Isn't writing intent just more work for me? At first, a little. Half a page takes less time than answering the same kind of question every day for a month. It's one of the few tasks that buys back more hours than it costs.

What if my team makes the wrong call? Some calls will go differently than you'd have made them. If a decision served the purpose and stayed inside the lines, let it stand and talk it through. If it crossed a line, clarify the intent so the line is easier to see next time.

Where do I start? With the one piece of work you keep getting pulled back into. Write the intent, hand it over in person and review it together in two weeks.

Bring this conversation to your leaders

I speak to CEOs, founders and leadership teams about building companies that don't run through one person. If your leaders are working on how to let the team decide, invite Nik to speak.

Get The Altitude Report. One clear idea you can act on by Monday. Sign up.

Clarity Changes Altitude. And Altitude Changes Outcomes.™