What to Do When Your Workload Is Too Much

When everything is a priority, nothing is, and the person trying to do all of it at once usually ends up doing the wrong thing late. The fix isn’t working faster. It’s making someone with the full picture choose.

Here’s the trap almost everyone walks into: the work piles up, you don’t want to look like you can’t handle it, so you stay late, skip lunch, and grind. Your manager sees nothing wrong: from their chair, the work is getting done. So they hand you more. You’ve accidentally taught the organisation that your capacity is infinite, and you’re the only one who knows it isn’t.

The way out of this isn’t a dramatic “I’m overloaded” conversation that feels like a confession. It’s a small, repeatable move: surfacing the math and handing the trade-off back to the person whose job it’s to make it. Let’s build the exact wording.

Why silent drowning backfires

Absorbing an impossible workload feels noble. It’s actually the most expensive option on the table. You burn your evenings, the quality of everything slips a little, and because nobody asked you to drop a ball, every dropped ball looks like your failure rather than a capacity problem the whole team owns.

There’s a sneaky status fear underneath it: if I say it’s too much, they’ll think I’m slow. But managers don’t experience “I prioritised badly because nobody told me what mattered” as competence. They experience it as a surprise — usually at the worst possible moment, the morning a deadline is already blown. Raising it early reads as ownership. Raising it never reads as unreliability.

The one-line priority script

This is the core move of the whole article, so memorise the shape of it. You name the competing items, you state your honest capacity, and you ask them to choose. You don’t ask for permission to be tired. You ask a logistics question.

Notice what that sentence does. It assumes you’re capable — “do two of those well” signals a high bar, not a white flag. It makes the cut their decision, so when something slips it slips with their fingerprints on it. And it offers a second door — getting help — so the only options on the table aren’t “you do it all” or “it doesn’t happen.”

The key word is “realistically.” It reframes the whole exchange from “I don’t want to” to “here is the physics of the situation.” You’re not complaining about the weather; you’re reading the thermometer out loud.

The left version invites reassurance (“you’ve got this!”) and changes nothing. The right version forces a decision. Vague feelings get vague answers; concrete numbers get concrete calls.

Bring the math, not the mood

Managers respond to scope, not to sighs. Before you raise it, spend five minutes turning your overwhelm into something countable: a quick list of what’s on your plate, the rough hours each piece needs, and the deadlines stacked against the hours actually in the week. When you can say “these four things need about 50 hours and the week has 40,” the conversation stops being about your stamina and becomes about arithmetic nobody can argue with.

This is also where keeping a running record of your output pays off. If you already document your wins — what you shipped, how long it took, what it moved — you walk into the conversation with evidence that you deliver, which buys you enormous credibility when you say a workload is genuinely unrealistic. The person who never complains and suddenly flags a problem gets taken seriously.

Handle the “it’s all urgent” pushback

Sometimes you’ll surface the trade-off and get a reflexive “well, it all needs to happen.” That’s not a no; it’s a manager who hasn’t felt the constraint yet. Your job is to make the constraint real and gently keep the choice with them.

Offering your own ranking is a power move. It shows you’ve thought about the business, not just your calendar, and it gives them something easy to react to. Most managers will tweak your order rather than build one from scratch — and now the priorities are jointly owned. For the harder conversations where a manager keeps loading you up regardless, it’s worth getting deliberate about setting boundaries without sounding rude, because the script only works if you’re willing to hold the line it draws.

Busy week, or broken system?

A crunch is normal. Quarter-end, a product launch, a colleague out sick — these are spikes, and a good week of grinding through one is just the job. The priority script handles spikes beautifully.

What the script can’t fix is a structural problem dressed up as a busy week. Watch for the pattern:

• The “temporary” crunch has lasted three months with no end date anyone will name.
• You’ve flagged the math more than twice and the answer is always “just push through” with nothing taken off your plate.
• Every priority conversation ends with you keeping all the work anyway.
• You’re routinely doing the equivalent of two roles because a vacancy never got backfilled.
• Your manager treats your capacity question as an attitude problem rather than a planning one.

When prioritisation requests keep bouncing off, the issue has moved from this week to this job, and it may need a different conversation — sometimes about staffing, sometimes about how the relationship itself works. If the friction is really about the person you report to, the playbook for dealing with a difficult boss is a better tool than another tidy deadline list. And if you’ve genuinely run the script, brought the math, escalated cleanly, and the answer is still “drown quietly,” those are real signs it might be time to leave — not as a threat, just as honest information about whether the place can ever right-size your load.

Make it a habit, not a crisis

The people who never seem buried aren’t working magic — they’re running a tiny ritual. At the start of each week they glance at what’s incoming, spot the collisions early, and have the two-sentence priority chat before the pile becomes a panic. Done that way, asking for prioritisation stops being an admission and becomes just how you operate: professional, planned, slightly boring. Boring is the goal.

If the workload tension is tangled up with a specific clash — a colleague dumping work on you, a manager and a stakeholder pulling in opposite directions — that’s less a prioritisation problem and more a workplace-conflict one, and it’s worth untangling which is which before you act.