Being Good at Your Job Shouldn’t Mean Doing Everyone Else’s

What to say when “we know you’ll handle it” has become the entire staffing plan.

Imagine a familiar Thursday. You finish the report early, close three lingering issues, and briefly entertain the possibility of a normal Friday.

Then your manager sends a message: “You’re so good at these. Could you take a quick look?”

Attached is a problem with six people copied in. Nobody has quite agreed on what is wrong, who owns it, or when it became your problem. The deadline, however, has enjoyed unanimous support. Tomorrow.

You can probably fix it. That is the inconvenient part.

A dependable employee can become the easiest answer to a poorly defined problem. If you keep making those problems disappear, the arrangement can look remarkably successful from every desk except yours.

The practical response is to make the work visible before accepting responsibility for it: establish what help is being requested, how much time it needs, who owns the outcome, and what changes if you take it on. That conversation gives your manager something concrete to decide. “I’m overwhelmed” may be true, but it leaves them much more room to interpret the problem as your mood.

Competence makes you convenient

There are reasonable reasons to ask a strong employee for help. They may have the relevant expertise, understand the client, or be ready for a larger assignment. Extra work can be useful experience when it brings appropriate authority, visibility, support, or a clear change in role.

The trouble begins when the same person repeatedly absorbs the awkward work because asking them requires the least effort.

Consider what happens when you quietly repair an incomplete handoff. The client gets a clean result. Your colleague avoids an uncomfortable follow-up. Your manager does not need to resolve the ownership question. Unless you make the additional work visible, they may never understand how the result was produced.

You are left with the hours. They are left with evidence that the arrangement works.

That does not prove anyone has set out to exploit you. It does mean your willingness to absorb the cost may be helping preserve the arrangement.

Find out what “help” means before agreeing

“Take a look” is wonderfully elastic. It can mean fifteen minutes of feedback or responsibility for getting an unfinished project across the line.

Ask the question while the request is still small:

“Do you need my comments on the draft, or are you asking me to own the revisions through delivery?”

If you can offer limited help, define it in ordinary terms:

“I can review the proposal for half an hour and flag the main issues. Priya will need to make the changes and send the final version.”

This is especially useful when a colleague asks you directly and has no authority to change your priorities. You can be helpful without accepting a new deadline on your manager’s behalf.

If the work expands after your review, return to the agreement: “The review has identified a larger rewrite. I can explain the issues, but taking on the rewrite would need to go through my manager because of the client report.”

Keep the distinction visible. Otherwise a sensible offer of advice can become ownership through sheer conversational momentum.

Give your manager an actual tradeoff

When the request comes from the person who sets your priorities, show them the collision.

“I can take the revisions through delivery. They look like about four hours of work, which would move the client report from Friday to Monday. Do you want me to make that change?”

Use an honest estimate. If you have not inspected the work, say so: “I need twenty minutes to assess it before I can give you a delivery time.” Inflating the effort undermines the conversation; understating it to sound agreeable recreates the problem.

Your manager may respond, “They both need to happen.”

Then narrow the question to the options available: “Could someone else take the data check, or can we send a shorter report on Friday? With the current scope, I can’t complete both in the time available.”

If their answer remains unchanged, avoid giving a reassuring promise you already expect to break. State what you can complete and flag the remaining risk through your normal work channel. A clear conversation cannot manufacture capacity, but it can prevent a private workload problem from becoming a surprise missed deadline.

Put the extra work where the work is tracked

If the additional assignment is approved, record the change in the place your team already uses to manage delivery.

“Confirming today’s change: I’m taking ownership of the proposal revisions for Friday. The client report moves to Monday. Priya is handling the data check.”

There is no need for an indignant essay, a dramatic subject line, or six historical examples attached for context. The purpose is to leave a usable record of scope, ownership, and timing.

Repeated rescue work also belongs in routine workload discussions. Describe what you did and what it displaced. “Helped with a proposal” conceals more than it explains. “Rebuilt the pricing section and coordinated approval, taking four hours originally allocated to the report” gives a manager something they can plan around.

If you are concerned about sounding transactional, remember that the organization is already making decisions about your time. You are supplying the missing information.

A pattern needs a different conversation

Handling each request well may still leave you handling the same request every week.

At that point, bring a small set of recent examples to a planned conversation. Choose enough to show the pattern without conducting a prosecution of everyone who has ever asked you for anything.

“Over the last month, I’ve taken over three late proposal revisions. That has delayed the reporting work I’m accountable for. Who should own these revisions going forward, and what level of review do you want from me?”

Your manager might decide that the work should formally become yours. That opens another conversation about what leaves your role, which decisions you can make, and how the responsibility will be assessed. If it is being presented as development, ask what that means in practice: “What capability am I expected to demonstrate, and when will we review it?”

They might instead agree that the original owner needs training, a better handoff, or a clearer deadline. Follow up on that change. An agreeable meeting followed by identical requests is useful information, too.

What if being direct feels risky?

The employee who needs the income has to live with the consequences of this conversation. Advice should respect that.

If a blunt refusal would create unnecessary exposure, start with narrower clarification: “Which part do you need me to review?” Put the new task into the shared plan. Ask your manager to confirm the order of work during an existing check-in. These are ordinary coordination questions, and they can make the load more visible without requiring a confrontation.

Some managers still resist acknowledging limits. If repeated, specific conversations produce no change, the problem may be beyond what better wording can solve. You can then weigh your options with more information: a role discussion, an internal move, or a search elsewhere, according to what is realistic for you.

For the next “quick look,” begin smaller. Open the attachment, assess the request, and ask who owns delivery before you start repairing it.

You can remain the person who does excellent work. The Friday deadline does not have to become yours simply because you were copied in.

For the wider questions behind repeated overload, including priorities, responsibility, and managing up, read Sable Marchetta’s Workplace Boundaries Without Conflict.