8 min read
There is a person on every team who can be handed almost anything and it lands. You know who they are on your team. There’s a reasonable chance you are that person on yours.
Watch what happens to them over eighteen months.
They start with a defined role and a reputation for reliability. Then a project goes sideways and someone says, half as a compliment, just give it to her, she’ll figure it out. She figures it out. A vendor relationship gets messy and the same logic applies — he’s good with people, let him handle it. He handles it. A new hire needs onboarding, a cross-functional thing needs an owner, a fire needs putting out at 6 PM on a Thursday. Each time, the most capable person is the obvious choice. Each assignment is individually defensible. Anyone in the room would have made the same call.
Eighteen months later that person is carrying roughly double what their peers carry, is quietly exhausted, and cannot point to a single moment where they agreed to it. They didn’t say yes to a heavier load. They said yes to a series of reasonable requests, and the load was the residue.
This is not bad luck and it is not poor boundaries. It is a structural force, and it has a name.
What’s actually pulling work toward you
Capability is not neutral. It exerts a pull.
When a team has work that needs to land and a choice of where to send it, the work does not distribute evenly. It moves toward the person most likely to complete it cleanly, the same way a dropped object moves toward the densest mass nearby. The more reliable you are, the stronger your pull. Reliability is mass. Mass bends the field around it. Work falls inward.
Call it Competence Gravity. It is the tendency of tasks, decisions, and ownership to migrate toward the most capable person in a system, not because anyone decided to overload them but because at every individual decision point, sending it to them was the rational move.
The reason this is so hard to see — and so hard to resist — is that gravity acts at the level of the single instance, but the damage only appears at the level of the accumulation. Each request, examined alone, is reasonable. Of course the reliable person should take the high-stakes deliverable. Of course the person who’s good with the difficult client should keep the difficult client. There is no individual decision you can point to and call wrong. The wrongness is only visible in the aggregate, and the aggregate has no author. Nobody assembled your workload. It accreted.
This is the same illusion the urgency loop runs, viewed along a different axis. There, each urgent request looked reasonable and only the loop revealed the trap. Here, each assignment looks reasonable and only the gravitational drift reveals it. Same structural sleight of hand: a force that hides inside individually defensible decisions.
Why your competence makes it worse, not better
The cruel part of Competence Gravity is that the trait being punished is the trait being rewarded. The better you get, the more pull you exert, the more falls toward you, the more buried you become.
Three mechanisms compound the drift.
Demonstrated reliability lowers the cost of asking you. Every time you absorb something and deliver, you teach the system that sending things to you is cheap and safe. The next request meets less friction than the last. A person with a track record of saying I’ll handle it is a person to whom handling things gets routed by default — no deliberation required, because the deliberation already happened the first ten times and you passed.
Capable people pre-absorb the cost of asking. Less reliable colleagues impose a tax on whoever delegates to them: the work might come back wrong, late, or needing rework. You don’t impose that tax. So a manager weighing where to send something isn’t weighing it neutrally — sending it to you is genuinely the lower-cost option for them. The gravity isn’t irrational. It’s an accurate response to the fact that you really are the safest pair of hands. Which is exactly why it won’t stop on its own.
The accumulation is invisible to everyone but you. The person assigning the eleventh thing has no view of the previous ten — those went to you through different people, on different threads, in different weeks. Each delegator sees only their one reasonable request. You are the only node in the system with visibility into the total. Which means you are the only one who can possibly notice the pattern, and you’re noticing it from inside, while exhausted, which is the worst possible vantage point for seeing structure.
If you’ve ever found yourself thinking why do I have so much on my plate and been unable to trace it to a decision, this is why. There was no decision. There was a field, and you were the densest thing in it.
Why working harder accelerates the trap
The instinct, when the load gets heavy, is to get better at carrying it. Tighten the system, work the edges of the day, become more efficient. This is the most natural response available and it is precisely the wrong one.
Efficiency increases your capability. Capability increases your gravitational mass. Mass increases the rate at which work falls toward you. You will get better at carrying the load and the load will grow to match — because the thing that determines your load is not your capacity, it’s your pull, and improving your capacity strengthens your pull.
This is why the most competent person on a team is so often the most overloaded, and why their overload is so resistant to personal-productivity fixes. They are not failing to keep up. They are succeeding so visibly that the system keeps routing more toward the success. You cannot out-work a force that feeds on your output. The harder you pull, the more it sends.
What changes the load is not your speed. It’s the field. You have to make yourself a less automatic destination — to put friction back into the act of routing things to you, so that “just give it to her” stops being the frictionless default it became.
What to notice this week
You don’t reset Competence Gravity in a week. But you can make it visible, and visibility is the precondition for everything that follows.
1. Count your inbound channels, not your tasks. Don’t list what you’re doing — list who can put work on you and through how many doors. Direct manager, skip-level, three peers who “just loop you in,” two downstream teams, the one client who has your cell. The number of channels is the size of your gravitational field. Most overloaded operators have never counted it.
2. For your three heaviest items, find the assigning decision. Try to locate the moment someone decided this was yours. For at least one of them, you won’t find a decision — you’ll find a drift, a somehow this became mine. That drift is gravity. Name it as such.
3. Notice the next “just give it to —” before you agree. Sometime this week, work will be routed to you with the reliability logic out loud or implied. Catch it in the moment. You don’t have to decline it. You just have to register, consciously, that the field is acting on you right now — that this is an instance of the pattern, not an isolated favor.
4. Ask, once, “who else could carry this if I were out?” Not to offload it today. To find out whether the answer is a name or a silence. If the honest answer is no one, you have not found a compliment. You’ve found a single point of failure, and the single point is you.
None of these moves lighten the load this week. They do something more important: they convert an invisible force into a named one. A force you can name is a force you can begin to redirect. A force you can’t name just keeps pulling.
The cluster this article belongs to
This is the entry point to a body of work on reclaiming ownership — the recognition that most operator overload is not a volume problem to be worked harder, but an allocation problem in which responsibility has drifted to one person and stayed. Two adjacent pieces extend the frame:
- The Quiet Habit of Picking Up What Falls examines the reflex that keeps work stuck to you even after you tried to hand it off.
- You Are Not Overloaded. You Are Over-Owning. is the thesis piece — why the entire frame of “too much work” points you at the wrong fix.
The shorter version: you did not choose to carry the most. You were the densest mass in a field that had no author. The first move is to see the field.
Start with the diagnostic
If you want to map your own gravitational field as a structured exercise — counting your inbound channels, tracing your heaviest items back to the decisions that never happened, and naming where the drift is strongest — the free Urgency Reset Framework is where to start.
It’s a one-week structural audit. It won’t lighten your load by Friday. It will hand you something more useful: a clear picture of how the load assembled itself, which is the only ground from which it can be redistributed.
It is free. It takes seven days. The first prompt lands in your inbox the moment you sign up.
A dedicated structure for redistributing ownership — the Responsibility Reclaim System — opens to a founders’ list in Q3 2026. If that’s the work you’re actually here for, you can ask to be told first.