abstract object
The shape of a good tool
Good tools disappear. They shrink the distance between intent and outcome until the work feels like thinking out loud — and the interface recedes.
That’s a high bar, and most software misses it. Features accumulate; fluency doesn’t. The test we hold for our own work isn’t how much a tool can do, but how little a person has to think about the tool while doing it.
Fluency over features
A feature list answers “what can this do?” Fluency answers “what can I now do that I couldn’t before?” The second question is harder, and it’s the only one that matters to the person doing the work.
How we get there
We start from the task, not the toolbar. We watch where intent stalls, and we remove that distance — one honest decision at a time.