Making Invisible Systems Visible
The central thesis of this site — why legibility matters, and how to achieve it without oversimplification.
Every project on this site shares a single thesis: invisible systems should be made visible. Not simplified. Not dumbed down. Made legible — readable by someone who cares enough to look.
The Problem with Invisibility
Most of the systems that shape our lives are invisible. The payment network that moves your money. The routing infrastructure that delivers your messages. The recommendation algorithm that shapes what you see. The identity system that proves who you are.
Invisibility isn’t neutral. When a system is invisible, you can’t:
- Notice when it’s broken
- Understand who benefits from its design
- Participate in decisions about its future
- Develop intuition for how to use it well
Invisibility concentrates power in the people who can see the system — its builders, maintainers, and operators.
Legibility vs. Simplification
Making something visible is not the same as making it simple. A subway map is legible without being a complete representation of tunnel geometry. A circuit diagram is legible without being a photograph of the actual board.
Good legibility preserves the essential relationships while stripping away implementation noise. The goal is to make the system thinkable — to give someone a mental model that’s accurate enough to reason with.
Three Tools for Visibility
Metaphor — Map the unfamiliar onto the familiar. The dabbawala system makes packet routing thinkable. Neighborhoods make network segments thinkable. These aren’t simplifications — they’re translations between domains.
Interactivity — Let people manipulate the system and observe consequences. A static diagram of DNS resolution is information. An interactive simulator where you type a domain and watch resolution unfold is understanding.
Narrative — Give the system characters and stakes. A firewall described in a manual is a configuration. A firewall characterized as a guard with rules and judgment calls is a concept you can reason about in new situations.
The Work
- ServerBound makes cybersecurity visible through spatial exploration
- DataFolks makes data infrastructure visible through Indian metaphors
- The lab experiments make network concepts visible through interaction
Each uses a different combination of the three tools. All share the same goal: take something invisible and make it legible without betraying its complexity.
This node is the root of the garden’s philosophy. Most other nodes connect back here eventually.