TL;DR: Most advice on how to prioritize work stops at the urgent-vs-important sort. That’s a useful first pass, but it almost always leaves you with more “important” work than the week or quarter can hold. The next layer is the one that creates real focus: subtracting based on what your team has already pre-decided is the priority right now, through your strategic plan and current OKRs. Below is the framework I use, plus the polite scripts for pushing back on work that doesn’t pass either filter.
It’s 8:47am Monday. The list is open. You’re scanning the line items and doing the silent math: meeting prep, two reviews, the Thursday deck, the comment thread you said you’d close out, the new ask that landed Friday at 5pm. The question forming in your head has nothing to do with the list itself. It’s the only question you have energy for: how am I going to get all of this done this week?
I’ve been there. More than once. Sitting in front of a list I didn’t fully build, in a week I didn’t fully plan, asking the question that the list itself can’t answer.
What does it actually mean to prioritize work effectively? Learning how to prioritize work is less about ranking the list and more about subtracting from it. A first pass like the Eisenhower matrix sorts the list into urgent versus important quadrants. Useful. The problem most leaders run into is that even after the sort, the “important” pile is still bigger than the week can hold. The layer that finishes the job is the one that asks: which of these important items did the team already commit to as priorities this quarter, through the strategic plan and current OKRs? That’s the cut that creates focus.
That reframe is harder than it sounds, because most of us have been trained for years to treat the to-do list as the brief.
How to Prioritize Work When “Busy” Feels Like Valuable
The wiring runs deep. A full calendar, a roaring inbox, and a Slack window that never sits still all feel like contribution. They feel like proof you’re in demand, in the loop, doing your part. Most of us have heard the line that busy doesn’t equal productive. It’s a comforting reminder. It also rarely changes our Tuesday.
That gap between the intellectual rebuttal and the actual behavior is the part worth naming. It’s why the urgent keeps crowding out the important, quarter after quarter. The reflex to look busy is faster than the discipline to ask whether the work is worth doing.
In fact, learning how to prioritize work by subtracting can even feel lazy. And if you’re anything like me, being perceived as “lazy” at work, or not earning my keep, is the absolute last thing I want.
Greg McKeown, in Essentialism, names this directly: the way of the essentialist is “the disciplined pursuit of less but better.” Cal Newport’s case for deep work lands in the same place from a different angle: shallow, busy work crowds out the focused effort that actually creates value. Both arguments are well-rehearsed by now. What’s harder is acting on them when your boss has just dropped one more thing onto your plate.
What’s the Real Cost of Treating “Busy” as a Strategy?
When everyone is busy, nobody is responsible for outcomes. Teams ship a quarter’s worth of activity and end the cycle wondering why the strategic priorities barely moved. The Microsoft Work Trend Index keeps surfacing the same pattern in workplace data: knowledge workers are spending more time in meetings, more time in chat, more time on document work, and reporting less capacity for the focused effort their roles actually require.
Jim Collins, in his research on what separates good companies from great ones, argues that great executives keep a “stop-doing list” with at least as much rigor as their to-do list. The stop-doing list is the artefact of subtraction. It’s the version of prioritization that has teeth, because every item on it is something you’ve actively decided not to fund with your attention.
Most of us don’t have a stop-doing list. We have a to-do list with a quietly growing tail.
How to Prioritize Work: A Five-Step Framework
When I’m staring at a list that won’t fit into the week, this is the order I work through. It takes about fifteen minutes. It’s not glamorous. It’s the most reliable way I know how to prioritize work without losing the things that actually matter.
- List every commitment, not just the ones in your task tool. Pull from your inbox, your calendar invites, the Slack threads you’ve promised to close out, and the verbal “yes” you gave in Thursday’s meeting. Until the full set is on paper, you’re prioritizing a partial picture. This step alone is often the relief, because it turns the vague dread into a finite list.
- Run the urgent-vs-important sort. This is where the Eisenhower matrix earns its place. For each item, ask whether it’s urgent, important, both, or neither. The “neither” items are easy to drop. The “urgent but not important” items belong on someone else’s plate or in an automation. You’re not finished after this step, but it cuts the list cleanly.
- Apply the OKR layer to the “important” pile. This is where most prioritization frameworks stop and most leaders stay stuck. After the sort, you almost always have more “important” work than fits in a week. The next cut is asking which of those important items connect to a strategic priority or current OKR your team has already committed to. The strategic plan and OKR cycle did this work for you in advance. Treat them as the predetermined areas of focus they’re meant to be. Items that pass this filter earn the week. Items that fail it can be valid work, but they don’t earn priority right now.
- Identify the one item that, if it shipped well this week, would matter most. Not three. One. The single item whose completion would change what your team or your leadership would feel by Friday. Protect time for it before you protect time for anything else. Cal Newport’s deep-work argument lives in this step.
- Write the items you’re not doing this week somewhere visible. This is the stop-doing piece. The list of “not now” items has to live in writing, not in your head. When the person who delegated it asks for an update, you have a clear answer: “It’s on my list. It’s not this week. Here’s what is, and here’s why.”
If you do this every Monday, the question stops being how do I get all of this done? It becomes which of these am I willing to commit to delivering well this week? That’s a question you can actually answer.
The OKR Layer: How to Prioritize Work After Urgent vs Important
Step 3 is the one that does the heavy lifting, so it’s worth slowing down on. This is the layer most prioritization advice skips, and it’s the layer the strategic planning cycle is supposed to produce. It’s this: how to prioritize work so that we lead with impact.
The principle: subtraction through predetermined areas of prioritized focus and alignment. When the team set its strategic plan and committed to a small set of OKRs for the quarter, the team was making a promise about what matters most right now. That promise is the filter. Use it.
Run each “important” item through these five anchors before it earns the week:
| Anchor | What you’re checking | If the answer is no |
|---|---|---|
| Mission and vision | Does this work serve the company’s stated reason for existing? | Be cautious. Items that ignore mission usually become noise. |
| Values | Does this align with how the team has agreed to operate? | Push back, especially if the request asks you to compromise on stated team values. |
| Strategic pillars | Does this connect to one of the named long-horizon priorities? | Defer. Items outside the strategic pillars rarely deserve in-the-week attention. |
| Current quarter OKRs | Does this contribute to a key result the team is accountable for? | Park it. Quarterly focus is the contract. Adding to it dilutes it. |
| Cross-team support | Does this materially help another team hit their OKR? | Worth doing if the answer is yes and it doesn’t crowd out your own commitments. |
If a request fails all five anchors, you have a legitimate, well-reasoned case for declining or deferring it. That isn’t being difficult. That’s stewardship of the commitments you already made.
This is also why a team’s OKRs are only as useful as the discipline behind setting them. A list of seventeen “priority” OKRs gives you no filter at all. Three to five well-set objectives, on the other hand, make this layer of OKR prioritization fast.
How to Push Back on Delegated Work Without Being Seen as Difficult
This is the section most prioritization advice skips, because it’s the hardest part. You can have the cleanest priorities in the building and still get steamrolled if you can’t say no in a way that lands as professional rather than obstructive. Saying no isn’t a personality trait. It’s a practiced muscle, and it gets stronger with the right scripts.
The frame to start with: you’re not refusing the work. But you recognize you can only do so much with the time available to you in a given day or week. So under the constraint of the time available to you, you must be able to learn how to prioritize work that actually makes an impact.
You’re asking the person delegating to make a trade-off explicit. Most of the time, they haven’t done the math themselves. They’re handing you the request because it’s on their plate and you’re available. When you surface the trade-off, you’re doing them a favor.
Four scripts that have worked for me:
- When the new ask competes with a current OKR. “I want to deliver well on [current OKR or commitment]. Taking [new ask] on this week would push that. Can we walk through the trade-off? If the new request is more important, I’ll re-sequence. If not, I’d recommend parking it until next cycle.” This script makes the trade-off the conversation, not the no.
- When your boss is the one delegating. “I want to do this well. To turn it around on the timeline you’re asking for, I’d need to deprioritize [current item]. Are you OK with that swap, or should we rethink the deadline?” This puts the call back in the right seat without sounding like resistance.
- When the ask doesn’t fit any current strategic pillar or OKR. “Help me think this through. Which of our strategic pillars or current OKRs does this connect to? I want to make sure I’m pulling toward the outcomes the team committed to this quarter.” Asking the alignment question forces the answer to surface before you commit.
- When you’re at capacity and the work could go elsewhere. “That sounds important, and I want to make sure it gets the right attention. My plate is fully committed to [strategic priority] right now. I can recommend [alternative person or path], or we can revisit in [timeframe].” This is the cleanest version of no, paired with a way forward.
Notice the common thread. None of these scripts say “no” outright. They all surface a trade-off and ask the person delegating to weigh in. That’s the move that protects your relationship while protecting your focus.
What Changes When You Start Subtracting
Subtraction feels uncomfortable at first. The first time you decline an ask with a script like the ones above, you’ll wonder if you’ve damaged the relationship. The first time you finish a Monday with five items on your list instead of seventeen, you’ll feel like you’re getting away with something.
Then Friday rolls around and you’ve actually shipped the thing that mattered. And the people who pay attention to outcomes notice. That’s the shift you feel once you’ve internalized how to prioritize work this way. Subtraction isn’t laziness. It’s the discipline that makes the OKR cycle close on what you said you’d close on, instead of fading into the next quarter as a list of activity nobody can quite explain.
For a deeper look at why subtraction is the OKR Leader stance, see Why Most Teams Set OKRs that Fail and The Real Reason Your Team Isn’t Hitting The Mark When Drafting Their OKRs For The Cycle.
Frequently Asked Questions
How do I prioritize work when everything on my list feels important?
If you’re trying to figure out how to prioritize work and everything looks important, start with the urgent-vs-important sort. Drop the items that are neither. Hand off the items that are urgent but not important. After that pass, you’ll usually still have more “important” work than the week holds, which is the cue to apply the OKR layer. Ask which of those important items connect to a strategic priority or current OKR. The ones that do earn the week. The ones that don’t are valid work, but they don’t earn priority right now. That second cut is the one that creates real focus.
How does OKR-based prioritization work with the Eisenhower matrix?
They layer. The Eisenhower matrix does the first sort, dividing work by urgency and importance. The OKR layer comes next, asking which of the “important” items the team already committed to as priorities this quarter through the strategic plan and current OKRs. The two tools aren’t in competition. Eisenhower gives you a useful first pass; OKRs give you the second, sharper cut that subtracts the rest. That layered approach is the cleanest answer I’ve found to how to prioritize work at the team level.
How do I say no to my boss when they’re delegating something I can’t take on?
Don’t say no. Make the trade-off visible instead. Ask them to weigh the new request against the commitments you’ve already made. A line like “to deliver this on the timeline you’re asking for, I’d need to push [current OKR commitment]. Are you OK with that swap?” puts the priority decision back in their seat, where it belongs. Most managers will rethink the urgency once the trade-off is named out loud.
What if the new request is genuinely important but I have no capacity?
Then the conversation isn’t about whether to do the work. It’s about what comes off your plate to make room. Bring a list of your current commitments to the conversation and ask the person delegating to help you choose what gets deferred. You’re not being difficult. You’re protecting the quality of every other commitment you’ve made. That’s the job, especially in a Department Head seat.
The OKR Alignment Audit: A Free Tool for Pressure-Testing Your Priorities
If your team’s OKRs aren’t doing the work of filtering busywork, the issue may not be your prioritization muscle. It may be the OKRs themselves. The OKR Alignment Audit walks you through six anchors per OKR (strategic priority, supporting role, team strength, external opportunity, team weakness, external threat) and gives you a clear read on which of your OKRs earn the team’s attention this quarter and which are orphans.
It’s free during launch. The audit takes about twenty minutes to complete and includes a guided review call and a refined report.
Request Access to the OKR Alignment Audit →
If you want a system that protects focus instead of fragmenting it, OKR Leader is built for that. The platform is designed around how to prioritize work that makes a meaningful impact. It’s the discipline of fewer, better OKRs and the check-in cadence that keeps them in motion.
