When everything is a priority
A new service gets added. An incredible opportunity appears. A project that was important months ago is still hanging about. Someone has a great idea, or two, or three. A customer needs something now! Something else isn’t working as well as it should.
Individually, each of these things makes sense. The problem is that businesses (and people) are usually much better at adding priorities than removing them.
Eventually, every single thing is important. And when everything is important, nothing gets the attention it truly needs.
The difficult part of prioritisation isn’t usually deciding what matters. It’s deciding what matters most right now - and what you’re prepared not to do as a result.
Busyness can hide a lack of direction
Take the list above. This doesn’t necessarily look like a business that’s stuck.
Quite the opposite. The team could be busy with projects moving, meetings happening, plans, backlogs, roadmaps, and plenty of things to do. But that activity and actual, directed progress aren’t the same thing.
Work can be happening everywhere while the things that matter most move surprisingly slowly if at all. Projects advance in bursts, then stall. Decisions get made and reopened. Something urgent appears and pushes everything else back. A huge opportunity gets all hands on deck.
The response is often to add more structure: another planning session, a more detailed roadmap, a new initiative, another conversation about priorities, a tool, app, model...
Sometimes that helps, but if the underlying problem is that just too many things have been allowed to remain important, organising them more carefully simply can not resolve it.
How priorities accumulate
Mess isn’t always a sign that something has gone wrong. Often it’s a consequence of growth and change.
New services sit alongside old ones. Audiences are added without deciding whether the existing or older ones still matter - or matter as much. Old, legacy projects survive long after the circumstances that created them have changed. Temporary solutions become permanent.
None of those decisions needs to be particularly bad. The problem is the accumulation, and eventually that accumulation starts to show.
Warning signs
- Projects keep starting but struggle to finish. Something newer or more urgent keeps displacing them.
- The same decisions keep coming back. They get discussed, temporarily settled, then reopened.
- Everything has a reasonable justification. There are few obviously bad ideas to remove.
- Urgent work routinely displaces important work. The longer-term things matter, but never quite enough to win today.
- People are busy, but progress feels strangely thin. Lots is happening without much changing.
- Priorities change without anything being deprioritised. New work gets added; old work just becomes slower.
- Nobody can confidently say what can wait. Ask what matters and you’ll get a list. Ask what doesn’t matter yet, and the answer is much harder.
Together, these are a useful indication that the problem is less about capacity and more about focus.
Prioritisation requires subtraction
It’s relatively easy to identify important things.
Improving the website is important. Developing a new service is important. Looking after existing customers is important. Building the pipeline is important. Fixing the product is important... and so on.
A list like that might be completely accurate – it still isn’t a list of priorities.
Prioritisation requires a second decision: what gets less attention—or stops altogether—because something else gets more? That’s the uncomfortable bit.
Choosing three priorities without changing anything else just gives three things a new label. If every existing project continues, every audience remains equally important, and every opportunity still deserves attention, nothing has really been prioritised.
A useful test is:
If these are our priorities, what are we explicitly choosing not to prioritise?
If there isn’t an answer, they aren’t priorities yet. They are just yet more important things.
A roadmap can organise confusion without resolving it
Roadmaps, backlogs, and plans are undeniably useful. They make the work visible and give it structure. But they can also make an unresolved set of priorities look reassuringly organised.
A beautifully ordered list of thirty initiatives is still thirty initiatives.
You can keep moving work between quarters, pushing lower-priority projects further into the future and inserting new ones at the top. Eventually the roadmap becomes less a statement of intent and more a record of everything the business would like to do if capacity ever appeared.
Sometimes the useful decision is not where something belongs on the roadmap. It’s whether it belongs there at all.
The test is in asking:
- What matters most now – and why?
- What can wait?
- What happens if we don’t do this?
- What happens if we only do this?
- What are we prepared not to do?
Clarity creates capacity
Every unresolved priority consumes attention. It creates meetings, decisions, updates, dependencies, and context switching. Even projects that aren’t actively moving require people to keep them in mind.
Removing something from consideration can create capacity without anybody working faster or harder.
The team has fewer competing decisions to make. Projects have a better chance of reaching completion. New opportunities can be judged against a clear focus rather than simply added to the pile.
The aim here isn’t to create a perfectly ordered business where nothing unexpected happens. It’s to make the current direction clear enough that the unexpected can be dealt with without everything else immediately losing its shape.
Good strategic clarity can be surprisingly simple:
- This matters now.
- This can wait.
- This seemed important six months ago, but it doesn’t anymore.
- This is a good idea, but not one we’re going to pursue.
A priority isn’t really a priority until you’ve decided what it takes priority over.