Coworker Refused to Help Her Power Through a Two-Person Job While She Was Sick — Then She Returned the Favor

Photo credit: AI-generated image created using ChatGPT.

There’s a certain kind of workplace stress that doesn’t come from the work itself, but from realizing you’re the only one carrying it. You can handle long hours and tough clients if the team is solid. What wears a person down is being left alone in the trench while someone else stands back and critiques your choice of boots.

In the original post, a 34-year-old woman describes getting hit hard with the flu over a public holiday, losing her voice, and planning to rest. Instead, she gets an urgent call from her boss: a client task needs to be done immediately, and it’s normally a two-person job. Her supervisors are out of town, so it’s just her and her coworker, “Melinda.”

She texts Melinda for help and gets a cold reply: she “shouldn’t have answered the call,” and then basically a shrug and “good luck.” The sick employee pushes through the entire workload alone while medicated and in pain. The next day, during the presentation and implementation, the boss asks Melinda to assist because the employee can barely speak. Melinda refuses, dodges calls, and claims she’s out of town even though her location seems to suggest otherwise. Later, Melinda asks for help on a project she’s never done, and the employee declines. Now Melinda is slamming doors and acting offended.

Being “nice” isn’t the same as being a team

A lot of grown adults confuse politeness with partnership. They’ll smile in meetings, laugh at the right jokes, and keep the tone light, but the moment responsibility shows up, they vanish like smoke. That isn’t teamwork; it’s social camouflage.

What makes this situation sting is that the employee wasn’t asking for a favor that belonged to her alone. The urgent task was described as a two-person job, and the next day’s presentation was tied to work that should’ve been jointly owned. Melinda’s refusal wasn’t just unhelpful; it was a decision to let someone else suffer for something the team was meant to handle together.

There’s a difference between boundaries and payback

When the employee refuses to sit with Melinda and work through her new project, it’s tempting to call it revenge. Sometimes it is. But sometimes it’s simply clarity arriving late, after a person has spent too long pretending the imbalance isn’t real.

Notice what she did say: she has real deadlines, she doesn’t have the capacity, and she still explained the steps Melinda needs to take. That’s not cruelty; that’s triage. If you’re buried in your own responsibilities, you don’t light your remaining oxygen on fire just to keep someone else warm—especially someone who already proved they won’t do the same for you.

Payback is, “I won’t help you because I want you to hurt.” Boundaries sound more like, “I can’t carry this for you, and I won’t pretend I can.” The tone matters, but the core issue here is stewardship: of time, energy, and obligations.

Melinda’s reaction tells you what kind of help she wanted

Slamming doors and pouting isn’t the behavior of someone who simply needed a hand. It’s the behavior of someone who expected access. There’s a particular entitlement in workplace relationships where one person treats another like an on-demand safety net, then gets angry when the net develops a spine.

Melinda didn’t ask for a quick review or a specific question answered. She wanted the employee to sit down, go through the entire file, and figure it out alongside her in real time. That’s not “help” in a busy season; that’s outsourcing your own learning curve. Training and collaboration are normal at work, but so is taking ownership of your own assignments—especially after you’ve refused to share burdens in the past.

The boss created the conditions for this mess

Melinda’s choices are her own, but the management piece can’t be ignored. If a task is truly urgent and truly a two-person job, calling a sick employee during a holiday and leaving her to handle it alone is poor leadership. A good boss doesn’t just assign work; he ensures the work can be done without grinding someone into the floor.

Then, the next day, the boss instructs Melinda to assist and she refuses outright. That’s insubordination in plain clothes, and it teaches the whole office a lesson: you can opt out of responsibility if you’re willing to be difficult. If leadership doesn’t address that kind of behavior, the reliable people become pack mules and the unreliable people become “just how she is.”

The employee shouldn’t have had to ask someone outside the company to step in for a presentation because an assigned coworker wouldn’t pick up the phone. That’s not normal friction; that’s a breakdown in accountability.

Don’t let one selfish coworker turn you into a bitter person

The employee admits something important: she doesn’t feel bad this time, and the situation “changed something” in her. That’s an honest reaction. Pain clarifies relationships fast, and illness has a way of revealing who’s mature and who’s merely convenient.

Still, there’s a danger here. When you get burned, the easiest move is to become the kind of person who keeps score with everyone. That’s how one coworker’s selfishness spreads through a whole team: it multiplies. A Christian view of character doesn’t mean you keep offering yourself up to be used, but it does mean you watch your own heart. There’s a difference between refusing to be exploited and cultivating resentment as a hobby.

The goal isn’t to “get her back.” The goal is to be the kind of steady, principled person who helps appropriately, says no cleanly, and doesn’t need revenge to feel whole.

What a firm, professional “no” can look like

If you’ve ever been cornered by an entitled coworker, you know the pressure: you say yes to keep the peace, then you pay for it in late nights and missed deadlines. A clean no isn’t dramatic. It’s specific, calm, and boring.

Something like: “I can’t sit with you and work through the whole file. I have deadlines I’m responsible for. If you send me two or three specific questions, I can answer them by end of day.” That offers limited support without sacrificing your week. If she reacts poorly, that’s information, not an emergency.

And if the work truly requires support, then the right move is looping in the boss: “This project is new to her and it’ll take time. Can you assign someone to train her or adjust the timeline?” That puts the burden where it belongs—on management to resource the work—rather than on the nearest conscientious person.

If you want to go one step further, document the key moments privately: dates, tasks, and refusals. Not to build a vendetta, but to protect yourself if the story gets rewritten later. People who dodge responsibility often become surprisingly creative with their version of events.

The employee isn’t wrong for refusing to carry Melinda’s project after being abandoned during a legitimate crisis. She already did what mature adults do: she communicated, she gave basic guidance, and she stayed focused on her own responsibilities. If Melinda wants the benefits of teamwork, she can start by acting like a teammate.