How to tell your boss you have too much work

You have five projects, three deadlines, and a new urgent request, and working later has stopped solving the problem. You're probably doing the thing that quietly makes it worse: absorbing every new task without saying anything, then hoping the week somehow works out.

This article covers how to turn your workload into a short forecast, how to propose tradeoffs your manager can actually decide between, and the exact words to use. Have the conversation while there's still time to change the plan, instead of waiting until something has already slipped.

The advice comes from Shreyas Doshi, who led product at Google, Twitter, and Stripe; Wes Kao, co-founder of Maven; Nir Eyal, author of Indistractable; and John Zeratsky, co-author of Make Time, plus the Mochary Method's issue format.

Turn the workload into a forecast

Before you say anything to your manager, make a short list of every meaningful commitment. For each one, note the deadline, the remaining effort, who's waiting on it, and what happens if it slips. Include the recurring work too: support rotations, approvals, interviews, meeting prep. Those small obligations are often why a calendar that looks open is already full.

Separate facts from estimates. "The analysis needs six focused hours plus a review from finance" gives your manager something to plan around. "This project is taking forever" doesn't give them anything to work with.

Sort the list by the return on your attention

Shreyas Doshi, who led product teams at Google, Twitter, and Stripe, sorts work into three buckets: leverage, neutral, and overhead. A leverage task returns far more impact than the effort you put in. A neutral task returns about what you put in. An overhead task returns less. He built the framework after his first years as a PM at Google left him overwhelmed and stressed.

His point about overload: ambitious people and perfectionists treat all three types with the same level of care, and that's exactly what makes the list unmanageable. Mark each item on your list L, N, or O, then ask yourself:

• Which leverage task will suffer if I keep servicing every request?
• Which neutral task can be done to a simpler standard?
• Which overhead task can be dropped, delegated, batched, or automated?
• Which deadline comes from a real dependency, and which is just a preference?

The labels also leave room for your manager to add context you don't have, like a customer promise or a company priority that changes where a request belongs.

Name the problem your manager can solve

"Too much work" can describe several different situations, and each one has a different fix. Figure out which one you're in before you propose anything.

• A temporary surge. A launch, an incident, or a colleague's absence created a short crunch. Two weeks of help may be enough.
• Conflicting priorities. Several leaders each expect their request to come first. This needs one person who can make the call.
• Scope growth. The work expanded while the deadline and staffing stayed fixed. This needs a smaller deliverable or a later date.
• Persistent understaffing. The team's normal commitments exceed its normal capacity. This needs a durable change, covered at the end of this article.
• A skill or process gap. Rework, unclear ownership, or a skill you're still building is inflating the time required. This may need coaching, pairing, or a different workflow.

Naming the cause keeps the conversation practical. It also protects you from asking for the wrong thing, like extra headcount for what is really a one-week spike.

Put the tradeoff into one sentence

The conversation itself has five parts:

1. State the shared goal. Start with the result you want to protect: a reliable launch, a strong client deliverable, sustainable coverage.
2. Show the constraint. Summarize active work, available time, and the specific deadline or quality bar at risk.
3. Own your part. If a missed estimate or a late escalation contributed, say so factually and briefly.
4. Offer choices. Move a deadline, cut scope, pause another item, lower the quality bar on something, or add help.
5. Ask for a decision. Your manager should know exactly which call you need from them.

The Mochary Method, the coaching curriculum Matt Mochary uses with startup CEOs, formalizes this as "Issue and Proposed Solution": write the issue, acknowledge your contribution to it, propose a solution, and name who owns the next action. Sending that note before a 1:1 gives your manager time to think instead of reacting live.

Make every new yes displace something

Wes Kao, co-founder of the course platform Maven, tells a story about a designer named Alex who never seemed to refuse work but never got buried either. Instead of saying no, he named what the new request would displace and handed the choice back.

Kao's observation as the person making the request: it felt like she was in control, and the conversation stopped being about whether Alex was a team player and became about which work mattered most. You get the effect of a no without having to say it.

Lines you can use when new work arrives:

• "I can take this on. That would move the customer analysis from Thursday to Monday. Is that the right tradeoff?"
• "I have room for the brief or the presentation this week. Which one should be done by Friday?"
• "If the date is fixed, I recommend limiting the first version to the top three accounts."
• "I can send a quick answer today or a reviewed recommendation tomorrow afternoon. Which do you need?"

If something is really a priority, it has to change the order, scope, or standard of your other work. Ask for that change explicitly.

Ask your manager to choose what moves

Nir Eyal, who wrote Indistractable after starting and selling two companies, argues that the standard advice about protecting your time fails the moment you apply it to your manager. His alternative: show the gap between what's been asked and the time you have, and make prioritizing it your boss's job.

He says the payoff goes beyond the immediate decision: a manager who can see how you spend your time stops wondering why things aren't done, and the whole sync takes about ten minutes.

One caution. Don't arrive with a 40-line task dump and ask your manager to solve it from scratch. Group the work, identify the key conflict, and recommend a choice. Your preparation lets the meeting focus on the decision itself.

Scripts for the conversations people avoid

Asking for the workload meeting

"Could we use 20 minutes in our next 1:1 to review workload and priorities? I'm seeing a conflict among [A], [B], and [C] that puts [deadline or outcome] at risk. I'll send a short list with my forecast and two options before we meet."

When every request sounds urgent

"I have four items marked urgent. Based on customer impact, I would order them A, C, B, then D. At current capacity, A and C will be done this week. Would you change that order?"

When the deadline is impossible

"With the current scope and review steps, Friday is not a reliable date. We can deliver the core analysis Friday and the appendix Tuesday, or the full package Tuesday. I recommend the staged version."

When you need temporary help

"Coverage is taking about twelve hours a week while Priya is away. If we want to keep both project dates, I need help with the support queue through the end of the month. Could we rotate one teammate in each day?"

When your own estimate was wrong

"I estimated two days and the work needs closer to four. I missed the data cleanup and should have flagged it sooner. I can deliver a reviewed version Thursday, or an unreviewed draft Tuesday. I recommend Thursday. I've also updated how I estimate this type of work."

When your boss adds work during a 1:1

"I can add that. Before we finish, can we place it against the other three priorities? My recommendation is to pause the documentation refresh until next week."

When your boss says everything is a priority

Stay with the operational question. Ask for an ordered list, a smaller scope, or a different quality bar. "Understood. With the current team and dates, my forecast is that A and B finish Friday, C finishes Tuesday, and D starts after that. If all four need to finish Friday, we need to cut scope or add capacity. Which change should I plan around?"

If your manager still won't choose, send a written forecast anyway. Keep it neutral: the order you'll follow, the expected dates, and the work at risk. Invite corrections. That gives your manager another chance to change the plan and creates a shared record of what everyone knew and when.

Put the decision in writing and change the calendar

Without a written recap, you and your manager can leave the same meeting with different priorities.

Include the decision, the owner, the deadline, and anything that moved. Skip the long defense of why you raised it.

Protect the time the decision created

A priority decision only helps if your calendar changes to match. John Zeratsky, who wrote Make Time with Jake Knapp after years running design sprints at Google Ventures, argues that most productivity systems just make you faster at servicing other people's requests.

After the conversation, block time for the priorities you just agreed on. Cancel or shorten the meetings your manager agreed were lower value. Batch the small neutral tasks. Send a status note for anything that doesn't need a live discussion. When a new request changes the plan, run the tradeoff conversation again instead of quietly absorbing it.

When overload is the normal workload

One priority conversation can fix a busy week. A mismatch that persists for months needs a broader discussion about role scope, staffing, process, or expectations. Track the pattern for several weeks first:

• committed work versus completed work;
• hours lost to recurring support, rework, or meetings;
• scope added after estimates were made;
• priority changes and the work each change displaced;
• quality, customer, health, or retention risks.

Then ask for a durable change: remove a responsibility, revise the role's goals, add capacity, fix an approval bottleneck, or name one person who resolves priority conflicts.

Consider talking to another manager or an HR partner when the workload creates a safety or compliance risk, when someone asks you to misrepresent progress, or when repeated good-faith attempts produce no plan. If the job continually requires unsustainable hours and leadership won't address the cause, it's also fair to ask whether the role can support your health and long-term performance.

Frequently asked questions

How do I professionally say I have too much work?

Show your current commitments and explain which deadline or quality standard is at risk. Then offer options: move a date, cut scope, pause another project, or add help. Ask your manager which tradeoff best supports the team.

Should I tell my boss I feel overwhelmed?

You can name the feeling briefly. Then give your manager the facts they can act on: current commitments, available time, at-risk work, and a proposed change.

Will this make me look incapable?

Flagging risk early is part of reliable execution. Own any estimating mistakes, and show the thinking you've already done toward a solution. Waiting until after a missed deadline leaves your manager fewer useful choices.

What if the extra work could help me get promoted?

High-impact stretch work can support growth. Ask which existing responsibility should move to make room, and how success on the new work will be evaluated. If the larger scope becomes permanent, that's a compensation and level conversation, and it deserves its own meeting.

The workload conversation on one page