Quiet as a Strategy
On the practice of doing less, and the kind of attention it asks of the people who try it.
There's a particular kind of work that announces itself slowly. It doesn't show up in dashboards. It doesn't photograph well. It tends to be the work that, years later, you can't remember whether you did or whether it had always been there.
I've come to think of this work as quiet, and to recognise that quiet, far from being a default state, is one of the harder things to practise in 2026.
Three observations
First, that the loudest version of almost any discipline tends to be the most lucrative one in the short term and the most fragile one in the long term. Loudness compounds in the wrong direction.
Second, that the people doing the most interesting work, in markets, in design, in software, in horology, are almost always the people who have arranged their lives so that they don’t need to be loud to eat.
Third, that quiet isn't the absence of confidence. It's its mature form.
A small practice
I keep a private rule, written above my desk. Ship only what survives the second read.
It isn't a productivity hack. It's closer to a measurement device. When something fails the second read, I've learnt to treat that failure as more useful than the original draft. The friction is the information.
The strategy, in the end, is small. Make less. Read more. Edit slowly. Refuse most of what's offered. Pay close attention to the few things that remain.