How to Prioritize Work as a Manager

How should a manager prioritize work?

how to prioritize work as a manager is a key topic in modern project management and teamwork. A manager should prioritize by leverage: the amount of durable value a task creates per hour of your attention. Start with the work only you can do — setting direction, removing blockers, and developing people — then delegate or decline the rest, and protect the team’s focus from your own reactive habits.

That definition matters because it changes what “busy” means. A manager who personally clears 20 tickets may be less useful than one who removes the approval bottleneck that created 200.

Why is prioritization different for managers?

Because your output is other people’s output. An individual contributor optimizes their own hours; a manager allocates attention across a system. The cost of a badly chosen priority is not one wasted afternoon, it is a team pointed at the wrong work for a sprint.

The time data is blunt. McKinsey’s survey of middle managers found roughly 28% of time spent on people management, 18% on administrative work — close to one full day a week — 31% on individual-contributor work, and 23% on strategy. More than half said they create the most value through strategy work, yet they spend less than a quarter of their time there.

Asana’s 2025 research puts the broader picture at 55% of knowledge-worker time on “busywork” — status chasing, searching, switching tools. That figure is self-reported and comes from a software vendor, so treat it as a directional signal rather than a precise measurement. The direction is consistent with what managers describe in time audits: the day is full, and little of it was chosen.

> Important note: Being busy is not evidence of prioritization. If your calendar contains no explicit trade-off, someone else made your priorities for you.

What are the three jobs only you can do?

Direction. Deciding what matters this quarter and saying it out loud, repeatedly, in language the team can act on. A team with a declared top three can reject incoming work without escalating to you.

Unblocking. Removing the dependency, approval, or decision that is stopping someone. This is where a manager’s hour has the highest multiplier, because it releases other people’s hours.

People. Hiring, coaching, feedback, and workload conversations. These are the tasks most easily postponed and most expensive to neglect, because the cost arrives two quarters later as attrition.

Everything else is a candidate for delegation, automation, or deletion. That includes work you enjoy, which is usually the hardest category to give up.

Which prioritization framework should you use?

Any of the common frameworks works if you apply it consistently. The failure is switching frameworks every month, which produces meetings about prioritization instead of decisions.

For a manager’s own priorities, the last one is usually the most practical. Frameworks built for product backlogs assume you are ranking features; you are ranking your attention across direction, unblocking, people, and admin.

How do you score a request in 60 seconds?

Use two questions and one division: how much durable impact will this create, and how much effort will it take from me? Then apply a narrow deadline override for commitments you cannot move.

Leverage score = (Impact 1–5 × Durability 1–3) ÷ Effort 1–5

Impact is the size of the outcome. Durability asks whether the benefit lasts a week, a quarter, or a year. Effort is your personal hours, not the team’s. The override applies only to legal deadlines, contractual commitments, and safety issues — not to whoever asked most recently.

Here is a real-shaped week for an operations manager with about 12 discretionary hours.

The top two consume four hours, leaving eight for unblocking, one-on-ones, and the interruptions that always arrive. The bottom two never get done, and that is the point: a priority list without a “no” is a wish list.

Two calibration rules keep the scores honest. Score effort in half-days, not hours, to avoid false precision. And review the scores with the person who requested the work, because they often know a cheaper path.

What should you delegate, and what should you keep?

Delegate anything that does not require your authority, your context, or your relationships. Keep decisions that only you can make, work that requires information the team does not have, and conversations where your presence changes the outcome.

The test takes ten seconds:

• Authority: does this need a decision only my role can make?
• Context: do I hold information that is not written down anywhere?
• Relationship: does this person need me specifically, or just a competent answer?

If the answer to all three is no, it belongs to someone else. If the answer to the second is yes, the better move is often to write the context down and then delegate.

Now the money. Delegation is not automatically cheaper, and pretending otherwise damages trust when the junior person hears “it saves us money” while being handed a mess.

Take a task that costs you 4 hours a week at a loaded $65 an hour: $260. A team member at $35 takes 6 hours because they are learning, plus 45 minutes of your review at $65. That is $210 + $48.75 = $258.75. The saving is $1.25 a week — essentially zero. If their learning curve is shorter and they reach 4.5 hours, the cost drops to $206.25 and you save $53.75 a week, or $2,795 a year.

The real return usually comes from what you do with the freed hours, not from the wage difference. If those 4 hours go into unblocking, the value can be an order of magnitude larger. If they go into more meetings, delegation was just a transfer of cost.

Add the setup cost: 6 hours of briefing and documentation at $65 is $390. At $53.75 a week, payback is about seven weeks. That is a reasonable investment — for a recurring task, not a one-off.

How do you protect the team’s focus?

Set a work-in-progress limit, make the top three visible, and treat every new request as a trade rather than an addition. A team cannot prioritize what it is allowed to start simultaneously.

Little’s Law makes the arithmetic concrete: average cycle time equals work in progress divided by throughput. A team of six completes about five items a week. With 15 items in progress, average cycle time is three weeks. Cap work in progress at nine and cycle time falls to 1.8 weeks — a 40% improvement with no extra hours, because people stop switching.

That is the most underrated prioritization lever a manager has. Adding capacity is slow and expensive; reducing concurrent work is a decision you can make on Monday.

Two supporting habits help. First, an interrupt budget: agree how much unplanned work the team will absorb each week, for example 15% of capacity, and make the cost visible when it is exceeded. Second, a single intake path, so requests arrive in one place instead of in five channels and two direct messages.

> Practical tip: When a new request arrives, ask “what should we stop to do this?” If nobody can name the thing to stop, the request is not yet a priority.

How do you say no without damaging the relationship?

Say no to the request, not to the person, and offer a real alternative: a later date, a smaller scope, or a different owner. Vague deflection (“we’ll see”) is worse than a clear no, because it keeps the work alive in someone’s mental queue.

Three scripts that work:

To a peer: “I can’t take this on this sprint without dropping the onboarding fix. If it’s more urgent than that, I’ll need your help reprioritizing with the sponsor.”

To your boss: “Yes, and here is what moves. This displaces the pricing refresh, which slips two weeks. Do you want that trade?”

To a client-facing colleague: “We can do the small version by Thursday or the full version on the 24th. Which one protects the launch?”

Each script does the same thing: it converts a yes/no conversation into a trade-off conversation, and it puts the decision where the authority sits.

What weekly rhythm keeps priorities alive?

Priorities decay in about three days without a ritual. A light rhythm beats an elaborate planning system.

Monday, 30 minutes: choose the team’s top three for the week, check the WIP limit, and confirm who is unblocking what. Publish the three where the work lives, not in a slide.

Wednesday, 15 minutes: review the interrupt budget and any slipped commitments. Decide whether to protect the plan or change it, and tell the team which.

Friday, 20 minutes: close the loop. What shipped, what moved, what was learned, and what next week’s candidates are. This is also where you notice someone carrying too much.

Keep a decision log with dates. When a stakeholder asks why something slipped, “we chose the onboarding fix on the 12th” is a complete answer.

How do you prioritize when you own several projects?

Rank projects by the cost of delaying them, not by how interesting they are, and protect one strategic project from being starved by three operational ones. A portfolio view is mostly about noticing where your hours actually went.

Take a manager with five projects and 12 discretionary hours a week. The operational project that keeps the business running needs 4 hours. Two client projects need 2 hours each. The strategic project that will matter next year needs 4 hours, and the internal cleanup project needs 2. The total is 14 hours against 12 available, so something must give.

The useful question is not “which project is most important” but “what does a two-week delay cost each one?” If delaying the strategic project by a quarter costs a hiring round and a product window, and delaying the cleanup costs a messy folder structure, the answer is obvious. Write the delay cost down once a quarter; it turns an emotional argument into a number.

Then check the distribution, not the plan. If the strategic project received 90 minutes in each of the last four weeks, it is not a priority regardless of what the roadmap says. A simple time audit — calendar categories, four weeks, no judgement — usually reveals one project absorbing twice the attention its delay cost justifies.

How do you prioritize during a crisis week?

Freeze new commitments, rank by consequence and reversibility, and communicate the freeze in one message. Crisis prioritization fails when managers try to keep everything moving and quietly drop the work nobody is watching.

A workable sequence: name the incident or deadline, list what stops for the next five days, name who is covering each stopped item, and set a review date. Then work only on what is both high-consequence and hard to reverse. Everything reversible can wait a week.

The trap is the silent freeze. If you stop answering a stakeholder without telling them, they assume the work is happening and plan around it. One short message — what is paused, until when, who to contact — costs two minutes and prevents a second crisis.

What mistakes do managers make most often?

• Treating urgency as importance. The loudest request is rarely the highest-leverage one.
• Prioritizing by seniority of the asker. Escalation becomes the real roadmap.
• Keeping work you enjoy. Comfort tasks crowd out direction work.
• Delegating without context. The task bounces back within a week, now later and more expensive.
• Setting more than three priorities. Five priorities is a list; three is a decision.
• Never revisiting the plan. A priority set in January and never reviewed is a guess with a deadline.
• Protecting the team’s time but not your own. Your calendar is part of the system.

Where should the priorities live?

In the same place as the work, with an owner and a date. A priority that exists only in a meeting or a slide cannot be defended when a new request arrives.

That is the gap Doitify is built for: goals become projects with tasks, sub-tasks, owners, and dates, and the board, workload, and reports show whether the top three are actually moving. The AI Coach can help turn a stated goal into a plan and flag work that has gone stale, which is useful when your Monday list and the real board have drifted apart. Doitify is our product, so treat that as a product claim rather than independent advice; the prioritization discipline still has to come from you.

Conclusion

Prioritizing as a manager means choosing where your attention creates the most durable value, then defending that choice against the day’s arrivals. Do the three jobs only you can do, score the rest, delegate with the maths in front of you, and cap how much the team starts at once.

The tools are simple: one scoring rule, one top three, one WIP limit, one weekly rhythm, and a decision log. What makes them work is repetition. A manager who applies a mediocre framework every week will outperform one who adopts a perfect framework and abandons it by Friday.

If this post on how to prioritize work as a manager was helpful, you might also enjoy Research Project Management Template (Free + Example) and What Is a Sprint in Project Management? (Definition, Duration, Events).