The case for slow tools

There’s a particular kind of software I keep coming back to. It doesn’t have a loading spinner. It doesn’t have a tour. It opens to a blinking cursor or a blank page or a single text field, and it asks you to start.

What gets in the way

Most products spend their first impression trying to convince you of something — that they’re powerful, that they’re easy, that they’re for someone like you. The tools I trust skip that. They assume you have a reason to be there. They don’t perform.

This isn’t austerity. It’s confidence. Confidence that the work itself is interesting enough to compete with whatever else you might be doing on a screen.

What it costs

The honest part: building software like this is expensive. Not in code — the code is usually smaller. In meetings. Someone has to say no, every week, to features that would absolutely improve the product on paper and absolutely degrade it in spirit.

The hardest part of design isn’t deciding what to add. It’s defending what you’ve decided to leave out.

I’ve watched several products lose this thread over a few releases. The team that ships the quiet version year one is not necessarily the team that ships year three. The discipline is a continuous expense, not a one-time decision.

A short reading list

A few things I keep recommending:

• The Design of Everyday Things — Don Norman, 1988
• Tools for Conviviality — Ivan Illich, 1973
• Anything by Bret Victor, but especially Magic Ink

Tools that respect your attention are still rare. Worth noticing when you find one. Worth noticing how you found it, too — usually word of mouth, never an ad.