Think about an experienced driver on a familiar road. She does not consciously operate the pedals or the steering wheel. She decides to turn, and the car turns. Her attention is on the road, the traffic, the conversation with the passenger, not on the machine wrapped around her.
This is not carelessness. It is what skilled tool use looks like. The tool has stopped being an object of attention and has become an extension of intention.
I have spent most of my working life around tools, first as an architect, then as a founder building software. The question that follows me from one field to the other is simple: why do physical tools disappear so readily, while software almost never does?
Thinking through a tool, not about it
The philosopher Andy Clark gave this phenomenon a name. In his work on extended cognition, he describes transparent technologies: tools that become so integrated into our cognitive processes that we no longer consciously attend to them. We stop thinking about the tool and start thinking through it, directly engaging the world on the other side.
Clark's larger claim, made in a well-known 1998 paper with David Chalmers, is that the mind does not stop at the skull. When an external tool plays the right kind of role in our thinking, reliably, fluently, without constant conscious supervision, it functions as part of the cognitive system itself (Clark and Chalmers, 1998). In his later book Supersizing the Mind, Clark (2008) develops the idea at length: tools that are integrated deeply enough are not aids to thinking, they are part of it.
He goes further. Clark points to brain imaging research suggesting that well-practiced tools can be represented within our body schema, the brain's running model of what counts as "self." On this view, the driver's sense of her own boundaries genuinely extends to the edges of the car. The tool is not just used by the body. For practical purposes, it is temporarily part of it.
Readiness-to-hand
Clark is drawing on an older idea. In Being and Time, Heidegger observed that tools in skilled use withdraw from our awareness. His example was the carpenter's hammer. While the hammering goes well, the carpenter does not experience the hammer as an object with properties. He experiences the nail, the wood, the work. Heidegger called this mode of being "ready-to-hand."
The hammer only becomes an object again when something goes wrong. It slips, or the handle cracks, and suddenly there it is: a thing in your hand, demanding attention, standing between you and the work. For Heidegger, a tool becomes visible precisely at the moment it fails.
The example philosophers in this tradition keep returning to is the blind person's cane. With practice, the cane is no longer experienced as an object being held. It becomes the medium of perception itself. The person does not feel pressure in the palm and infer a curb. They feel the curb, at the tip of the cane. Perception has moved out along the tool.
That, to me, is the gold standard for any technology: not that it is easy to use, but that in use it stops being experienced at all.
Software as the perpetually broken hammer
Held to that standard, most software is a hammer that never stops slipping.
Interfaces announce themselves constantly. Notifications interrupt. Windows demand arranging. Files hide inside hierarchies that must be reasoned about rather than simply seen. Every switch between applications is a small failure event, a moment when the tool becomes the object of attention and the actual work recedes.
There is also a quieter cost, which I think of as translation. Between the intention "I want that file" and the outcome sit many small abstract steps: recall the name, guess the folder, open the file picker, scroll, search again. None of these steps is hard. But each one forces you to think about the system instead of through it. In Heidegger's terms, our software spends most of its life present-at-hand, an object to be operated, and only rarely achieves readiness-to-hand.
What a transparent interface would mean
So what would it take for an interface to disappear the way a cane does?
I have a personal stake in this question. For years I have been building FileMap, a desktop tool that lays your entire file system out on one zoomable spatial canvas instead of nested folder lists. I mention it not to sell it but because it is the laboratory where I test these ideas, and it keeps me honest about how hard transparency is to achieve.
From Clark and Heidegger, I take four working criteria.
First, direct manipulation. You should act on your material through intuitive spatial movements, the way you reach for a physical object, rather than through abstract commands addressed to the system.
Second, reduced translation. The visual environment should map onto the real underlying structure of your work, so that the gap between "I want that" and having it is as short as possible.
Third, embodied interaction. We evolved to navigate physical space. An interface that borrows that capacity, with places, neighborhoods, and landmarks, asks less of the mind than one built from lists and labels.
Fourth, context preservation. In the physical world you can focus on one object without losing your sense of where you are. An interface should allow the same: zoom in on one thing while the surroundings remain, felt at the edges.
A spatial workspace: research, sketches, projects, and files arranged as neighborhoods on one zoomable canvas.
The test of success is a change in inner speech. A user of a transparent interface would stop thinking "I am using this tool to find a file" and simply think "where is that file?", the way you find your keys at home without consciously operating your house. At that point the organization of your digital material has become part of your spatial memory, not a separate system to be managed.
A note on state-dependent memory
There is a second, less obvious reason to want interfaces that behave like stable places.
Most people know the experience of failing to remember something at your desk, walking back into the room where you first learned it, and having the memory surface on its own. Psychologists call this state-dependent memory: what we learn gets encoded together with cues from the state we learned it in, including the physical environment, its sounds, even our mood at the time. Return to the state, and the cues help pull the memory back.
My working assumption is that this applies to digital environments too. An interface that looks the same every time you open it, where your project lives in the same visual place and your materials stay where you left them, gives memory a stable context to bind to. A tool that rearranges itself, or scatters your work across windows that exist only until closed, offers no such anchor.
This is, I suspect, the same reason so much productivity advice recommends dedicated physical spaces for specific activities. The room becomes part of the remembering. I see no reason a digital room could not do the same.
Beyond one mind
Everything so far is about a single mind and its tools. But the idea has a collective edge.
Researchers in distributed cognition have argued that shared visual spaces give groups common ground that sequential media like text and speech struggle to provide (Hollan, Hutchins, and Kirsh, 2000). When several people can navigate and rearrange the same information landscape, the space itself begins to hold their shared understanding.
I suspect transparency scales the same way. A tool that disappears for one person extends a mind. A shared space that disappears for a team might do something more interesting: it might let a group think in one place.
The disappearing screen
None of this is an argument that tools do not matter. It is the opposite. The cane matters enormously to the person using it. It matters so much that it has been absorbed, promoted from object to organ.
Heidegger's hammer disappears into the carpenter's work. The cane disappears into the street. What I keep wondering is what it would take for a screen to disappear into a thought.