12 min read
There is a moment most capable people can point to, and it never looks like the beginning of anything. Someone needed something handled. You handled it. It went well, which is the whole problem, because the system was watching — not consciously, not maliciously, but the way water finds the low point in a floor.
Nothing was decided that day. No scope was expanded, no role was rewritten, no one made you the owner of anything. And yet from that point forward, work of that shape had somewhere to go, and where it went was you. Repeat that a few dozen times across a few years and you arrive at the familiar destination: a job description that covers about half of what you actually do, and no document anywhere that explains how the other half arrived.
The mechanism has a name
We call it Competence Gravity™: the structural pull that draws unowned work toward the most reliable person in a system. It is one of the ten mechanisms that together produce The Misallocation Effect™, and it belongs to the group concerned with responsibility — how ownership transfers without consent and never transfers back.
The word gravity is doing precise work here, not decorative work. Gravity is not a decision. Nobody in a room agrees to it, nobody can be blamed for it, and it does not stop when everyone involved is well-intentioned and tired and genuinely trying to be fair. It is a property of the arrangement. Mass bends the space around it, and things roll downhill without anyone pushing. Demonstrated competence bends the routing of work the same way, for the same reason: not because anyone chose it, but because the shape of the system makes that path the cheapest one available.
This is not favoritism. This is physics.
Why capability bends the flow
Every organization runs on a quiet, continuous calculation that nobody performs out loud: where does this go so that it gets done. Formal structure answers that question badly. Roles are written before the work exists, they describe categories rather than instances, and no role description has ever survived contact with an ambiguous problem that belongs to two departments and neither.
So the system falls back on evidence. It routes by track record, because track record is the cheapest available signal and it is almost always right about the immediate question. If you want a thing done, send it to the person who has done things. At the level of a single task, this is not a flaw. It is good judgment, and pretending otherwise is how these conversations go wrong.
The failure is not in any one routing decision. It is in the aggregate, because the calculation is run continuously by people who cannot see each other’s answers. Each one independently, sensibly, sends its item toward the most reliable available destination. Nobody is tracking the sum. The result is that load concentrates without support concentrating with it — and concentration of load without concentration of support is what makes this a structural problem rather than a personal one.
How the gravity well forms
Competence Gravity™ is not a single event. It is a sequence, and each stage is small enough to be unremarkable on its own. That is exactly why it is so rarely caught in progress.
- Demonstration. You handle something outside your formal remit and it goes well. Nothing has changed yet. This stage is invisible because it looks exactly like doing your job.
- Registration. The environment records the result — not in a system, but in the working assumptions of everyone who saw it. You are now associated with that class of problem.
- Preference. The next item of that shape arrives with you already in mind. No one assigns it. It simply has an obvious destination, and the obviousness is the assignment.
- Expectation. Routing hardens into assumption. Your involvement stops being a choice anyone makes and becomes the baseline everyone plans around.
- Architecture. The arrangement is now load-bearing. Your presence is a dependency in other people’s plans, and the system’s fragility is hidden by the fact that you keep showing up.
Notice that the ratchet only turns one way. Demonstrating less capability does not reverse the flow; it stalls it while the expectation stays exactly where it was. That asymmetry is what makes the mechanism compound instead of settling. You can stop feeding it and still be carrying everything it has already delivered.
One vendor problem, five stages
Watch it run once, in a case small enough that nobody would think to escalate it.
A vendor invoice arrives coded to the wrong cost center. It is not finance’s, because the miscoding happened upstream. It is not the requesting team’s, because they never saw the code. Somebody in a meeting says the vendor thing is still sitting there, and you say you will look at it, because you can see the fix and it will take eleven minutes. That is demonstration, and it is indistinguishable from being useful.
Three weeks later a second invoice lands wrong. This time someone forwards it to you directly, with no preamble beyond a question mark, because the last one went to you and went away. That is registration becoming preference, and it happened in the gap between two emails that nobody would describe as a decision.
By the end of the quarter, vendor coding questions come to you first. Nobody announced this. When a new person asks who handles them, they are told your name, and the telling is the closest thing to an appointment that will ever occur. That is expectation.
Then you take two weeks off, and three invoices age past terms, and one vendor pauses a shipment. You come back to a small fire and an apology for the fire, and everyone agrees it was unlucky timing. It was not timing. It was architecture — the point at which removing you does not slow the system down but stops it. You are now The Load-Bearing Person™ for a process you were never assigned and could not have declined, because at no stage was there anything to decline.
Eleven minutes, once. That is the entire cost at stage one, and it is why the mechanism is so hard to argue with while it is happening.
What Competence Gravity is not
Three familiar explanations sit close enough to this mechanism to be mistaken for it, and each one sends you toward a fix that cannot work.
It is not workload imbalance. Imbalance is a quantity problem with a quantity answer: measure the distribution, move some items, rebalance. Competence Gravity™ is a routing problem. Rebalance the queue and the same pull refills it, because the mechanism that filled it is untouched. If redistribution has ever worked for you and then quietly undone itself, this is why.
It is not poor boundaries. The boundaries account puts the mechanism inside you — your discipline, your willingness, your inability to say no. But most of these transfers never contained a request you could have declined. There was no ask. There was a gap, an obvious destination, and a silence that resolved itself in your direction. You cannot decline a sentence nobody said. That is Silent Assignment™, and it is the mechanism that makes the boundaries advice fail.
It is not being valued. This is the most expensive confusion, because it feels good and it is half true. You are being relied upon, and reliance is real. But reliance is not recognition, and the arithmetic makes the difference plain: recognition adjusts your compensation, your authority, or your support in proportion to what you carry. Reliance adjusts none of them and increases the carrying anyway. The gap between those two is The Reliability Tax™.
Reading it in your own week
The mechanism is easier to confirm than to argue about. Four questions, answered honestly about the last two weeks rather than about how things ought to be:
- How much of what you did was in your job description, and how much simply arrived?
- For the work that arrived — can you name the conversation in which it became yours? If not, it did not become yours. It landed.
- If you were unavailable for three weeks, what stops? Not what slows. What stops.
- When something ambiguous appears and nobody owns it, how long is the pause before people look at you? If the pause is short, the routing is already settled.
A clean set of answers means the pull is present and operating. It does not mean you have failed at anything. It means you have been reliable inside a structure that has no other way to allocate ambiguity, and reliability is the one trait such a structure will consume without ever asking permission.
How to interrupt it
You cannot switch gravity off, and any advice amounting to being less good at your job is not advice. What you can do is change what happens at the junctions — the specific moments where routing is decided — because the mechanism is strong in aggregate and weak at any single point.
Make the transfer say something. The pull depends on silence. A single sentence spoken at the moment work arrives — naming that it is arriving, and asking whose it is — converts a silent routing into a visible decision. Visible decisions can be discussed. Silent ones cannot, which is the entire reason they stay.
Separate the doing from the owning. Much of what lands on you needs your capability once and your ownership never. Doing something well and being permanently responsible for its category are two different commitments, and the system will merge them if you let it. Untangling them at the point of arrival costs a sentence. Untangling them two years later costs a negotiation.
Fix the gap, not the instance. If work reaches you because nothing else defines where it should go, then handling it well removes the only evidence that the gap exists. That is Symptom Displacement™, and it is how competent people accidentally guarantee the return of every problem they solve. Name the missing owner out loud, even when it is faster to absorb the item.
None of these require more effort. They require the opposite — a small, deliberate pause at exactly the moment your instinct is to resolve things quickly, which is the instinct that built the gravity well in the first place.
Where this sits
Competence Gravity™ is one of four mechanisms in the responsibility group, alongside The Reliability Tax™, Silent Assignment™ and The Load-Bearing Person™. They describe how ownership moves toward a person without consent and does not move back. The other six mechanisms concern urgency and structure. Together the ten produce The Misallocation Effect™, which is the condition rather than any single mechanism within it.
For the lived version of this rather than the structural one — what the pull feels like from inside, late at night, when someone tells you that you make it look easy — read the essay on what your capability costs you. For the question most people arrive with, there is why the most capable person ends up with the most work.
Common questions
What is Competence Gravity?
Competence Gravity™ is the structural pull that draws unowned work toward the most reliable person in a system. It operates through accumulated routing decisions rather than through any explicit assignment, which is why it produces a large shift in workload without leaving a record of how that shift occurred.
Is Competence Gravity the same as being overworked?
No. Being overworked describes the quantity of work. Competence Gravity™ describes the routing that produced that quantity. The distinction matters because quantity problems respond to redistribution and routing problems do not, which is why rebalancing a capable person’s workload tends to undo itself.
Can better boundaries stop Competence Gravity?
Rarely, because most transfers never take the form of a request. Work arrives through gaps, assumptions and silences rather than through asks that could be declined. Interrupting the mechanism requires making the transfer visible at the moment it happens, not refusing a request that was never made.
How does Competence Gravity relate to The Misallocation Effect?
Competence Gravity™ is one of the ten mechanisms that together produce The Misallocation Effect™, and one of the four concerned with responsibility. The Misallocation Effect is the resulting condition; Competence Gravity is one of the forces that builds it.
Where to begin
If the four questions above landed, the useful next step is not a decision about your career. It is a smaller instrument aimed at the next thing that arrives. The free Urgency Reset Framework™ is a one-page tool for that moment — when something has landed on you and you need to know, quickly, whether it is genuinely yours and genuinely now.
When the pull turns out to be constant rather than occasional — when it is not one item but the whole queue — the Clarity Reset System™ rebuilds how work reaches you in the first place.
Your competence is not neutral. It bends the space around it, and it has been bending that space for as long as you have been good at this. That is not a fault to correct. It is a force to account for — and a force you can name is a force you can route around.
— HCOS