Why Alignment Is the Most Overused Word in Leadership

There's a phrase that gets said in nearly every leadership meeting I've sat in for the last decade.

"We need to get aligned on this."

It sounds reasonable. Collaborative, even. Nobody disagrees with the framing, how could you? But watch what happens after. The conversation doesn't move forward. It moves sideways. The decision that needed to be made today gets bookended by three more meetings. Someone offers to "drive the alignment." Someone else says they'll "bring it to their team for input." And the calendar starts filling with the kind of meetings that have no decision attached to them, only the promise of one.

This is how organizations slow down without anyone deciding to slow them down.

Last week I wrote about why top talent leaves when their ideas stop mattering. One of the patterns underneath that piece, the one that didn't quite fit there but kept showing up in the drafts, is what people call alignment. It's the word leaders reach for when they want to look collaborative without committing to a decision. And the cost of that habit is far higher than most companies realize.

The thesis of this piece is simple. "Alignment" does three jobs that should be three different words. When leaders use it without distinguishing between them, they substitute the easiest job for the hardest one. The organization pays for the substitution in speed, in decisions and eventually in the people who are tired of waiting for either.

Alignment is doing three jobs and pretending it's one

Listen carefully the next time someone says "we need alignment." They mean one of three things, and almost never name which.

First meaning: informing. Everyone needs to know what's going to happen. This is the cheapest version. It costs an email, maybe a written doc. It does not require anyone's agreement, only their awareness.

Second meaning: agreeing. Everyone needs to genuinely think this is the right call. This is the expensive version. It requires conversation, sometimes argument, often compromise. It's also rare. Most decisions don't actually need everyone's agreement to proceed.

Third meaning: deferring. Everyone needs to stop pushing back and let it happen. This is the version nobody admits to. It looks identical to the first two from the outside, which is exactly why the word is so useful for the person asking. "We need alignment" sounds participatory. "I need you to stop disagreeing with me" doesn't.

The trick the word performs is letting all three sound like the same request. The person who said it can mean any one of them. The person who heard it doesn't know which. So the conversation drifts toward the most expensive interpretation, full agreement, because that's the safest bet for the listener. Everyone slows down to negotiate a level of consensus that the decision didn't actually need.

McKinsey's research on this is direct. Executives spend roughly 40% of their time making decisions, and 61% of that time is reported as ineffective. Most of it happens in meetings. A useful question to ask in the middle of any one of them: which kind of alignment is this? Informing, agreeing or deferring? If nobody can answer cleanly, the meeting is the problem.

The word people reach for when they don't want to decide

The most damaging version of alignment-talk is the one where it gets used as a substitute for deciding.

It works like this. A decision is on the table. It's hard. There's a real tradeoff. The person who needs to make the call doesn't want to make it. Maybe because they're not sure, maybe because they'll catch heat either way, maybe because they have a view but don't want to overrule someone louder. So they say "we need more alignment on this." A second meeting gets scheduled. A doc gets circulated. Three more people get added to the thread.

What's happening is not alignment. It's avoidance.

Bezos named this dynamic in Amazon's 2016 shareholder letter, and the line has stayed with me since the first time I read it: "Without escalation, the default dispute resolution mechanism for this scenario is exhaustion. Whoever has more stamina carries the decision."

That's what alignment-as-stall really produces. Not a better decision. Not consensus. Just the version of the decision that whoever was willing to attend the most meetings was advocating for. The outcome correlates with calendar capacity, not with quality.

Bain has been studying this for over a decade. Their research across nearly 800 companies shows a 95% correlation between decision effectiveness and financial results, across every country, industry and company size they've measured. Companies in the top quintile on decision effectiveness return more than 4x what their peers do to shareholders over five years. The variable that drives it isn't intelligence or strategy. It's the discipline to actually make and execute decisions, fast, without confusing alignment-as-consensus for alignment-as-clarity.

The counter-intuitive piece, the one that most leaders resist when I bring it up: organizations that make decisions quickly are twice as likely to make high-quality decisions. Speed doesn't trade off against quality. The same disciplines that produce speed, like clear ownership, defined process and real empowerment, also produce better outcomes. Slow decisions aren't more careful. They're just more crowded.

Whoever has more stamina carries the decision

The Bezos line is worth sitting with. The default dispute resolution mechanism, when you don't escalate and don't make the call, is exhaustion.

This is the part most leaders haven't internalized. When you say "we need more alignment" and don't say what kind, you're not stalling neutrally. You're handing the decision to the person with the most stamina to keep showing up to the meetings. That's almost never the person with the best judgment. It's the person with the most time, the most political incentive, or the most willingness to outlast the conversation.

Bezos's answer to this is "disagree and commit," and the part of it that gets misread is the disagreement, not the commitment. The phrase isn't "agree on everything before moving." It isn't even "be polite and go along." It's something stronger: you voice your view, you're heard, the call gets made and then you genuinely back the call, even if it wasn't yours.

The example he gives is the one that makes it credible. He greenlit an Amazon Studios original he didn't believe in. He told the team his view. They disagreed. He wrote back: "I disagree and commit and hope it becomes the most watched thing we've ever made." Then he got out of the way.

What that looks like in practice, for a leader who isn't running Amazon: you state your view, the team states theirs, somebody is named as the decision-maker and the decision gets made. Not bookended by three more meetings. Not deferred until someone gets tired. The decision-maker decides, the rest commit and the team moves.

This requires something most organizations underinvest in: clarity about who actually owns the call. Bain's RAPID framework (Recommend, Agree, Perform, Input, Decide) exists precisely because most teams can't answer the question "who decides this?" without 15 minutes of debate. If you can't answer that question in seconds, you're going to live in alignment hell.

Align on the goal, not the path

There is a real version of alignment, and it's worth defending. It's just much narrower than the version that gets invoked in most meetings.

Real alignment is about the goal, the constraints and the deadline. Where are we going. What can't we break. When does this need to ship. Everyone on the team needs to be aligned on those things. If they're not, the team is genuinely misaligned, in the Bezos sense, and no amount of execution will fix it. You're rowing in different directions.

What doesn't require alignment is the path. Two engineers can disagree on the architecture and still ship a great product if they agree on what it needs to do. Two PMs can disagree on the sequencing of features and still deliver a great quarter if they agree on the outcome. A finance lead and a product lead can disagree on the tradeoff between margin and growth and still land somewhere reasonable if they agree on the company's stage and constraints.

The version of alignment that costs companies the most is the version that tries to align on the path. It's the meeting where four senior leaders argue about the spec for forty minutes when the only thing they actually needed to agree on was the constraint the spec had to satisfy. Each one of them, given the constraint, would have come up with a workable solution. The argument exists because the constraint was never named.

The fix is unglamorous. Before any meeting that purports to need alignment, ask one question: are we aligning on the goal, or on the path? If it's the goal, the meeting is worth having and probably short. If it's the path, cancel the meeting, name a single owner and let them propose. Disagreement on a proposal, once it exists, is faster and cheaper to resolve than disagreement in the abstract.

The meeting that never ends

Go back to the phrase that started this piece. "We need to get aligned on this."

In the best case, said with discipline, it means: let me make sure everyone has the context they need to commit to a call that's about to be made. That's a useful sentence. It moves things forward.

In the bad case, said reflexively, it means: I would like to delay this decision for another two weeks while we negotiate everyone's comfort. It usually wins, because nobody can argue with the word. Who's against alignment? But the cost shows up later. In the project that shipped six weeks late, in the team that stopped bringing real proposals because the proposals dissolved into alignment cycles, in the senior leader who quietly logged that this company can't decide without three layers of agreement and started looking around.

Whoever has more stamina carries the decision. That's the trap. The companies that escape it don't escape by talking more carefully. They escape by deciding who owns the call, making it and committing to it, including the people who disagreed.

Top talent doesn't measure your meeting cadence. They measure how often the meetings actually produce a decision. When the answer trends toward never, they leave. And the word everyone used to describe the cause was alignment.

If you're seeing this in your own organization and want to talk it through, get in touch.

---

This is the second in a weekly series on what I see in the market and hear from operators across the companies I've worked with. Next week: why most product roadmaps are theater, and the operating doc that actually drives the work.