The Gravity Problem

There is a moment every leader recognizes, even if no one ever taught them the name for it. An incident is running late. A delivery is at risk. A conversation with a struggling team member keeps getting pushed. And instead of coordinating the response, you open the terminal yourself. Instead of coaching the team through the delivery risk, you take over the plan. Instead of having the harder conversation, you quietly pick up the task the person was supposed to be doing.

It feels like leadership. It is usually the opposite.

Why the pull is so strong

In Never Down, I call this the Gravity Problem: under pressure, leaders drift downward toward the work they once did themselves. A Senior Manager starts firefighting instead of shaping the system. A Manager starts managing tasks instead of leading the team. A Team Leader starts doing the work instead of coordinating it.

The pull makes sense. The lower level is where we are most comfortable — it's where we built our credibility, where progress feels immediate and visible, where we know exactly what "good" looks like. Firefighting feels like contribution. Coaching someone through their own mistake, slowly, feels like doing nothing at all.

But it is exactly where organizations lose leverage. Every altitude exists because someone needs to hold that horizon: the daily work, the team's outcomes, or the system's standards and direction. When a leader drifts down, that altitude goes unattended — not because the person stopped working, but because they started doing someone else's job instead of their own.

Every hour spent below your leadership altitude is an hour of work at your real level that nobody else can do.

A diagnostic you can run this week

You don't need a workshop to catch this. You need one honest question, asked regularly: at what altitude did I actually spend this week — my own, or the one below it?

If a Senior Manager spent the week doing work a Manager should own, or a Manager spent it doing work a Team Leader should own, that is not dedication. It is a leak of the leverage the organization is paying for. And the fix is rarely dramatic — it's usually one thing, handed back deliberately, the following week.

Why this matters more in technology operations

Teams that keep critical services running feel this pull harder than most. Incidents are urgent by nature, and urgency is gravity's favorite excuse. The leaders who hold their altitude best under pressure are not the ones who never step in — they're the ones who notice the pull, name it, and climb back up on purpose, instead of letting the emergency quietly redefine their job.

Next time you feel the pull downward, treat it as a signal, not a failure. Ask what it's telling you — about the moment, about a gap in someone else's capability, or simply about a habit worth breaking. Then go back to the work that only you can do.