Alignment vs Agreement, Part 2: How Founders Actually Coach for Alignment

The leader's job changes once you understand alignment. Here's what leading through alignment actually looks like.

A couple of weeks ago, we wrote about the difference between agreement and alignment. Quick recap. Agreement is shared commitment to a plan. Alignment is shared commitment to an outcome, as well as a shared way of thinking about that outcome. Teams that only have agreement need the founder in the room to make every real decision. Teams that have alignment can make those decisions on their own.

That post explained the concept. This one is about what a founder actually does with that knowledge on a Tuesday afternoon.

Because here’s the thing—once you understand alignment, your job changes. You’re no longer the person who tells people what to do. You’re the person who teaches them how to think about what to do. And that’s a much harder (and more important) job than most founders realize.

Stop improving the plan. Start improving the thinking.

When a team member brings them a plan, most founders do one of two things. They approve it, or they fix it. “Yeah, looks good, ship it.” Or “No, you should do it this way instead.”

Both responses are mistakes. Just approving sets you up as the rubber stamp. Fixing teaches them to come back to you for the answer next time, because you have it and they don’t. Either way, you become the bottleneck.

There’s a third option that takes more patience. Instead of evaluating the plan, ask about the thinking that produced it.

“Why did you pick that approach?” “What outcome are you optimizing for?” “What did you consider and rule out?” “What would have to be true for this to be the wrong call?”

The point is not to interrogate them. The point is to surface the reasoning behind the plan so you can coach the reasoning, not the output. A team member who walks out of your office with a corrected plan has a better plan. A team member who walks out with a corrected way of thinking has a better next ten plans.

Build a version of yourself in every team member’s head

The goal of all this on-the-job coaching is not just to make better decisions on the current project. It’s to install your decision-making framework in your team members so they can predict what you’d say.

When alignment is working, you can leave the room, and the team makes the same call you would have made. Not because they got the plan right, but because they understand the underlying thinking well enough to apply it to a situation you’ve never discussed.

The way you build that mental version of yourself in their heads is by externalizing your thinking. Constantly. Repeatedly. Out loud.

Don’t just tell people what to do. Tell them why. Don’t just approve a decision. Walk through the factors you weighed and how you weighted them. Don’t just say “we don’t do that.” Explain the principle that rules it out.

This feels inefficient because … it is … in the short run. You could have just made the call in thirty seconds. Instead, you spent ten minutes explaining how you got to the call. But the next time a similar situation comes up, your team member is better equipped to make the call without you. The time investment compounds.

Ask the team to propose, not to receive dictation

The other thing that changes once you’re coaching for alignment is how decisions get made. The default founder mode is often dictation. You decide what should happen, you tell the team, the team executes. That works fine when you’re five people. It breaks with 15. It’s a disaster at 50.

The mode that scales is proposal. The team member proposes what they think should happen and why. You react, ask questions, and either align with their thinking or help them see what they missed.

This is the hardest mental shift for founders, especially technical founders, because they spent years being the person who knew the answer. Asking “What do you think we should do?” feels like punting, almost like abdicating responsibility. It isn’t. It’s the move that surfaces whether you have alignment in the first place.

When their proposal is a bit off or even wildly off, that’s helpful information. It tells you the alignment isn’t there yet, and now you can do something about it. If you’d just dictated the plan, you’d never have learned that, and the misalignment would have shown up later, in worse form, with bigger consequences.

The leader’s job, revised

Founders usually think their job is to have the answers. The most senior leaders we work with would describe the job differently. Their job is to make sure the team has the thinking that produces the answers, so they don’t need to be in every room.

That shift, from answers to thinking, is the entire game.

Improve the thinking, and the plans take care of themselves.