When a team wins, we talk about stars. When a team loses, we talk about blame. Teamwork itself barely gets mentioned either way, and that says something worth paying attention to if you are the one writing job descriptions.
The USMNT lost to Belgium in the World Cup. Within hours, every article and every comment section was doing the same thing, hunting for who to blame. The goalkeeper. The defense. A substitution that came too late. Nobody was writing about the fact that a team is not one player having a bad night. It is dozens of people, from the best player to the last man on the bench, and from the best supporting staff to the most overlooked one, all contributing to the result. When you lose, that entire structure disappears from the conversation and gets replaced with a search for a single name.
Now flip it. The Knicks won a championship with a roster full of legitimate stars. One player scored more than half the team’s points in the final game and walked away with MVP. Fully deserved. But anyone who watched the whole season knows that title did not happen because of one player. It happened because of a long list of people who showed up in ways that never made a highlight reel. When a team wins, credit gets funneled the same way blame does when a team loses. Upward, and narrow.
I was on a panel recently with a handful of HR leaders from major financial firms. Teamwork came up, the way it always does. Everyone had a theory about how their people worked well together and why. The tone in the room was confident, almost rehearsed. And the honest truth, the one nobody says out loud on a panel, is that most of these firms are not actually doing it well. They think they are. That is a different thing entirely.
What this has to do with hiring
I have read thousands of job descriptions over thirty years. Nearly every one has some version of the same line. Must be a strong collaborator. Excellent team player. Works well with others. It is such a standard requirement that nobody questions it anymore.
Here is what I have never once seen in a job description. We need someone who does not work well with others, but who is exceptional operating alone. And yet that person exists in every firm I have ever recruited for. The analyst who does their best work with headphones on and zero meetings. The specialist who is difficult in a room but brilliant on a problem nobody else can solve. Firms need those people just as much as they need the collaborators. Nobody writes a job posting looking for them, because nobody has figured out how to say it without it sounding like a red flag.
The gap between what gets said and what actually works
That panel is not unusual. Most conversations about teamwork inside financial services sound the same. Confident, well intentioned, and light on specifics. Nobody in that room could tell you exactly what their firm does differently that makes teamwork work. They could tell you it is a priority. They could not tell you the mechanism.
That is the real parallel to the World Cup and the Knicks. We talk about teams constantly. We rarely talk about what teamwork actually requires, which is dozens of unglamorous contributions that never get individually recognized, whether the outcome is a loss that needs someone to blame or a win that needs someone to credit.
No amount of trust falls, company softball leagues, or a lavish barbecue thrown once a year at the owner’s waterfront property actually creates that. Everyone shows up, eats the food, and goes back to work on Monday feeling exactly as connected to the mission as they did the Friday before. Firms keep mistaking the appearance of togetherness for the thing itself, and then wonder why engagement scores do not move.
The firms that actually get this right are not the ones with the best sounding teamwork pitch in a town hall. They are the ones who understand that the analyst who cannot stand small talk and the natural collaborator who runs the room are often solving the exact same problem from two different directions, and both of them are the reason the result happened at all.
That is exactly the kind of nuance we look for when we build a team for a client at Ramax Search and Staffing.
