When Preeti Malani, a professor of internal medicine at the University of Michigan, reviewed six years of data on loneliness among older Americans, one pattern kept surfacing: the people most likely to report chronic isolation weren’t always the ones you’d expect. They weren’t uniformly the unemployed, the homebound, or the widowed. A significant portion were people who had spent decades being deeply competent at their work, people others relied on, and who had structured their entire social existence around being the person who could solve the problem. When that structure shifted, more than one-third of adults aged 50 to 80 reported feeling lonely, and the rates were far worse for those dealing with physical or mental health challenges. The numbers confirm something I’ve watched play out for years in high-performance environments: competence builds a particular kind of solitude, and almost nobody warns you about it.

The Ground Crew Problem

The pattern showed up most clearly in the place I knew best. I spent twelve years at JPL, and the engineers who drove Curiosity across Mars — who planned each sol’s traverse and monitored each system’s health — were the definition of competence operating in obscurity. They managed a rover millions of miles away that they would never touch again, making decisions that mattered enormously and receiving very little recognition for it. They were extraordinary at what they did. And they were, in a specific and structural way, alone.

The loneliness of that kind of work isn’t about physical isolation. Mission operations teams sit in rooms full of people. The isolation is structural. When you’re the person who understands the rover’s navigation system or the power distribution network better than anyone else on shift, your knowledge separates you. You can’t fully explain your concerns to someone who doesn’t share your depth of understanding, and the people who do share it are usually too busy solving their own problems to connect on a human level.

I watched this dynamic shape entire careers. There was a thermal engineer — I won’t name her — who could diagnose a heater circuit anomaly faster than anyone I’ve ever worked with. She was the first person called on every critical shift. People sought her out constantly. But the conversations were always the same: something was wrong, and she was needed to fix it. When nothing was wrong, nobody called. When the mission wound down and the team scattered to new projects, she told me she didn’t know how to have a conversation with a colleague that didn’t start with a problem report. She’d been so thoroughly cast as a resource that she’d lost the social grammar for being a person.

That’s what competence-driven loneliness actually looks like. It’s not dramatic. There’s no single moment where someone gets excluded. It’s a slow accumulation of interactions that are just slightly less than real connection, happening every day, for years, in rooms full of people who genuinely like each other but have no idea how to show it outside the frame of work.

The Architecture of Being Needed

What I saw at JPL wasn’t unique to space operations. Competence creates a feedback loop that looks, from the outside, like success. You solve problems well. People bring you harder problems. You solve those too. Over time, your identity becomes load-bearing. You are the person who knows how the thermal model works, who can trace the fault tree back to its root, who remembers why a design decision was made seven years ago. You become essential.

Being essential feels good. It also restructures every relationship around you into a dependency. The conversations people have with you increasingly center on what you can do for them. The social exchanges become transactional without anyone meaning them to be. You’re included in meetings because you’re needed, not because anyone thought about whether you’d enjoy being there.

The most capable engineers on any mission team carried a kind of quiet weight that had nothing to do with the technical problems. It was the weight of being the person everyone looked to but nobody looked after. People assumed competence came with a kind of emotional self-sufficiency. If you could keep a rover operating on Mars, surely you could keep yourself operating at home.

That assumption is wrong. And it’s expensive.

Why Competence Specifically Isolates

The broader loneliness data tells a consistent story: about a third of older adults report feeling isolated, and that baseline was never good even before the pandemic. Researchers have argued that loneliness should be treated as a public health issue rather than merely an individual problem. But the general loneliness epidemic doesn’t fully explain what I’m describing. There’s a specific mechanism at work for competent people, and it operates like a design flaw.

Think about it in systems engineering terms. In a well-designed system, every component has a defined function. The more reliable a component is, the less attention it receives during nominal operations. You monitor the parts that might fail. The parts that always work become invisible. That’s good engineering. It’s terrible social architecture.

People who are consistently competent become the reliable components of their social and professional systems. They’re counted on. They’re not checked on. The difference between those two things is the entire gap where loneliness lives.

Research published in Frontiers in Aging Neuroscience found that social isolation and the erosion of social initiation skills form a reinforcing cycle: the more isolated someone becomes, the harder it gets to restart social connections, even when they want to. For highly competent people who have spent years channeling their cognitive energy into professional problem-solving, the atrophy of social initiation skills can happen quietly, over decades, without any single moment of crisis.

You don’t notice you’ve become lonely until you realize that every conversation you’ve had this week was about work. That thermal engineer at JPL didn’t wake up one morning and find herself isolated. It happened one solved anomaly at a time, one transactional conversation at a time, over the course of a decade.

The Social Cost Nobody Mentions

We’ve explored this dynamic before at Space Daily, examining the specific social costs that competence imposes. The mechanism deserves more attention than it typically gets.

Competent people develop what I’d call an asymmetric vulnerability problem. They know how to help others, which means people approach them for help. But the reverse rarely happens. Not because competent people are cold, but because their competence signals that they don’t need help. The signal is wrong, but it’s persistent and hard to override.

There’s also a selection effect. Over time, competent people end up surrounded primarily by people who need something from them. Friends who weren’t work-adjacent fall away. Social connections that existed for their own sake get crowded out by professional relationships that feel social but aren’t, not really. The calendar fills up with obligations that look like human contact but function as service delivery.

I saw this selection effect play out on every long-duration mission I was part of. The ground crew who stayed the longest were the ones who were most needed — and the most needed were, almost without exception, the most socially depleted. They’d given up hobbies, let friendships lapse, organized their lives entirely around being available. The mission justified it. The mission always justified it. And when the mission ended, they were left standing in a social landscape they hadn’t maintained in years.

There’s a broader midlife recalibration that happens around this realization. Part of it involves recognizing that competence purchased at the price of connection is a bad trade, even when it felt like the only trade available at the time. You look around and see that the people you envied weren’t necessarily happier — they’d just made different trade-offs. Understanding that distinction changes what success looks like.

Why Nobody Talks About It

The silence around this problem is self-reinforcing. Competent people don’t talk about being lonely because it feels like a contradiction. How can you be lonely when people need you constantly? The very framing sounds ungrateful. You have colleagues, responsibilities, purpose. What more do you want?

Research clarifies this: loneliness is subjective, separate from the actual amount of social interaction. You can be surrounded by people and still feel profoundly disconnected. What matters is the quality and reciprocity of the connection, not its quantity. For competent people, the quantity of interaction is often high while the reciprocity is near zero.

There’s also a cultural component. In professional environments, admitting loneliness reads as weakness. And weakness, for someone whose social role is built on reliability, feels like an existential threat. If you’re the person everyone depends on, showing vulnerability risks destabilizing the structure. So you don’t show it. You handle it the way you handle everything else — alone, competently, without asking for help.

Some researchers studying loneliness have noted that having limited social contact doesn’t necessarily mean lacking a rich, fulfilling life. That’s true. Being alone isn’t the same as being lonely. But the reverse is also true: having a full calendar isn’t the same as having full connections. The ground crew members with the most packed schedules were often the most isolated people I knew.

What Changes This

I’m not going to pretend there’s a clean solution. The loneliness of competence is baked into how we organize work and value people. But there are structural interventions that help, and they operate at different levels.

At the team level, the intervention is about reciprocity. The most competent person on a team needs to be checked on, not just checked with. There’s a difference between asking someone “What’s the status?” and asking “How are you doing?” In high-performance environments, the first question gets asked constantly. The second almost never. At JPL, the best team leads I worked with understood this instinctively. They’d pull the strongest engineer aside not to ask about a system, but to ask about their weekend. It was a small act, but it disrupted the pattern. It said: I see you as more than what you produce.

At the organizational level, researchers argue for screening. If loneliness and isolation are health issues with measurable consequences, then institutions have a reason to identify and address them. Treating loneliness the way clinicians screen for diet and exercise — as a serious health concern, not an inevitable byproduct of dedication — reframes the problem entirely.

There’s something useful in that framing. Calling competence-driven loneliness a health concern removes the stigma of personal failure. You’re not lonely because you did something wrong. You’re lonely because the system you operate in doesn’t support the kind of connection you need. That’s a design problem, not a character flaw. And if there’s one thing competent people understand, it’s that design problems have design solutions.

The Identity Question Underneath

The deepest version of this problem is about identity. When competence becomes who you are rather than something you do, every social interaction gets filtered through that lens. People relate to you as the competent one. You relate to yourself that way. And competence, by definition, is about handling things. So you handle the loneliness too. Quietly. Alone.

The connection to building identity around effort rather than arrival is direct. If your sense of self is anchored to what you can do, then needing something from others feels like a failure of that self. The compliment doesn’t land. The offer of help feels patronizing. The invitation to just be present, without producing anything, creates anxiety rather than relief.

I’ve seen this in engineers I worked with for years. Brilliant people. People who could trace a signal path through a spacecraft’s avionics in their sleep. People who would stay at JPL until midnight working an anomaly. And people who, when the mission was over and the team dispersed, didn’t know how to call someone just to talk. That thermal engineer I mentioned earlier — she eventually found her way to a book club, of all things. No problems to solve, no expertise required, just people talking about a story. She told me it was the hardest social thing she’d done in years. Harder than briefing the mission director. Harder than defending a design review. Because in a book club, competence doesn’t get you anything. You just have to show up as a person.

The skills that made these people extraordinary at their work — the focus, the analytical precision, the ability to subordinate personal needs to mission requirements — were the same skills that made connection harder. The training that taught them to think in terms of systems and failure modes and margins didn’t include a module on how to be a person when nobody needs you to solve anything.

Competence is lonely because we’ve built environments where being good at things is rewarded with more responsibility and less connection. The better you get, the more you’re used. The more you’re used, the less you’re known. And the less you’re known, the harder it becomes to say the simple thing that would break the cycle: I’m not fine. I need something I can’t build for myself.

Nobody talks about this. Maybe it’s time we did.

Photo by Sabina Kallari on Pexels