It is easy to treat the interface as the whole job, because it is the part everyone can see and have an opinion about. But the interface is a surface. What people actually buy is the outcome underneath it — the thing that gets done, the time that gets saved, the worry that goes away.
what the screen hides
Behind every clean screen there is a decision about scope, a data model, an error state nobody wanted to design and a support team that has to explain it. A beautiful layout on top of a confused model is still a confused product.
designing the parts nobody screenshots
- Empty states, which is where most people start.
- Error states, which is where trust is won or lost.
- The second visit, which is the one that decides retention.
These are rarely in the portfolio shot, and they are usually where the real design work sits. The interface should be the last thing you resolve, not the first.

