FIELD NOTE / 04 · 5 MIN READ

The interface should disappear

Interface quality is not measured by how much UI is visible. It is measured by how little friction remains between intent and outcome.

Every interruption has a cost.

Opening a tool, finding the right record, reconstructing context, and choosing from a menu all consume attention. Each step may look minor in isolation while the complete workflow feels heavy.

AI can remove that weight when it carries context forward. It can also add more of it when every capability arrives as a new panel, command, or prompt box.

The interface is finished when the work, not the software, holds attention.

Good defaults carry intent.

The interface should remember the routine parts: which account is active, what evidence matters, how results are formatted, and where the completed work belongs. People should spend their attention on exceptions and judgment.

This is not about hiding control. It is about placing control where it has consequence. A reversible default is often more useful than a wall of configuration.

Measure the distance to done.

Count the transitions between a person recognizing a need and the work reaching a usable state. Then remove the steps that exist because the tools do not share context.

A disappearing interface is not empty. It is precise. It appears at the decision, explains the stakes, and gets out of the way when the person has what they need.

Next field noteAI should inherit the workflow