i. The afternoon I stopped a redesign.
A Wednesday in late February. I was eleven days into a brief that had asked, more or less honestly, for a faster redesign of a checkout flow. The team had timed it to a quarter-end. There was a slide deck with bright arrows. There was a metric that had quietly stopped moving, which is usually the real reason anyone is paying for a redesign at all.
By 14:00 we had a working prototype, two reasonable alternatives, and the beginning of a research plan. By 15:30 I was sure we were solving the wrong problem.
I stopped the meeting. Not dramatically — there is almost never a good reason for drama in a working session — but with the small, definite, slightly awkward sentence: I think we need to put this down for two weeks.
I think we need to put this down for two weeks.
— what to say when everyone is moving fast in the wrong direction
The room did not love this. A redesign on hold is a redesign that, in the head of the person paying for it, is broken. But the alternative — shipping a faster version of the wrong thing in three weeks — was worse than the alternative of looking like I was stalling. Or so I told myself, at the time, in the quiet way one tells oneself things one is not yet sure about.
Three weeks later, the right answer arrived. Not from any of us, exactly. From a customer-support transcript that someone on the team had read twice and not flagged, because the customer had been polite about something that, looked at in the right light, was the entire problem. We did the redesign. It took four days. It moved the metric. ↘ this is the part of the story I would have left out, five years ago
ii. What "fast" was actually doing.
Speed is rarely the enemy. Most teams I work with are not, in fact, slow. They are, on the contrary, alarmingly productive. They ship. They iterate. They run experiments. They produce, in any given quarter, more design artifacts than most studios in 2008 would have produced in a year.
And yet, often, the work does not compound.
This is the sentence I keep coming back to. The team ships, but the work does not compound. It is a description of a specific failure mode that I see, with some variations, in maybe seven of every ten engagements I take. The team is moving. The work is not.
When I ask, gently, what is going on — and gently is the only register in which this question gets a useful answer — the response is usually some variation of: we are trying to get a result before the next review. Which is fair. Reviews are real. Quarter-ends are real. The pressure to show motion is real.
But the result of moving fast in this register is not, usually, a faster answer. It is a faster version of not knowing what the question is. And not knowing what the question is, at speed, looks indistinguishable from progress for about three sprints. After which it looks, suddenly and all at once, like the metric has quietly stopped moving.
iii. The shape of slow clarity.
Slow clarity, in the sense I mean it, is not the absence of speed. It is the presence of a different rhythm. There are moments in any engagement where the right move is fast — a prototype, a test, a small decisive call. And there are moments where the right move is to slow down for half a day and let the question reshape itself in your hands.
Knowing which is which is most of the job.
I do not have a clean test for this. I have, instead, a handful of small signs that I have learned to take seriously. Most of them are bodily — a feeling in the room, the way someone phrases a question, the silence after a decision is made. When the work is compounding, these signs feel calm. When it is not, they feel reactive.
The instinct, when things feel reactive, is to push harder. To run another experiment. To schedule another review. The discipline — and it is a discipline — is to do the opposite. To put it down, for an afternoon, or a week, or two. And to come back to the thing with the part of your mind that is not trying to ship.
When the work is compounding, the small signs feel calm. When it is not, they feel reactive.
iv. Three practices, named small.
I do not believe in frameworks the way I used to. Judgment over process, as the last essay had it. But there are three small practices I run, quietly, in every engagement, and which I would offer as the load-bearing pieces of slow clarity:
One. A standing rule that no design decision gets made on the same day it is first proposed. Not because the decision will be wrong — it will sometimes be right on the first day — but because the practice of waiting one night makes the dozen decisions that are wrong much easier to catch.
Two. A weekly fifteen-minute review where I read everything I produced in the last seven days the way I would read someone else's work. Not to critique it. Just to notice what it says. About a third of the time, the work tells me something I did not consciously know.
Three. A small ritual of writing one sentence at the end of every working session that names what I now think the question is. Across an engagement, those sentences make a small, honest history of how the thinking has moved. They are also, on the bad days, embarrassing to read. Which is the point.
v. Closing — and what is not in here.
What is not in here, and you may have noticed: any case for slowness for its own sake. I have very little patience for the strain of design writing that romanticises slowness as a virtue. The point is not slow. The point is right. Slow is what right tends to look like, from the outside, while it is still becoming itself.
If a sentence here helped you think more clearly about something on your week, that is enough. If none did, the writing was at least short.
⁂