The Loneliness of Leadership

Why leadership narrows your world as much as it expands it
The Loneliness of Leadership

There’s an old adage that it’s lonely at the top. It’s usually reserved for fame, power, and celebrity. But it applies just as much to org charts.


The internal cost of responsibility

Responsibility doesn’t just mean making decisions - it means carrying the consequences quietly.

As an individual contributor (IC), uncertainty is often offloaded - usually by escalating to your manager. But as the manager, you are the escalation. Even an innocuous request for advice means you’re now aware - and the responsibility lands back on you.

The entire job of a solid manager is to be an ambiguity sponge. Absorbing chaos and leaving the team with a clean message and a clear path forward. The role is defined by turning “we’re not sure” into “here’s what we’re doing.”

The cosmic joke is that people leave, markets shift, priorities change - and yet you’re still the one left explaining why things didn’t work.

It’s your job to hold the space for all that stress, fear, frustration, and disappointment. And when things really go off the rails, you need to double down and project calm. Anything less risks destabilizing the team.


The shrinking pool of peers

Vertical isolation

You can never fully vent down.

You can never fully tell your team how bad things are - how bad it really is, how hopeless it sometimes feels. To do so is mutually assured destruction - a quiet, self-immolation of morale.

Yet you can never fully confide up. Senior leadership has a natural tendency to treat every issue as something to solve - a grenade to jump on, not something to sit with.

So you start editing yourself. Constantly. In every situation. Not out of deceit or self-delusion, but responsibility.

Your words start to land differently now. Casual uncertainty becomes “lack of confidence.” Fleeting frustration becomes “signal.”


Horizontal isolation

As an IC, you might have several peers on your team - and dozens or thousands across the organization just like you. But every team has one lead. Those leads roll up into fewer managers, and eventually a single executive.

As a new team lead, you may have only a handful of true peers. As a VP or CTO in a startup, you may have none.

The peers you do have increasingly sit in different domains or functions - never quite “getting” your exact problem. Even then, there’s a quiet hesitance - a sense that everyone is playing a zero-sum game in a constrained system, where your success competes directly with their goals (funding, staffing, the next promotion, the ear of the CEO).

The surface area for open honesty shrinks. Every promotion trades camaraderie for context. You gain visibility, but lose symmetry.

Loneliness isn’t accidental - it’s geometric. It’s baked in.


Lonely in a crowded room org

Having worked in orgs of all sizes, the busiest ones are often the loneliest.

Everyone wants something from you - direction, decisions, protection, approval. Few want to just be with you. Fewer still want to be in your splash zone and risk the collateral damage.

No one stops by to see how you’re doing. No one asks for a coffee to talk about the kids. Sitting down at lunch changes things - people sit a little straighter, choosing their words more carefully. Conversations narrow.

It’s subtly dehumanizing - people react to the title, not the person.

At the same time, you become a representative of the company. Strong opinions were easy with limited context and few people listening. Now there’s an expectation to support leadership’s decisions - even when you don’t agree.

The reward structure becomes asymmetric. Success is shared. Failure is owned.

If you do your job well, it looks effortless - like you did nothing at all.

Privately, you hope someone notices.
Instead, you become the person who always gets it done.


Naming “The Loneliness Curve”

You’ve been in back-to-back meetings all day. You have nothing left in the tank emotionally.

As you push back from your desk and think about what you actually achieved, there’s nothing you can quite point to.

You stopped things from catching fire. You kept everything aligned for the next deliverable.

All you did was talk to people all day - and yet you feel more alone than you ever did, headphones on, four hours into a coding session.

Connection and belonging live among peers.

Leadership brings more context, more responsibility, and all the pressure that comes with it. At the same time, it dramatically reduces the number of people you feel you can turn to.

If this feels familiar, you’re not doing it wrong.

This is the silent part of the job - the part that never makes it into the job description.

Ideas are cheap
Older post

Ideas are cheap

What distinguishes you from other developers?

I've built data pipelines across 3 continents at petabyte scales, for over 15 years. But the data doesn't matter if we don't solve the human problems first - an AI solution that nobody uses is worthless.

Are the robots going to kill us all?

Not any time soon. At least not in the way that you've got imagined thanks to the Terminator movies. Sure somebody with a DARPA grant is always going to strap a knife/gun/flamethrower on the side of a robot - but just like in Dr.Who - right now, that robot will struggle to even get out of the room, let alone up some stairs.

But AI is going to steal my job, right?

A year ago, the whole world was convinced that AI was going to steal their job. Now, the reality is that most people are thinking 'I wish this POC at work would go a bit faster to scan these PDFs'.

When am I going to get my self-driving car?

Humans are complicated. If we invented driving today - there's NO WAY IN HELL we'd let humans do it. They get distracted. They text their friends. They drink. They make mistakes. But the reality is, all of our streets, cities (and even legal systems) have been built around these limitations. It would be surprisingly easy to build self-driving cars if there were no humans on the road. But today no one wants to take liability. If a self-driving company kills someone, who's responsible? The manufacturer? The insurance company? The software developer?