Create Distance
Can I design my work so I'm not the bottleneck?
Can I design my work so I'm not the bottleneck?
In short: Every decision that requires me is a point of failure. Sustainable systems remove me from the critical path. The system runs; I am not the engine.
Why This Matters
The INTP 5w4 mind is drawn to the center of its own systems. The Ti function wants to hold the entire model. The 5 wants to be the one who understands, the one who can answer any question, the one without whom the system would fail. This feels like competence. It feels like sovereignty. It is actually fragility. A system where every decision flows through me is not a system at all. It is a job I have created for myself, and I am the single point of failure.
AuDHD note: For the dual‑booting brain, being the bottleneck is especially draining. The ADHD half craves novelty and resists the repetitive maintenance tasks that keep the system running. The autistic half becomes rigidly attached to being the sole operator, creating a dependency that amplifies stress on low‑energy days.
Creating distance means deliberately removing myself from the critical path of my own work. It means designing processes, documentation, and structures that allow the system to function without my constant presence. This is not abandonment. It is the difference between being the engine of the system and being its architect. The engine must run continuously and wears out. The architect designs the engine and can step away. The cathedral that depends on the builder's daily presence will crumble the moment the builder cannot show up. The cathedral built to stand on its own will outlast the builder entirely.
The Principles
Decisions Are Bottlenecks
Every decision that can only be made by me is a bottleneck. Every time someone must wait for my approval, my explanation, or my input, the system slows. When I am unavailable—due to illness, burnout, or simply the limits of a single human's attention—the system stops. Creating distance means systematically identifying these bottlenecks and removing myself from them. This may mean documenting decision criteria so others can apply them. It may mean delegating authority to trusted people or automated rules. It may mean accepting that decisions made without me will sometimes be imperfect, and that an imperfect decision made quickly is often better than a perfect decision delayed indefinitely.
Knowledge Must Live Outside My Head
The 5 hoards knowledge as a form of security. If I am the only one who knows how the system works, I am irreplaceable. This is a trap disguised as job security. Being irreplaceable means I can never rest. It means I am chained to the system. Creating distance means externalizing knowledge: documenting not just what decisions were made but why they were made, what alternatives were considered, and what constraints were operating. The document is not a record for posterity. It is a tool for removing me from the decision path. When the context is documented, someone else can make similar decisions without consulting me.
The 20‑Second Rule for Friction
Friction determines behavior. The 20‑second rule states that if a task takes more than 20 seconds to initiate, it will be avoided. To remove myself from the system, I must reduce friction for autonomous operation and increase friction for actions that require me. If a process currently requires my approval, adding a 20‑second delay to that approval will not fix the bottleneck. The solution is to remove the approval step entirely, replacing it with a rule that allows autonomous action up to a defined limit. The 20 seconds of friction is a diagnostic: if a process regularly makes me wait, I am creating friction for the system. The system will route around me—badly.
The Protocol
Identify one recurring bottleneck
Where do people, processes, or systems wait for me regularly? Write it down.
Document the decision criteria
Write down the rules you would use to make that decision. Be explicit: "If X, then Y. If Z, then W."
Delegate authority to the criteria
Empower the person closest to the work to make the decision using the documented criteria. Communicate the new boundary.
Observe what happens
Do decisions get made? Are they acceptable? If not, refine the criteria. The goal is a continuously improving system, not a perfect one.
Repeat for the next bottleneck
Each bottleneck removed is a degree of freedom regained. The system runs more without me.
The Deeper Layer
Creating distance is uncomfortable. The Fe inferior may fear that removing myself from the system means I am no longer needed. The 4 wing may fear that the work will lose its authenticity. The 5 may fear that I will lose control. These fears are real, and they are the reason most people never build sustainable systems. The cathedral does not need me to run. It needs me to have built it. The shift from operator to architect is the shift from fear to trust: trust that the system I designed can stand without me.
Reflection
- What decision does your team or family currently wait for you to make? What would it take to delegate that decision?
- Where do you hoard knowledge that someone else could use? What would it cost to document it—and what would it cost not to?
- What is the smallest bottleneck you can remove this week? Not the biggest—the smallest. The one that is easiest to document and delegate.