OLD SCRIPT DETECTED
Try this response:
“I can be reliable with my own work and still decline work that isn't mine to own.”SEE THE PRACTICE
THE THOUGHT
“Everyone just offloads their work onto me”
YOUR RECORDED RESPONSE
“I can be reliable with my own work and still decline work that isn't mine to own.”
ONE PRIVATE MOVE
The next time someone asks you to take on something you didn't initiate, pause before answering. Write down in a private note what you're currently committed to. Then decide based on that list, not on the feeling that refusing might cost you. Observe: what actually happens when…
SCENE_01
You're reviewing your own deliverable when a Slack message appears: a senior colleague asking if you'd mind looking at something. Not asking if you have capacity. Not framing it as a request with timing. The phrasing itself is already deferential—they know you'll say yes. The work is attached. It's not small. You open it. By the time you close the document, you've already started mentally reorganizing your afternoon to fit it in.
SCENE_02
Six months back, you finished projects on time. Now you finish them on time while absorbing someone else's draft, while flagging another team's oversight, while mentoring through someone's blockers. Your output looks the same. Your hours don't. You notice you're slower to start your own work because the constant small adds have created a background hum of incompleteness. The private story you tell yourself: if you push back now, after all this, it reads as peaked. Done. So you don't push back. You absorb. You become the organizational shock absorber.
SCENE_03
The real mechanics are simpler than you fear. Your reliability is not a permanent obligation. It's a current fact that others notice. They route work to you because it lands safely—not because you owe them unlimited access to your time. The difference: one is a description of your track record. The other is a claim on your future. You can keep one and change the other. Start small: the next soft ask—the one phrased as a favor—say 'I'm full right now, and I want to give it proper attention. Can we find another route?' Don't explain. Don't apologize for your own schedule. Notice what happens. The work still gets done. The world doesn't…
TRACE · 01/04
SOURCE_LOCATED · 02/04
The Reliability Trap
Being dependable means I absorb whatever lands near me. If I stop absorbing, I signal that I've become unreliable. So I don't stop. I silently rearrange. I become the person who handles overflow. This protects my reputation and ensures no one questions my value.
FORGING_REPLACEMENT · 03/04
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
When I think
“Everyone just offloads their work onto me”
I say
“I can be reliable with my own work and still decline work that isn't mine to own.”
Then I do one thing
The next time someone asks you to take on something you didn't initiate, pause before answering. Write down in a private note what you're currently committed to. Then decide based on that list, not on the feeling that refusing might cost you. Observe: what actually happens when…
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
You're not avoiding work. You're distinguishing between work you committed to and work that arrived as an assumption. Commitment is choosing. Overflow is inherited. The difference is agency. Lazy people avoid their own projects. You're finishing yours while absorbing others'. The move here is stopping the absorption, not stopping the output.
The short version: you'll find out. Most of the time, they route to you because it's efficient, not because you're the only option. When you're unavailable, actual delegation happens—they learn to ask differently, or they distribute the load. That's not collapse. That's the system working as designed.
That's a different conversation than this thought reveals. This pattern is about peers and colleagues offloading. If your manager is explicitly trading promotion or stability for unlimited extra work, that's a negotiation question, not a thought-interruption question. For now: notice whether the offloading is coming from above or sideways. The move changes based on that answer.