The Team Player Trap

"Thanks for going over that case with me," I say, smoothing the wrinkles from my white coat as I stand to leave my boss’s office. When I reach the door, I remember that I'd planned to go for a run before clinic the next morning instead of driving an hour across town for the monthly faculty meeting.

"Hey, Matt."

He looks up from the papers on his desk. "Yep?"

"Would it be okay if I attended tomorrow's meeting remotely?"

His expression tightens. He caps his engraved pen, aligning it neatly with the edge of his desk before looking back up at me. “We expect everyone to be physically present at every general faculty meeting.”

I nod. "Got it."

I walk out of his office, my heart racing. The run will have to wait. I'm new junior faculty, and I need people to know I'm a team player.

Why "team player" works

Human beings are tribal creatures.

From the day we're born, we're organized into tribes: our families, communities, schools, professions, and cultures. Every tribe has rules. Most of them are never spoken aloud. No one sits us down and hands us the manual. We learn them through a thousand small signals: what gets rewarded, what gets ignored, what earns approval, and what earns disapproval.

Over time, we develop an almost instinctive sense of what it takes to belong.

This matters because belonging was never just a social luxury. For most of human history, belonging was survival. The tribe provided protection, food, shelter, identity, and meaning. To lose the tribe could be life-threatening.

Our modern lives have changed dramatically, but our nervous systems have stayed the same. Therefore, the possibility of exclusion still feels dangerous to our primitive brain.

Tribal shame

Clinical neuropsychologist Dr. Mario Martinez describes tribal shame as the distress of believing you've become unworthy of love or belonging within your group.

Because our identity is so intertwined with the tribe, its judgments feel like true referendums on our character. If the tribe thinks we’re not a team player for whatever reason, then we must not be a team player. And if we’re not a team player, we are as good as dead.

The most insidious part of tribal shame is that it rarely arrives as a direct accusation. It's a look. A grunt. A passing comment, like “Everyone else shows up to these meetings."

The unspoken rules often shame the hardest because we don't discover they exist until we've broken one. Or in this case, until we make it clear that we had the audacity to even consider breaking one.

My coach and mentor, Martha Beck, tells a story that illustrates this beautifully. She once assigned her Harvard sociology students to intentionally violate a social norm and observe the reaction. One student went home for Thanksgiving and ate the entire meal, including the mashed potatoes and gravy, with her hands. For ten minutes, no one said a word. Until, finally, her father stood up and said he couldn't take it anymore before storming out of the room. No one ever explained that utensils were expected. They didn't have to. It was a tribal norm.

But it doesn't stop at the family dinner table.

Surgical culture is a tribe

Surgery has its own unwritten rules. No one hands us a document on the first day of residency that says:

Your needs are secondary.

Don't complain.

Don't inconvenience the hierarchy.

Don't question the system.

Don’t set boundaries.

Respond to every unreasonable request from your chief with:“thank you, sir, may I have another?”

Always come to work early, unless, of course, you are in the emergency room or dead.

They just tell us, “Eat when you can, sleep when you can, and don’t touch the pancreas” and throw us into the chaos. And yet we all learn those rules. We learn them the same way we learned every other tribal rule: through observation, correction, approval, silence, and shame. Surgical culture is, in many ways, a masterclass in enforcing unwritten expectations. One of its most effective enforcement mechanisms is just two words: team player.

When "team player" becomes a weapon

Most of us think "team player" is a compliment. Sometimes it is. But sometimes it's something else entirely. Sometimes it's what gets said when someone names a human limit. When they ask a question that challenges the status quo. When they decline another committee, call switch, or double-book. When they speak up about an unsafe system. When they choose their family. When they need rest.

Rather than engaging with the substance of the request, the conversation immediately shifts to the person's character.

They're not a team player.

It's remarkably effective because shame is more efficient than argument. Our point might be valid. Our concern might be reasonable. Our boundary might be healthy and essential for our sustainability in the profession.

But if the conversation can be reframed around whether we’re sufficiently committed, our argument no longer has to be addressed.

The fascinating part is that, in many cases, no one even has to shame us.

We do it ourselves.

We imagine the raised eyebrows before they happen. We rehearse the criticism before it's spoken. We convince ourselves that saying no could cost us our reputation, career, or place within the tribe.

That's how powerful belonging is. The phrase team player sounds like praise. But in many institutions, it functions as a mechanism of social control. Teamwork is a wonderful thing when all members of the team are participating willingly. Team work is toxic when it leverages our primal fear of exclusion.

Someone who contributes generously to a shared mission is a team player. Someone who abandons their own humanity to preserve the comfort of the institution is self-sacrificing. When we are just complying with a broken system out of fear and shame, then we’re no longer playing on a team.