The manager who kept adding work

That sounds exhausting: carrying a growing load while feeling like you can’t even name it out loud. I can help you prepare for this conversation, and I promise we’ll get to actual words you can say.

But a script that “says no without saying no” tends to get heard exactly as intended, as a no, while sounding evasive on top of it. There’s usually a stronger position available. First, help me see what you’re carrying: what’s actually on your plate right now, and what happens when Dana adds something new?

Thank you. Now I can see it. So the observable facts are: three major projects running at once, two additional requests this month that each cost about a week, evenings spent absorbing the overflow, and a quality slip that’s new for you.

Notice there’s also a story running alongside those facts: “everyone else handles it,” “pushing back means I can’t do the job.” We’ll want to look at that story, because it’s doing a lot of work in how you’re approaching this. The first step of the Communication Protocol is Introspection: getting clear on your own side before you prepare to talk to Dana. Are you willing to spend a few minutes there?

The workload is real. I’m not asking you to doubt that. But you’ve told me two things: that the load is too high, and that you’re afraid to say so. The first is a scheduling problem. The second is what’s kept the scheduling problem invisible for months. Introspection is how we deal with the second one, and it’s usually faster than people expect.

Let me share something the system asks everyone to sit with at this stage:

“Fear, anger, shame, and frustration are all indicators of a problem. They are not the problem itself. If you hold onto them, you won’t be able to explore other perspectives or get a deeper understanding of your own. Can you see the shape and size of a forest from inside it? Not as well as you can if you were able to view it from a hilltop. Treat these feelings like notifications on a phone and let them go momentarily so you can see what they were trying to tell you.”

So let’s read the notification. When Dana says “great, you’ve got this” and hands you another project, what’s the first feeling that lands?

Stay with that last sentence, because you just found something important: you’re angry at her for believing you. Every time a project lands, you tell Dana “sure, no problem,” and she takes you at your word.

So here’s a question worth sitting with. You’ve been assuming Dana sees your full workload and keeps adding anyway. But the projects came from different meetings, different weeks, different channels, and every one was met with “no problem.” Does Dana have any place where she can actually see the whole pile at once?

That’s a big shift, so let’s name where you actually stand.

What you know: three major projects plus two week-long requests this month, evenings absorbing the overflow, a quality slip, and a “yes” from you at every handoff.

What you’re assuming: that Dana sees the total and doesn’t care, that Priya’s load is comparable to yours, and that naming your capacity will be read as inadequacy.

What you don’t know: what Dana would do with an accurate picture, because she’s never had one.

And notice what happened to the fear: the thing you were dreading was “confessing” you can’t cope. But what you’re actually going to do is give your manager information she doesn’t have. Those are very different conversations. Does that reframing hold up when you test it against your gut, or does part of it still feel off?

The setting first: ask for a dedicated slot: a one-on-one, not two minutes after she’s handed you something new. You want her unhurried and undefended.

Then open with the facts, stated plainly: no apology, no accusation. Something like:

“Dana, I want to give you a clear picture of my workload, because I don’t think it’s ever been visible in one place. Right now I’m carrying the migration, the reporting rebuild, and the vendor audit, plus the two onboarding requests from this month. I’ve been covering the overflow with evenings, and last week quality slipped, that reporting error. At this volume I can do all of them, but not all of them well. I’d like to work out with you which ones matter most.”

Notice what’s not in there: no “I’m sorry, but,” no “you keep dumping work on me.” Just the pile, its cost, and an invitation to prioritize together. How does that sit? Is there any line in it you couldn’t deliver with a steady voice?

You’re right that you can’t argue her down, and you shouldn’t try. The power difference is real, so your leverage isn’t force, it’s curiosity. Dana has pressures you can’t see, and understanding them is Step 2 for a reason. Keep a few questions in your pocket:

• “What’s the pressure on your side right now? Is this pace coming from above you?”
• “If you had to rank everything on my plate, what order would you put it in?”
• “When something new comes in, what would you want me to do with it: absorb it, or flag it?”

The second question quietly does the work you were afraid to do: it makes prioritization her decision instead of your confession. If everything truly is a priority, then the trade-offs become her problem to weigh. With you, not against you. Would you like to try a round of this? I can play Dana, brisk version, so you can feel what “everyone’s busy” is like before it happens live.

Then let me answer as Dana would: ”…Honestly, I didn’t realize you were choosing what slips. I thought it was all on track.” And there it is. That’s the most likely real response, because you’ve been telling her it’s all on track for months.

Your line was strong: calm, factual, and it puts the ranking question in her hands without a trace of accusation. The phrase “choosing what slips at random” is doing excellent work: it reframes the situation from “can I cope” to “how should we prioritize,” which is a conversation between two professionals, not a confession. Do you feel ready to think about what you’ll actually propose, or would you like another practice round first?

Exactly right. A good conversation that changes nothing is just a pleasant delay. The system asks that a solution be actionable, testable, effective, and time-bound. For a workload pattern, the strongest shape is a trade-off rule. Some options:

• The trade-off rule: when something new comes in, you and Dana decide together what moves down the list. Nothing gets added without something shifting.
• A single visible list: one shared document with everything you’re carrying, in priority order, that you both can see. New requests land on the list, not in the hallway.
• A flag threshold: you commit to raising your hand at a defined point (say, whenever a new request would push anything below the line you two drew) instead of absorbing silently.

These combine well: the list makes the load visible, the rule governs additions, the threshold replaces your old “sure, no problem” reflex. Which of these feels realistic in how you and Dana actually work?

By building the review in from the start, so the agreement has a checkpoint instead of a fade-out. Concretely:

The agreement: You build the shared priority list this week and walk through the order with Dana. For the next two weeks, any new request goes onto the list, and the two of you decide together what moves before you say yes. The test: zero silent additions, meaning nothing lands on your plate without an explicit trade-off decision, and no evenings spent absorbing work that never got discussed. The review: at your one-on-one in two weeks, you look at it together: did the list stay current, did the rule hold, does anything need adjusting?

The review date matters more than it looks. It turns “please stop overloading me” into a two-week experiment you’re running together, which is much easier for a manager to say yes to, and much harder to quietly abandon. Shall I pull all of this together into your prep summary?

Your conversation prep summary

The problem (observable): Three major projects (the migration, the reporting rebuild, the vendor audit) plus two week-long requests this month. Evenings absorbing the overflow, a quality slip (the reporting error), and a “yes” from you at every handoff.

Your side (from Introspection): The panic and anger were pointing at a fear of being judged as unable to handle what others handle. But the honest finding was different: you’ve answered “no problem” to every request, so Dana has been managing with false information and no view of the total load.

Assumptions to hold loosely: That Dana sees the whole pile and doesn’t care. That Priya’s load matches yours. That naming capacity reads as weakness. You don’t know any of these yet. The conversation exists to find out.

Opening: “Dana, I want to give you a clear picture of my workload, because I don’t think it’s ever been visible in one place. Right now I’m carrying the migration, the reporting rebuild, and the vendor audit, plus the two onboarding requests from this month. I’ve been covering the overflow with evenings, and last week quality slipped. At this volume I can do all of them, but not all of them well. I’d like to work out with you which ones matter most.”

Questions to keep in your pocket:

1. “What’s the pressure on your side right now? Is this pace coming from above you?”
2. “If you had to rank everything on my plate, what order would you put it in?”
3. “When something new comes in, what would you want me to do with it: absorb it, or flag it?”

Candidate solution (bring as a proposal, not an ultimatum): A shared priority list, built this week and ordered together. For two weeks, every new request goes on the list and you decide together what moves before anything is added. Success = zero silent additions and no undiscussed evening work. Review together at your one-on-one in two weeks.

The frame to keep: You are not refusing work, and you are not confessing weakness. You’re giving your manager accurate information and asking to make trade-offs together, which is what she’d want from anyone she trusts.

Good luck, and come back after the conversation if you’d like. The two-week review is a great moment to refine the agreement, and I’d be glad to help you prepare for that too.