9 min read
Try to answer a simple question. Where does your job end?
Not your title — your actual job. The set of things that are yours to own, past which something becomes someone else’s problem. Most capable operators, asked this directly, can’t draw the line. They can tell you what they do, which is an enormous and growing list. They cannot tell you where it stops, because the edge that used to be sharp has gone soft, and they can’t remember when.
You used to know. When you started the role, the boundary was clear — here’s my scope, there’s the edge, beyond it isn’t mine. Now the edge is somewhere out past the horizon and you couldn’t locate it if asked. You didn’t move it. Nobody announced a change. And yet the territory you’re responsible for is visibly larger than the territory you were hired for, and you can’t point to the moment it grew.
That’s not a memory problem. It’s a structural one, and it has a mechanism.
The edge that moves while you watch the center
Your role has a boundary — the line past which work isn’t yours. That boundary is supposed to hold still. Your job is to operate inside it.
But the boundary doesn’t hold still. Every time a crisis lands near the edge of your scope and you absorb it, the edge moves outward to include it. Every time someone says can you just and the thing they’re asking sits slightly outside your role and you do it anyway, the edge moves to enclose that too. The boundary migrates outward, one absorbed thing at a time, and it migrates in only one direction: out. Things get added to your scope. They essentially never leave it.
Call it Boundary Drift. It’s the slow outward migration of your role’s edge, driven by absorbed crises and accumulated can-you-justs, each of which expands your scope by an amount too small to notice in the instant and permanent in the aggregate.
The reason you can’t see it happening is the same reason you can’t watch a glacier move. The per-instance change is below your detection threshold. When the can-you-just arrives, the marginal expansion it represents is tiny — a single small thing, obviously worth doing, not worth making a fuss over. You’re evaluating it as an isolated favor, and as an isolated favor it’s trivial. What you can’t see, in that moment, is that you’re not evaluating a favor. You’re ratifying a new permanent location for your boundary. The favor is temporary. The scope expansion is forever.
And because the drift only ever moves outward, it accumulates. There’s no countervailing force pulling the edge back in. Crises get added; they don’t get subtracted. Can-you-justs get enclosed; they don’t get released. Your scope ratchets — it clicks outward and locks, clicks outward and locks — until the territory you’re accountable for bears no resemblance to the territory in your job description, and you have no idea how the gap got so wide.
This is my job keeps expanding stated as a structure instead of a complaint. The job isn’t expanding because you’re being asked to do more in some announced, negotiable way. It’s expanding because its edge drifts outward below the threshold where you’d notice and object.
Why every individual expansion is impossible to refuse
The genius of Boundary Drift — if a structural force can have genius — is that it never presents you with a refusable case.
A refusable case would be someone walking up and saying I’d like to permanently expand your responsibilities by forty percent with no change in title or support. You’d refuse that instantly. It’s legible, it’s large, it’s clearly a bad deal. But that case never arrives. What arrives instead is a sequence of micro-expansions, each one individually reasonable, each one obviously not worth the social cost of pushing back over.
Can you just sit in on this one call. Of course. Can you just own the handoff to the new team, you know it best. Sure. Can you just keep an eye on the vendor thing until we hire someone. Fine — and then the someone is never hired, and the vendor thing is yours forever, and you absorbed a permanent responsibility through a word, just, that promised it was temporary and small.
Each can-you-just is calibrated, whether the asker knows it or not, to sit just below your refusal threshold. To refuse it, you’d have to be the person who made a thing out of a tiny ask — and capable, reliable operators are precisely the people least willing to be that person. So you absorb it. The edge moves. And the next ask comes in calibrated against your new, larger scope, so it too sits just below the threshold, and you absorb that too.
This is Competence Gravity operating on the boundary itself rather than on individual tasks. The same reliability that pulls discrete work toward you also makes you the obvious place to attach anything that doesn’t have a clear home. Orphaned responsibilities drift toward the most capable person and get enclosed inside their scope, because enclosing them there is the path of least resistance for everyone except the person doing the enclosing.
You can’t defend a line you can’t see
Here’s the trap that makes Boundary Drift so durable: you cannot defend a boundary you can’t locate. And the drift has, by design, erased your ability to locate it.
Boundary defense — saying no, that’s outside my scope — requires knowing where your scope ends. But after enough drift, you don’t know. So when the next can-you-just arrives, you have no line to point to. You can’t say it’s outside your scope because you genuinely can’t tell anymore whether it is. The boundary has gone so soft that everything feels at least arguably yours, which means nothing is clearly not-yours, which means there’s no ground from which to decline. The drift doesn’t just expand your scope. It dissolves the instrument you’d use to stop the expansion.
This is why willpower fails here. You can resolve to “set better boundaries” all you want, but a boundary is a location, and you can’t enforce a location you haven’t fixed. Setting better boundaries with a drifted, invisible edge is like defending a border you can’t see on a map you’ve lost. The first move was never to push harder against the line. It was to find the line again — to make the edge visible enough that you could finally tell what’s inside it and what isn’t.
Relocating your edge
You re-fix a drifted boundary the way you’d survey lost property: not by guessing, but by re-establishing the marks.
1. Write down your scope as it was defined, not as it is now. Pull the original job description, the role you were hired into, the thing you’d describe to someone outside the company. That’s your boundary’s original location. The gap between that and what you actually do today is the total accumulated drift — and seeing the size of that gap is often the first time the drift becomes real to you.
**2. For each thing past the original edge, name the can-you-just that added it.** Go through the work that lives outside your defined scope and trace each piece back to the absorption that enclosed it. Most will trace to a just — a small temporary ask that became permanent. Naming the entry point of each expansion converts an amorphous “my job grew” into a specific list of refusable, returnable items.
**3. Treat the next can-you-just as a boundary event, not a favor.** When the next one arrives, register what it actually is: a request to permanently relocate your edge, dressed as a momentary favor. You don’t have to refuse it. You have to see it correctly — as a scope decision, not a kindness — so that absorbing it becomes a choice instead of a reflex.
4. Ask the question that exposes the word “just.” When something is framed as can you just keep an eye on it until, ask: until when, and then who owns it? The word just survives only as long as the “until” stays vague. Force the “until” to become specific and the temporary thing either gets a real end date or reveals itself as the permanent transfer it always was.
None of this lightens your load this week. What it does is restore the instrument you lost — a known location for the edge of your job — without which every conversation about your workload is conducted in fog. You can’t redistribute, decline, or protect anything until you can say, plainly, where your job ends. The first work is drawing the line back onto the map.
The cluster this article belongs to
This piece is part of a body of work on reclaiming ownership — the recognition that most operator overload is an allocation problem, not a volume one, produced by structural forces that operate below the threshold of any single decision. Two adjacent pieces frame it:
- The calendar version of this exact mechanism is in The Calendar Isn’t Yours. It’s an Inheritance. — how meeting load drifts onto you the same way scope does, one inherited commitment at a time.
- Why the Most Capable Person Ends Up With the Most Work names the gravitational force underneath both the task drift and the boundary drift.
The shorter version: your job didn’t grow because anyone decided it should. Its edge drifted outward, one can-you-just at a time, until you lost track of where it ends — and you can’t defend a line you can’t see.
Start with the diagnostic
If you want to relocate your own boundary as a structured exercise — pulling the original scope, measuring the accumulated drift, and tracing each expansion back to the can-you-just that added it — the free Urgency Reset Framework is where to start.
It’s a one-week structural audit. It won’t shrink your scope by Friday. It will hand you the thing you lost to the drift: a clear, fixed location for where your job actually ends, which is the ground every boundary decision after it stands on.
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.