Make It Legible
Can someone else understand and maintain what I've built?
Can someone else understand and maintain what I've built?
In short: If only I can read the map, the territory dies with me. Legibility is not dumbing down. It is translating the internal model into a form that someone else can use.
Why This Matters
The INTP mind builds models that are internally coherent but opaque to outsiders. The Ti function creates elegant, interconnected structures that make perfect sense to the builder and no sense to anyone else. The 5 hoards knowledge as a form of security—if only I understand the system, I am irreplaceable. The ASD mind may struggle to predict what others will find confusing, because the internal logic is so clear to the self that the gaps in external understanding are invisible.
AuDHD note: For the dual‑booting brain, legibility is a powerful tool. The ADHD half benefits from clear, externalised checklists and instructions, while the autistic half needs explicit, unambiguous documentation to avoid misinterpretation. Writing for the stranger serves both halves.
This opacity is a form of fragility. A system that only I can maintain is a system that dies with me—or dies when I am sick, exhausted, or simply unable to explain it one more time. Making it legible means translating the internal model into a form that someone else can understand, use, and maintain. This is not about dumbing down the work. It is about externalizing the mental map so that the territory remains navigable even when the original cartographer is unavailable. The cathedral that is only visible to its architect is a private hallucination. The cathedral that is documented, labeled, and accessible is a public structure.
The Principles
Write for the Stranger, Not for Yourself
The Ti-Ne system creates documentation that is essentially a transcript of the builder's thought process: full of implicit assumptions, unexplained jumps, and references to mental models that only the builder possesses. This documentation is useless to anyone else, and often useless to the future self who has forgotten the context. The standard for legibility is: "If I handed this to a competent stranger with no prior knowledge of this project, could they understand it?" The documentation must include context, purpose, and explicit reasoning for decisions. It must not assume familiarity. It must start from zero every time.
Legibility Serves My Future Self First
Before anyone else needs to understand the system, I will need to understand it again. The INTP mind moves on from projects. The context fades. The brilliant insight of today becomes a forgotten detail of next year. Writing for the stranger is, first and foremost, writing for my future self. The stranger is a proxy for the person I will be in six months, who has forgotten the intricate architecture, who needs to be guided step by step through the system they built. Legibility is not generosity. It is planning for my own amnesia.
Examples Are Not Explanations
Examples illustrate; they do not explain. The INTP mind naturally offers examples—specific instances of the general principle—because the Ti-Ne system builds from examples. But examples alone do not make the system legible. The general principle must be stated explicitly. The exceptions must be catalogued. The reasoning must be documented. The example is a supplement, not a substitute. The legible system includes the map and the territory.
The Protocol
Select a system you have built
A project, a tool, a process, a codebase—something that currently lives only in your head or in opaque form.
Write a one‑page overview
For the competent stranger: what is this system for? Why does it exist? What problem does it solve?
Document the critical path
What are the steps to use, maintain, or modify the system? Write them as a numbered list. No gaps. Each step must be executable by someone with no prior context.
Add a "Why" section for each major decision
Not just what was decided, but why. What alternatives were considered? What constraints operated? This is the map of the reasoning, not just the territory.
Hand the documentation to a stranger
Find someone who has no prior knowledge of the system. Ask them to follow the documentation. Observe where they get stuck. Fix those points. This is the test.
Schedule quarterly legibility audits
Documentation decays. Knowledge fades. Every three months, review the system's legibility. Update the documentation. The system remains accessible.
The Deeper Layer
Making the system legible confronts the 5's identity as the sole possessor of knowledge. It is an act of vulnerability: I am saying that the system can survive without me, that someone else could step in, that the knowledge I have hoarded is not the source of my value. The 5's anxiety about this is real. It is also the cost of building a cathedral. The cathedral does not depend on the builder. The builder's legacy is not the knowledge they kept; it is the structure they made accessible. Make the map. Let them walk without you.
Reflection
- What system in your work or life would be impossible for someone else to understand or maintain today?
- What would it take to document that system for a competent stranger?
- When you look at your own documentation from six months ago, is it still legible to you? If not, why would it be legible to anyone else?