Make yourself obsolete
If you’re not trying to eliminate your own job, you’re not paying attention.
If you’re not trying to eliminate your own job, you’re not paying attention. The tasks you’re clinging to—half of them shouldn’t exist. The other half could be done by someone or something else.
Your job isn’t to be necessary. It’s to be useful. Those aren’t the same thing.
Most people work in the opposite direction. They accumulate responsibilities, protect their territory, make themselves hard to replace. That feels like security. It’s actually fragility. The more your value depends on tasks only you can do, the more brittle your position becomes—and the less room you have to grow into work that actually matters.
The question isn’t whether your job will change. It will. The question is whether you’ll be the one who changes it, or whether change will happen to you.
Making yourself obsolete doesn’t mean making yourself irrelevant. It means continually moving toward higher-value work by automating, delegating, or eliminating the work that no longer requires you. The person who can’t be replaced also can’t be promoted. They’ve become load-bearing. They’re stuck.
This requires a different kind of honesty than most people practice. You have to look at your calendar, your habits, your recurring tasks, and ask uncomfortable questions. Could someone else do this just as well? Could a tool do it better? Does this need to be done at all? And the hardest one: am I holding onto this because it matters, or because it makes me feel valuable?
The emotional resistance is real. Tasks become identity. Expertise becomes ego. Letting go of work you’ve mastered feels like giving something away. But hoarding tasks you’ve outgrown isn’t loyalty to the organization. It’s protection of self-image at the expense of contribution.
The goal is to always be working yourself out of your current role and into the next one. Not by climbing, but by clearing. You create space by finishing things, handing things off, and refusing to let your job description calcify around what you happened to be doing last year.
This isn’t just personal strategy. It’s organizational ethics. Every hour you spend on work someone else could do is an hour unavailable for work only you can do. That’s a resource allocation problem—and you’re the one creating it.
If your value depends on being the only one who can do something, you haven’t built value. You’ve built a trap. Get out of it before someone else dismantles it for you.
The practice
- Regularly ask yourself: what am I doing this week that someone else could do, that could be automated, or that doesn’t need to happen at all? Be honest. Then act on the answer—hand it off, build the system, or stop doing it entirely.
- Ask the people above you: what’s on your plate that you’d love to get rid of? That’s where your next challenge lives.
- Ask the people below you the same question about your plate.
- Make it normal to move work toward whoever can handle it best.
Nobody takes you aside anymore
Print taught a generation when to stop. What we lose when the machines absorb the constraints that used to form us.
Your AI agents need a water cooler
Coordination is a property of the room, not the org chart. What that means when your coworkers are agents.
On the death of the author and the birth of the detector
Why worrying about AI authorship is lazier, and more prejudiced, than it looks.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
Did the state change? A simple test for whether work actually happened
Either something exists now that did not exist before, or it does not. A simple test for whether work actually happened, and what changes when you build your systems so they can't record anything else.
How to manage content for multiple clients without flattening their voices
How to manage content for multiple clients without their voices blurring into one house style: a workspace and a voice profile per client, batchable stages, and approval buffers.
Why does AI writing sound generic? It has nothing to work with
Why does AI writing sound generic? Because the model has none of your perspective, examples, constraints, or stakes to work with. The fix is interview-first, not better adjectives.
Start with purpose
Transform your work by prioritizing purpose over tasks. Discover how focusing on time and intention leads to greater impact and fulfillment.
"I don't know" is never an excuse: Make an assumption and document it
Transform uncertainty into action by making reasonable assumptions and documenting them. Embrace decision-making for progress without perfect information.
How I made Tailscale and NordVPN coexist: the Linux exit node pattern
A practical pattern for running Tailscale and NordVPN together, plus the larger question it exposed: private networks need explicit exit profiles, not one vague VPN toggle.