The Broken Compass

The offsite was great. Everyone left feeling aligned. That was three months ago. Since then, the same agreed strategy has been interpreted six different ways — and nobody has acknowledged the contradiction because acknowledging it would require having the conversation that nobody wants to have.

The Broken Compass names a specific failure: leadership agrees to language vague enough for everyone to nod along with, then discovers months later the agreement never actually resolved anything. Six teams interpret the same "locked-in" strategy six different ways. Priorities that were supposedly settled get quietly reprioritized. Two VPs present contradicting plans in the same meeting, and nobody names the contradiction because naming it would require a conversation nobody wants to have.

The strategy deck still exists, in a folder somewhere. People reference it occasionally and nod like they're aligned. They're not reading the same book.


The Illusion of Agreement

Here's how it usually works.

The strategy meeting happens. Everyone has opinions. Some of those opinions conflict. But the meeting has a time limit, and nobody wants to leave without a conclusion, so the conflicts get papered over with language vague enough that everyone can agree to it.

"We're going to focus on growth while maintaining profitability." (What does that mean when growth and profitability conflict, which they will?)

"We'll prioritize the enterprise segment while not abandoning SMB." (So we're prioritizing everything? Great.)

"We're going to be more aggressive while staying true to our culture." (What happens when aggression and culture collide? Nobody knows, because nobody asked.)

Everyone leaves the room thinking they agreed. They didn't. They agreed to words that sounded like agreement. The actual decisions that would test the agreement never got made.

Those decisions happen later, in smaller rooms, without the full team present. One leader makes a choice based on their interpretation. Another makes a different choice based on theirs. Neither is wrong given their premises. The premises just never got reconciled.


What It Looks Like From Below

If you're two levels down from the leadership team, The Broken Compass feels like whiplash.

Last month, the priority was Product A. This month, you're hearing rumors that Product B is actually the focus now. Your skip-level said one thing; your direct manager said something different; the all-hands said something vague enough to be compatible with both. You're trying to figure out what to actually work on, and the answer seems to depend on which leader's Slack messages you read most recently.

So you hedge. You make progress on both things, committing fully to neither. You learn to read the political winds before allocating your time. You get good at presenting your work in whatever frame seems most favored this week.

This is exhausting. It's also rational. You're responding logically to an illogical situation. The problem isn't that you're not executing. The problem is that no one has told you clearly what to execute on. So you're doing your best impression of someone who knows what they're doing while quietly hoping someone will eventually clarify things.

(They won't. Not unless something changes at the leadership level.)


Why the Conversation Doesn't Happen

The leaders know. That's the thing. They're not unaware that they're pulling in different directions.

They just haven't been willing to have the conversation that would resolve it. And there are reasons for that.

Sometimes the conversation is too hard. The real disagreement is about something fundamental: the kind of company this should be, the role of specific people in the future, whether a particular leader belongs on the team anymore. Easier to talk about "strategy" than to have that conversation.

Sometimes the conversation has already happened and failed. The offsite was supposed to be the place where this got hashed out. It didn't work. Now everyone's a little burned out on the whole alignment thing. Let's just focus on execution and hope the strategy stuff sorts itself out.

Sometimes the ambiguity is serving someone. If the direction stays unclear, no one has to commit. No one has to be wrong. Everyone can continue to advocate for their preferred path without ever having to see it tested. The fog is a feature, not a bug.

Whatever the reason, the conversation keeps not happening. And every week it doesn't happen, the cost gets higher.


The Cost of Executing in Different Directions

Let's talk about what this is actually doing to your organization.

Execution gap. You have talented people working hard on things that may or may not matter. The roadmap has twelve initiatives, and six of them are pointed in one direction while the other six are pointed in another. Both sets make sense internally. Together, they're incoherent. The organization is generating effort without generating proportional progress.

Initiative mortality. Projects launch with energy and stall when they need leadership support. One VP is enthusiastic; another is skeptical. The initiative becomes a proxy for the disagreement that nobody resolved at the strategy level. It dies not because it failed but because it ran into an alignment problem that existed before it started.

Talent frustration. Your best people want to do great work. Great work requires clarity. They're not getting clarity, so they're either manufacturing it for themselves (and hoping they guessed right), or they're spending half their energy navigating ambiguity instead of executing. Some of them will get tired of it. They'll leave for somewhere that knows where it's going.

Decision latency. Every decision that requires alignment across leadership takes forever. The decisions that should be easy become hard because every choice surfaces the underlying disagreement. The calendar fills with "alignment" meetings. The actual alignment never arrives.


What Actually Resolves It

The Broken Compass doesn't resolve through another strategy process. You've done the strategy process. You have a deck. The problem isn't the deck.

It resolves when the leadership team has the conversation they've been avoiding.

Not the meta-conversation about how they should communicate better. The actual conversation. The one where someone says "I don't think we agree about where we're going, and I think we need to figure that out before we do anything else." The one where the real disagreement, the one underneath the proxy disagreements, finally gets surfaced and worked through.

That conversation is uncomfortable. It might involve acknowledging that someone's vision isn't going to win. It might involve revisiting decisions that felt settled. It might involve personal dynamics that have been managed around instead of addressed.

But it's the only thing that works. You cannot operationalize your way out of a leadership team that's pointed in different directions. The direction has to be set first. Everything else follows from that.


The Question We Ask

When an organization tells us they have a strategy problem or an execution problem, we start with a question.

Has the divergence been named directly, in a room with all the relevant people, or has it only been discussed in subsets and side conversations?

Usually the answer is the latter. Everyone knows there's a disagreement. It's been discussed one-on-one. It's been acknowledged in smaller groups. But the full cast has never been in the same room for the actual conversation. The one where you can't retreat to safe territory because everyone's watching.

That's where it has to happen. Not in the hallway. Not in the DM. In the room, with everyone present, with enough time to actually work through it.

We've facilitated that conversation before. We know what it takes to set it up, hold it together, and help the team land on something real. Something that sticks.

The leadership team already knows which conversation they've been avoiding. Stopping the management-around means finally having it.

— Principal Resolution