Designing for the eight-hundredth hour
Most interface advice optimises for the first five minutes. Here is what changes when your users live in the product all day.
There is a whole genre of design advice written for the first-run experience: reduce cognitive load, add whitespace, guide the user with a single clear call to action. It is good advice for a landing page and quietly terrible advice for software people use professionally, eight hours a day, for years.
Novices and experts want opposite things
A novice wants the interface to explain itself. An expert wants it to get out of the way. Confirmation dialogs, progressive disclosure and generous spacing all help the first hour and tax every hour after it. If your product is a tool rather than a destination, the eight-hundredth hour is the one that decides whether people stay.
Optimising for the first five minutes at the expense of the next five years is the most common mistake in professional software design.
Four things we do differently
- Undo instead of confirm. Reversible actions should never ask permission.
- Density as a feature. Give experts more per screen, and make it a setting rather than a fight.
- Keyboard parity. Every frequent action reachable without the mouse, discoverable through a command palette.
- Stable geometry. Do not move controls between releases; muscle memory is a real accessibility feature.
None of this means abandoning newcomers. It means treating onboarding as a separate, temporary layer over a dense product, rather than flattening the product until it feels like onboarding forever.
How to tell which one you are building
Ask how often your median active user opens the product. Weekly or less, design for recall. Daily or more, design for speed. Most teams know the answer and design for the other one anyway, because the first five minutes are what gets demoed.