Short answer
Stop absorbing their work and make the gap visible in project terms, not personal ones. Define your scope in writing, redirect requests back to the owner, and let missed deadlines land where they belong. The moment you silently cover for someone, the problem becomes invisible to everyone who could fix it.
It is one of the most common, exhausting issues discussed on professional forums: the lazy coworker. You log on every day, execute your tasks perfectly, and then look over to see a teammate missing deadlines, doing sloppy work, or simply going invisible—forcing the rest of the team to pick up the slack.
Your initial emotional reaction is likely frustration and resentment. You think: Why should I suffer because they are lazy? I should complain to the boss or fix it myself. But fixing it yourself creates an enabling trap, and complaining incorrectly makes you look petty. The solution is not to carry their load, but to establish bulletproof professional boundaries.
The Enabling Trap
In occupational psychology, the Enabling Trap occurs when high performers quietly absorb the workload of underperforming team members to protect project timelines. Because the project gets delivered, leadership never notices the resource gap. By "saving" the lazy coworker, you mask their underperformance and burn yourself out. To stop it, you must let their missed tasks become visible to the system.
Three Tactical Steps to Protect Your Queue
To establish healthy workload boundaries without triggering political friction:
- Document Your Scope Clearly: Maintain a strict, timestamped log of your specific queue deliverables. Never let task ownership get fuzzy.
- Use the "Redirect" Tactic: When a coworker tries to dump unfinished work on you, redirect it back to them immediately in writing, referencing the project delegation structure.
- Focus on Project Impacts, Not Personalities: If you must escalate to your manager, never say "Name is lazy." Instead, frame it in terms of blockers: “I have completed my frontend tasks, but cannot deploy because we are waiting on the API endpoints delegated to [Name].”
Build Your Boundary Muscle with DrillUp
Saying no and setting boundaries with peers requires practice. DrillUp acts as your tactical workspace co-pilot. Use our Smart Journaling tool to log daily queue metrics, ensuring you always have a paper trail of your deliverables. Run our Boundary Simulator in our safe AI sandboxes to practice redirecting difficult conversations with peers and managers before they happen in real life. Protect your focus. Download DrillUp today.
Frequently asked questions
How do you deal with a coworker who doesn't pull their weight?
Make the work allocation explicit rather than the person's character. In a shared doc, list who owns what by when. Ambiguity is what lets work slide onto whoever cares most, and a written owner-and-date removes the ambiguity without a single accusation.
Should I tell my manager about a lazy coworker?
Report impact, not personality. "The API work is blocked and the release date is at risk" is actionable; "Alex is lazy" makes you look political. Bring the dependency, the deadline, and what you have already tried, and let your manager draw the conclusion.
How do I say no when a coworker keeps dumping work on me?
Redirect with a question rather than a refusal: "I'm at capacity with the migration this week - which of these should I drop to pick that up?" It forces the tradeoff into the open and puts the prioritisation decision back where it belongs.
What if covering for them is the only way the work gets done?
Then do it once, visibly, and put the cost in writing. Silent heroics get you more work, not more credit. A short note - "I picked up the deployment scripts this sprint so we'd hit the date; that's not sustainable for the next one" - is the difference between being seen as reliable and being seen as available.