The ability to identify what matters most and sequence work accordingly. It involves weighing value, urgency, and impact to make deliberate trade offs, focus attention, and allocate time and resources to the highest return activities. Effective prioritisation turns ambition into action by ensuring energy is spent on what moves the needle, not just what demands attention.
The prioritisation visual above summarises five practical behaviours that help leaders direct limited time, attention and resources towards the work that matters most: anchoring priorities to important outcomes, evaluating competing demands against clear criteria, making explicit trade-offs and saying no when necessary, limiting work in progress to protect focus, and regularly reviewing priorities to maintain alignment across the team. Together, these behaviours help leaders distinguish genuine value from urgency, make difficult choices between worthwhile activities and ensure that both individual and collective effort is concentrated on achieving the outcomes that matter most.
“You can do anything, but not everything.” David Allen
Why prioritisation matters
Every leader has more valuable things to do than time or energy to do them. Prioritisation is the discipline of choosing which of those valuable things actually get done, and openly accepting that everything else will not happen right now. Leaders who skip this discipline do not end up doing nothing, they end up making shallow progress on many things at once, which from the outside can look exactly like productivity while actually delivering very little that matters.
Whatever a leader visibly spends time on, and whatever a leader rewards, quietly becomes the real priority list for everyone around them, whether that leader intends it or not. A leader who cannot clearly rank their own priorities passes that confusion straight down to their team, so unclear prioritisation at the top rarely stays a personal problem. It shows up a few weeks later as a team quietly working on different things, each person confident they are doing the right work.
Every day also brings dozens of small ranking decisions, this request before that one, this email now or after lunch, and each one draws on the same limited mental resource. A leader who already has a clear, ranked view of what matters most can make most of these small decisions almost automatically, preserving their best judgement for the handful of choices that genuinely deserve it. A leader without that clarity spends the same limited resource sorting out what matters most all over again, many times a day, and has less of it left for the decisions that actually count.
“If everything is important, then nothing is.” Patrick Lencioni
What good and bad prioritisation looks like
| Bad | Good |
|---|---|
| A leader keeps a single flat to do list where a client emergency, a birthday reminder, and a strategic planning task all sit at the same visual weight, so the day gets decided by whichever item was clicked most recently. | A leader sorts the list into three tiers before the day starts, must happen today, matters this week, can wait a month, so the first hour goes to the top tier regardless of what pops up. |
| An executive says yes to every meeting invite that lands in the calendar, arriving at each one having only skimmed the agenda five minutes beforehand. | An executive declines two of five meeting invites this week, naming the specific priority those hours are protecting, and arrives prepared at the three that were kept. |
| A product lead has fourteen workstreams in progress at once, each one nudged forward a little most days, none of them actually finished. | A product lead caps active workstreams at three, deliberately leaving the other eleven untouched until one of the three ships. |
| A manager keeps funding a two year old initiative because of how much has already been invested in it, even though a newer opportunity now offers a clearly better return. | A manager kills the two year old initiative mid quarter once the newer opportunity’s return becomes obvious, treating the earlier investment as already spent regardless of what happens next. |
| A team lead reviews the quarter by counting how many tickets got closed, and calls it a good quarter because the number is high. | A team lead reviews the quarter by asking which three closed tickets actually moved a customer metric, and treats the rest as activity rather than progress. |
| A director announces the annual priorities in January and never revisits them, so by September the team is quietly working from a different, unspoken list. | A director revisits the priority list at the start of every month with the team, retiring items that no longer matter and naming what has replaced them. |
| A senior leader schedules back to back meetings from 8am to 6pm every day, then wonders why the strategic plan promised to the board is still a blank document three weeks later. | A senior leader blocks two 90 minute windows each week that show up on the calendar as unmovable, and writes the strategic plan in exactly those windows. |
| A leader sets clear personal top three priorities, but never asks direct reports what they think the team’s top three are, so each report quietly works from their own private list. | A leader sets personal top three priorities and then spends 20 minutes with direct reports confirming everyone can name the same three, adjusting the wording until they agree. |
“Remember that if you don’t prioritise your life, someone else will.” Greg McKeown
Barriers to prioritisation
Lack of strategic clarity: When there is no shared, well understood definition of what the organisation or team is actually trying to achieve, every request looks equally plausible, so priorities end up being set by whoever asked most recently or most loudly rather than by what actually advances the goal.
No framework for weighing value: Without agreed criteria such as impact, effort, or urgency, a leader is left comparing a client request against a strategic project using nothing but gut feel, so the choice quietly defaults to whichever option feels most urgent in the moment rather than whichever option matters most.
Fear of saying no: Declining a request risks disappointing a colleague or being seen as unhelpful, so a leader accepts more commitments than they can actually deliver, trading a moment of short term discomfort for months of being spread too thin.
Reactive, fragmented days: When the working culture rewards visible responsiveness over quiet strategic progress, a leader’s calendar fills with interruptions and short notice requests, leaving no protected block long enough to think, plan, or do the work that actually matters most.
Poor time estimation: A leader routinely underestimates how long meaningful work actually takes, so the calendar looks like there is room for five priorities when there is realistically capacity for two, and everything after the second quietly slips.
Emotional attachment and sunk cost bias: A leader keeps funding or defending a project because of how much time, money, or personal credibility has already gone into it, even once the evidence shows a different option would now deliver more.
Misaligned incentives: When bonuses, recognition, or promotion are tied to activity, output volume, or visibility rather than to outcomes, a leader is quietly rewarded for staying busy on the wrong things, so rational prioritisation actually works against their own short term interests.
Decision fatigue: Making dozens of small ranking decisions every day, this email now or after lunch, this meeting or that one, steadily drains the same mental resource, so by the afternoon a leader increasingly defaults to whatever is easiest or loudest rather than what is genuinely most important.
Confusing effort with priority: A task that consumed the most hours or felt the hardest earns a leader’s attention and pride, so it gets treated as important because of how much it cost to complete, not because of what it actually achieved.
Confusing prioritising your own work with prioritising the team’s: A leader can be highly disciplined about sequencing their own personal task list while never actually aligning the team on a shared set of priorities, so each person quietly works from their own private ranking of what matters most.
“Deciding what not to do is as important as deciding what to do.” Steve Jobs
Enablers of prioritisation
Define what’s in and what’s out: Reconnect every prioritisation decision to two or three headline goals, and then go one step further by naming out loud which categories of work are explicitly not being pursued this quarter, so the boundary is as clear as the focus.
Use consistent decision criteria and a named method: Agree on two or three criteria such as strategic alignment, effort required, and urgency, and commit to a specific method for weighing them, a simple 2×2 grid works as well as anything more elaborate, or a named approach such as the Eisenhower Matrix, MoSCoW, or RICE, so that every new request gets compared against the same yardstick rather than judged fresh each time.
Set time horizons and work in layers: Organise the workload into today, this week, and this quarter, and treat each layer differently, so a task that matters this quarter is not squeezed out by something merely urgent today.
Make trade offs explicit: When accepting a new commitment, say out loud what it is displacing, if this moves up, that moves down or off, so the team can see and challenge the trade off rather than watching the leader’s list quietly grow.
Limit work in progress: Cap the number of active initiatives at a small, fixed number, and treat starting anything new as requiring something else to finish or stop first, so effort concentrates instead of thinning across everything at once.
Protect deep work time: Block recurring, uninterrupted windows on the calendar for the work that only progresses with sustained attention, and defend that time with the same seriousness given to an external meeting.
Say no with purpose: Build a small set of clear, respectful ways to decline a request that name the reason, this doesn’t serve our top priority right now, rather than a vague apology, so saying no becomes a routine skill rather than a stressful exception.
Review and reorder often: Revisit the priority list on a fixed cadence, at least monthly, asking what has changed, what still matters, and what can now be dropped, treating the list as a living document rather than a decision made once and filed away.
Review outcomes, not just activity: When assessing progress, ask what actually changed for the customer, the team, or the numbers, rather than how many tasks were completed, so effort gets redirected away from work that merely felt productive.
Involve your team in the ranking, not just your own list: Share your own top priorities with direct reports and ask them to name what they believe the team’s top priorities are, then work through any mismatch until everyone can describe the same short list in their own words.
“The key is not to prioritise what’s on your schedule, but to schedule your priorities.” Stephen Covey
Reflection questions on prioritisation
1. Can I state the two or three goals my current priorities are meant to serve, and could I name what I am explicitly choosing not to pursue right now?
2. What criteria am I actually using to compare competing requests, and would a colleague looking at my choices be able to guess what they are?
3. Which of my current commitments belong to today, which belong to this week, and which are quietly borrowing time from something that actually matters more this quarter?
4. The last time I said yes to something new, what did I quietly let slip as a result, and did anyone else notice the trade off happening?
5. How many initiatives do I currently consider active, and honestly, how many of them are actually moving?
6. When did I last protect a block of time for deep, uninterrupted work, and what took its place instead?
7. What is my current go to way of declining a request, and does it name a reason or just soften the disappointment?
8. When did I last sit down and deliberately ask whether my priorities from a month ago still hold, rather than assuming they do?
9. If I looked back at what I completed this month, how much of it actually changed an outcome, and how much of it was simply activity?
10. If I asked each of my direct reports to name the team’s top three priorities right now, how many different answers would I get?
“The difference between successful people and really successful people is that really successful people say no to almost everything.” Warren Buffett
Micro practices for prioritisation
1. Write your non priorities down, not just your priorities: A short list of things you will not do this quarter is far easier to hold yourself to than a vague intention to stay focused, because it gives you something specific to point to the next time a tempting distraction shows up.
2. Name the trade off out loud before you say yes: Before accepting a new request, finish the sentence, if I take this on, the thing that slips is. An unspoken trade off lets a calendar fill up invisibly, while a named one forces a real decision each time.
3. Cap your active list at three and write the fourth one down anyway: When a fourth priority appears, add it to a visible waiting list rather than your active one. Seeing it written down satisfies the urge to act on it immediately, while keeping it off your active list protects the three that actually matter.
4. Put deep work blocks on the calendar before the week fills up: Schedule two 90 minute blocks for your most important work first thing on Monday, before any meeting requests arrive. A block added after the week is already full always loses to whatever got there first.
5. Replace a vague no with a one line reason: Instead of saying you cannot take something on right now, say it doesn’t serve a specific named priority, so you are going to pass. A reasoned no is easier for the other person to accept and easier for you to repeat consistently, while a vague no invites a second attempt.
6. Set a recurring 20 minute date with your own priority list: Put a standing monthly slot on your calendar solely to ask what has changed and what can be dropped. A review that depends on you remembering to do it will not survive a busy month, one that is already scheduled will.
7. Ask your team to write down their own top three before you share yours: Ask each direct report to independently name what they believe the team’s top three priorities are, before you reveal your own list. Comparing their answers to yours, and to each other, surfaces silent misalignment that simply asking whether everyone agrees with the priorities never will.
“The essence of strategy is choosing what not to do.” Michael E. Porter
Explore related leadership resources
To further develop this capability, examine how it intersects with other core leadership dimensions across the libraries:
Leadership library:
- Planning: Translate priorities into clear, structured action plans, ensuring that focus areas are supported by deliberate sequencing and execution.
- Business Acumen: Strengthen your judgement by understanding commercial drivers, allowing you to prioritise work that delivers the greatest organisational value.
- Vision and Purpose (Managing): Anchor your priorities to the broader direction of the organisation, ensuring that effort is focused on what truly moves the needle.
Supporting libraries
- Impulse control (EQ-i): Resist the pull of urgency and distraction, enabling disciplined focus on what matters most rather than what demands immediate attention.
- Strategic orientation (Traits): Take a longer term view when setting priorities, balancing immediate needs with future impact and direction.
- Realistic thinking (Traits): Ground your decisions in what is achievable, ensuring priorities are credible, sustainable, and aligned with available resources.
Continue exploring: Return to the Leadership Library to view the full directory of competencies and resources.