Of the five traits in the Five-Factor Model, four get a mixed reception in the workplace. One gets treated as a defect.
Neuroticism is the trait our culture is most confidently wrong about. The people who carry it high are told, in a hundred small ways, that their most valuable feature is a flaw: they worry too much, they're too intense, they need to relax. I wrote an entire book pushing back on that verdict, because the case against it is overwhelming. This post is the short version.
What Neuroticism Actually Measures
Neuroticism measures the sensitivity of your threat-detection system. High-neuroticism people run an alarm that fires early and often: they feel the timeline risk before it's visible on any dashboard, notice the assumption nobody stress-tested, and wake up at 4:00 AM already rehearsing the failure modes of Thursday's launch.
Low-neuroticism people run a quieter alarm. They stay calm under fire, absorb setbacks without spiraling, and provide the emotional ballast every team leans on during a hard quarter. That steadiness is a genuine superpower, and nothing in this post takes anything away from it.
But notice what a quiet alarm doesn't do: it doesn't detect. A team built entirely of calm people is a building with the smoke detectors removed. Peaceful, right up until it isn't.
The Superpower
High-neuroticism team members are your best risk mitigators, full stop. They are the ones who catch the fuel-line flaw before delivery, flag the architectural gap while it's still cheap to fix, and see the dependency everyone else waved past in the planning meeting.
Think about what vigilance actually is, functionally. It's free, continuous, always-on quality assurance, running on hardware that cannot be turned off. Companies pay enormous sums for risk audits and pre-mortems and red teams, then sit a person with a biological version of all three in their Tuesday standup and tell her to stop being so negative.
The evolutionary logic is worth a moment too. Threat-detection sensitivity persisted in humans across every culture ever measured, because groups containing vigilant members survived things that uniformly relaxed groups didn't. Your anxious colleague isn't broken. She's the descendant of the one who heard the rustle in the grass.
The Pitfall
The honest version of this argument includes the costs, and they're real. An alarm system with no off switch can spiral into analysis paralysis: every path forward generates a new failure scenario, and the scenarios multiply faster than decisions can retire them. Under pressure it can curdle into frantic micromanagement, the alarm trying to control what it can't stop detecting. And carried alone, over years, it becomes the signature trajectory of chronic burnout.
Here's the crucial reframe: these outcomes aren't the trait failing. They're the trait unmanaged, an alarm wired to no response plan. The smoke detector was never the problem. The problem is a building with no fire procedure, where the detector just screams until someone rips out the battery.
How to Work With It
If you manage a high-neuroticism person, strike two phrases from your vocabulary permanently: "don't worry, it'll be fine" and "you're overthinking this." Both tell the alarm it isn't believed, and an unbelieved alarm doesn't quiet down. It escalates, or it stops reporting to you entirely, and the second outcome is worse.
The script that works validates the detection and then aims it: "I hear your concerns about the timeline risks, and I value that your threat-detection is catching these gaps. Of the dependencies you've flagged, which two have the highest probability of catastrophic failure in the next 24 hours? Let's build a structured Plan B for those, together, so we both feel secure."
The mechanics matter. You've confirmed the alarm was heard, which is the only thing that ever quiets it. Then you've converted an unbounded field of worry into a ranking exercise, and prioritizing threats is precisely what this hardware does best. The vigilance doesn't shrink. It gets a target.
If you're the high-neuroticism person, the same conversion works from the inside. The move is from detection to triage: when the alarm floods you with twenty risks, force-rank them, take the top two, and build a concrete response plan for each. A threat with a Plan B attached loses most of its 4:00 AM voltage. You'll never have a quiet alarm, and you shouldn't want one. What you can have is an aimed one.
The Two Sides of the Table
The classic collision is the vigilant team member and the calm leader, each misreading the other's hardware: the leader hears panic where there's data, the team member sees denial where there's ballast. The teams that get this right pair the two deliberately, letting the alarm detect and the ballast respond, which is the whole design principle behind why you need neurotic people on your team. Not tolerate. Need.
That argument, in full, is the subject of my book, Authentic Confidence: Why You Need Neurotic People on Your Team. And if you're wondering how sensitive your own alarm runs, our free assessment maps you across all five OCEAN traits in about five minutes, superpowers and pitfalls included. Your threat-detection system was calibrated long before your first job. Time to find out what it's for.
.svg)