Why Can't Leaders Agree on Priorities?

Get five senior leaders in a room and ask what the organization's top priority is this quarter, and you'll often get five confident, completely different answers, each one defensible, each one backed by real data, and none of them wrong exactly. That's not a a reflection of your strategy. But it is an identity problem wearing a strategy problem's clothes.

When leaders can't agree on priorities, the instinct is usually to fix it with better planning: a clearer roadmap, a tighter OKR process, a more disciplined quarterly review. Those tools help at the margins. But they can't resolve a deeper issue, which is that priority disagreements are often downstream of an organization that has never actually decided what it is and is not. Without that foundation, every leader is prioritizing based on a private, unstated theory of the company's identity, and those private theories rarely match.

Satya Nadella's early work at Microsoft is the clearest large-scale example of what it looks like to fix this at the root rather than the symptom. When he became CEO, Microsoft's leadership had been fighting, in effect, over which version of the company should win: the one defending Windows and its own hardware ecosystem, or the one that needed to compete in a mobile and cloud-first world increasingly built on platforms Microsoft didn't control.

Nadella didn't resolve that fight by issuing a new five-year plan. He changed what Microsoft was allowed to be. He articulated an identity built around empowering people and organizations to achieve more, rather than an identity built around defending a particular product line, and that single shift in self-definition did something a strategy memo never could: it gave leaders a shared filter for deciding what mattered.

The proof that this was real identity, and not a slogan, is that it killed things. Under the new identity, the phone hardware strategy no longer made sense and was wound down. The instinct to protect Windows at the expense of cloud growth no longer made sense either, and Azure became the priority it needed to be.

Microsoft began making its own tools run on competitors' platforms, a decision that would have been almost unthinkable under the old, more defensive identity. None of that was obvious or comfortable in the moment. It became obvious only once leadership had a real answer to the much more basic question underneath all of it: what is this company actually for.‍ ‍

That's precisely the diagnostic at the heart of Clarify Identity inside the BrandTruth Alignment™ System: identity that doesn't rule anything out isn't real identity, and a leadership team that can't agree on priorities is almost always a leadership team that has never been forced to agree, specifically and uncomfortably, on what the organization is and is not. Once that foundation exists, priority conflicts don't disappear, but they change shape. Instead of competing on whose initiative matters more in the abstract, leaders can test every option against the same shared filter and get to a real answer faster, even when that answer costs someone their pet project.

If your leadership team keeps circling the same prioritization debates without ever landing, the fix probably isn't a better planning process. It's asking, together and out loud, the harder question underneath it: if we had to pick only one thing this organization is fundamentally for, what would survive being said, and what would it rule out?‍ ‍

Helping leadership teams build that shared identity, specific enough to actually resolve priority conflicts instead of just managing them, is core to the work we do at Leadership In Focus.

Reach out to us at contact@leadershipinfocus.ca to talk through what that could look like for your organization.