Why Good Coworkers Are Hard to Spot (And Bad Ones Stand Out)

At work, you usually know within a quarter who you don't want to work with again. But identifying who you do want to work with? That can take years — and you still might not be sure. This asymmetry isn't a failure of judgment. It's built into how humans evaluate other people. In this article, we'll look at why bad coworkers are so easy to identify and good ones so hard — and why even glowing peer reviews don't always tell the whole story.

Negativity Bias: Why Bad Stands Out First

Psychology has a well-documented concept called negativity bias. Information of the same intensity, when negative, lands with much more weight than when it's positive. A 2001 meta-analysis published in Review of General Psychology found that across relationships, learning, emotions, and evaluations, negative information carries roughly three to four times the weight of positive information.* In practical terms: it takes about three or four good things to offset one bad thing. The brain itself reflects this. Threat-like signals get processed before our conscious "wait, something's off" response can catch up. Over the long arc of evolution, avoiding danger was more urgent than chasing reward — so our brains are wired to react to negative signals faster and harder. This system shows up at work, too. You see a colleague cut someone off in a meeting once, and the moment sticks. The colleague who quietly kept the same meeting on track? You remember that things went well — but not who made them go well. The effect intensifies under stress. If small things about a teammate are suddenly bothering you when they didn't before, it's worth asking whether the teammate changed or whether you're running on empty.

*Baumeister, R., Bratslavsky, E., Finkenauer, C., & Vohs, K. D. (2001). "Bad is Stronger than Good." Review of General Psychology, 5(4).

Asymmetric Signals: Incompetence Is Loud, Competence Is Quiet

Negativity bias is one layer. There's another layer underneath it: the behaviors themselves aren't equally visible. Bad-coworker behaviors tend to be overt violations. Missing deadlines. Showing up late. Dodging accountability when something goes wrong. Talking over teammates. These are clear norm violations — you only need to see them once or twice to notice a pattern. Good-coworker behaviors mostly show up after the fact, in what didn't happen. A well-timed question that unstuck a meeting. A quiet save on a deliverable that almost fell through the cracks. A conflict that got de-escalated before anyone else noticed. These behaviors leave only their results behind. The contribution disappears into "things just worked." This is the source of that familiar feeling: "everything ran smoothly, but I can't quite tell who made it run smoothly." Great collaborators tend to make their contributions invisible — which means they're rarely called out by name when it's time to evaluate the team.

"Good Coworker" Is a Vague Phrase

The third reason: the criteria themselves are unstable. "Someone I want to work with" sounds clear-cut until you ask people what they actually mean. One person pictures someone who delivers crisp work. Another pictures someone who keeps the room loose. One person prioritizes reliability; another prioritizes openness to trying new things. In American workplaces, "good coworker" often collapses into "team player" — a phrase that itself smuggles in unstated assumptions about agreeableness, conflict avoidance, or simply being easy to be around. A "good coworker" rating means little unless you can reverse-engineer what the rater was actually scoring. Skip that step, and the same phrase ends up describing wildly different people.

Evaluation Is a Function of Relationship

There's one more thing worth flagging. Peer reviews and references from people who've worked with someone are valuable inputs — but they aren't objective data about that coworker. They're data about that coworker in relation to the reviewer. The colleague who was a dream partner for Person A may not be a dream partner for Person B. Differences in pace, decision-making speed, where someone places responsibility, and how they handle conflict mean the same coworker can produce very different collaboration outcomes. Someone who holds the line on deadlines is a rock-solid partner for someone who shares that pace — and a difficult one for projects where the scope keeps shifting. This is the limit of references. Negative reviews generalize reasonably well: "shows up late" or "drops the ball" means roughly the same thing to almost any reviewer. Positive reviews don't. "I loved working with them" tells you something about the fit between them and the person speaking — not about them in absolute terms.

What's Missing: A Second Axis

Pulling it all together, evaluating a person involves at least three layered asymmetries. Bad information sticks harder. Good behaviors leave no fingerprints. The criteria mean different things to different people. On top of all that, the same person looks different depending on who they're working with. So how should you actually size up a potential teammate? Rather than trying to perfect a fundamentally limited process, it's more practical to acknowledge the limits and add another axis of information. Step off the "good vs. bad" axis, at least partially, and look at "how do they work?" Take references seriously — but ask what collaboration context they came from. A tool like Work DNA, which sorts collaboration styles into eight types, sits in exactly this second axis. If you know whether someone leans toward deadlines and precision, toward experimenting with new approaches, toward consensus, or toward immediate execution, you can ask a more useful question than "Is this person good?" You can ask, "How are they likely to work with me?" Before asking whether a coworker is a "good" one, ask what pace they work at. That small shift in question changes the whole way you evaluate someone.