Being a team player is a wonderfully noble thing. It’s helpful. It builds relationships. It makes you that person everyone relies on in a crisis.
Until one day you realise… you’re not just being a team player anymore.
You’re quietly absorbing work that has nothing to do with your actual job description while smiling through WhatsApp messages like “happy to help”.
Somewhere along the way, “collaboration” turned into:
“Hey, you’re good with computers right? Can you just quickly fix this code thing?”
Quickly.
Right.
Because nothing says “quick” like being roped into debugging something you didn’t build, don’t own AND were never trained for.
It rarely starts dramatically.
It’s usually something small like:
- “Can you just take a look at this?”
- “You’re so good at figuring things out”
- “It’ll only take a minute”
And because you’re competent and helpful, you say yes.
Then suddenly you’re:
- Balancing your own workload
- Managing deadlines that were never yours
- Trying to decode systems you were not introduced to
- And somewhere in there… accidentally becoming unofficial IT support
Not your job. Not your department.
But somehow, here you are.
There’s a big difference between:
- “I can help you with this once”
and - “This is now also your responsibility”
And when that line disappears, your actual work doesn’t shrink.
It just… waits for you.
Patiently.
Judging you.
There’s nothing wrong with being helpful.
But there’s a difference between being a team player…
And becoming the unofficial solution to everything that breaks, glitches or confuses someone else.
One builds a career.
The other builds burnout with a smile.
And if you’ve ever found yourself coding something that was absolutely not in your job description while thinking “how did I get here?”…
Yeah.
You’re not alone.