Priority, not priorities — the discipline of choosing

Having many priorities is the same as having none. When a leadership team lists eight strategic priorities, it has not made any choices — it has listed everything it cares about and called it a strategy. The organisation receives this list and, reasonably, tries to do all eight things. Resources are spread thin. Progress on each priority is slow. The team reports quarterly on all eight, notes that some are ahead and some behind, and moves on. Nothing changes.

Choosing a priority — singular — is one of the hardest things a leadership team can do, because it requires explicitly deciding what will not receive full attention. Most teams resist this. The language of priorities is politically safe; the language of a single priority forces a conversation about whose agenda is most important, which teams will have to defer, and what the organisation will accept being slower at for the next twelve months.

The discipline of choosing is not recklessness. It is the recognition that concentrated effort produces results that distributed effort cannot. A team that fully resources one priority, removes the blockers, and measures progress relentlessly will outperform a team that partially resources five priorities and optimistically updates the dashboard.

Saying no in writing, on purpose, is the accountability mechanism that makes this real. When the decision not to pursue something is documented — including the rationale and the conditions under which it would be revisited — it becomes much harder to quietly re-add it to the list three months later. It also creates a record that the team made a deliberate choice, which is more useful than a silence that looks like oversight.

This session covers the frame for making the choice, the conversation structure for getting a room of senior leaders to agree on a single priority, and the documentation practice that makes the decision stick.