The same name appears whenever something goes wrong. A deadline slips. A colleague leaves. A customer needs an answer nobody has prepared.

“Ask them. They will sort it out.”

Being trusted can be satisfying. Becoming the unspoken backup for an entire system is a different responsibility—especially when it arrives without authority, time, or acknowledgment.

Find the work that has no formal home

Some duties are visible in a role description. Others gather around a reliable person because they notice gaps and close them.

They remind people, find missing information, explain old decisions, rescue incomplete work, and remember what everyone else has forgotten. Each intervention may look small. Together they can shape a working day.

Before discussing workload, record a representative period. Note what interrupted your planned work, who needed help, why the task reached you, and what would have happened without your intervention. Keep the record factual and consistent with confidentiality requirements.

The purpose is not to produce a list of incompetent colleagues. It is to make a pattern visible. “I am always rescuing everything” is easy to debate. “These recurring requests took the time assigned to this project” gives a manager something concrete to address.

Distinguish a favour from a dependency

A favour is a particular act of help. A dependency is a recurring arrangement that others rely on, whether anyone has formally agreed to it or not.

In an illustrative team, one person helps a colleague prepare a report during an unusually difficult week. That may be reasonable generosity. If the same person is subsequently expected to check every report before it goes out, a new responsibility has emerged.

Name that change without accusing anyone of bad intentions: “I am now reviewing these reports each week. We need to decide whether that is part of my role, who owns the final approval, and which of my existing tasks moves.”

Reliability should make work more trustworthy. It should not conceal the fact that nobody has designed the process properly.

Ask for a structural decision

“I need less stress” may be true, but a useful workload conversation also needs a decision.

Ask which tasks have priority, who owns a recurring problem, what authority accompanies a responsibility, and what backup exists when you are unavailable. If a new task is urgent, ask explicitly what should be postponed.

You might say: “I can complete the client correction today or finish the scheduled analysis. I cannot complete both to the required standard. Which takes priority?”

That is information a responsible manager needs. Avoid quietly accepting both and hoping that exceptional effort will make the conflict disappear.

Where workplace power is unequal, consider the safest appropriate route: a direct discussion, a written clarification, a trusted manager, or an established staff support channel. General advice cannot guarantee a fair response from every organization.

Transfer knowledge without becoming permanently on call

If colleagues depend on information only you hold, help create an accessible record and a realistic transfer plan. Choose a few recurring tasks and teach the next person how to act, including where to find information and when to escalate.

But documentation is not a substitute for staffing, access, or time. A guide cannot give someone authority they do not have.

Agree when the handover is complete and what support remains available. An endless promise to “ask me anytime” can rebuild the dependency you were trying to reduce.

There is room for generosity in a well-run workplace. There is also room for a reliable person to have a day off, finish their assigned work, and be temporarily unreachable.

The most useful contribution you make next may be naming the gap you have repeatedly covered. A team becomes stronger when dependability is shared rather than borrowed indefinitely from one person.

If the same unfinished work keeps finding its way back to you, the next question is how to change the arrangement. Explore When Everyone Relies on You, with practical tools and conversation examples. Read the introduction and first two chapters free.

Keep one idea

Name one recurring rescue task. Ask who owns it and which existing priority must move if it remains yours.

Explore all Insights Follow this reading path