The quiet case for slower design

In 2022 we took on a project with a six-week timeline from brief to launch. The client was a Series B startup with a board presentation in seven weeks and a strong conviction that the brand could be done in parallel with everything else. We said yes.

The work was not bad. It was competent, considered, and delivered on time. It was also, in retrospect, exactly as good as six weeks of thinking could make it, and no better. Two years later the company has quietly rebranded.

We have thought about that project often.

Speed is a design decision

There is a version of the "move fast" argument that applies to certain kinds of design. Interface experiments, marketing variants, A/B tests — work that is cheap to change and benefits from market feedback. Speed is genuinely the right tool for that kind of problem.

Brand identity and foundational digital experience are not that kind of problem. These are decisions that will shape how a company is perceived for years. Changing them is expensive — not just financially, but in terms of the accumulated recognition that any consistent brand slowly builds. The cost of moving fast is paid later, and it is paid by the client.

What slowness actually means

Slower design is not the same as more meetings or longer presentations. It means protecting the time in a project when nothing visible is happening.

The most important work we do on any project is not the work that ends up on a slide. It is the thinking that happens in the gap between the first draft and the second one — the questions that surface overnight, the constraints that only become clear when you sit with something long enough to understand what is wrong with it.

That time cannot be compressed. You can run more concurrent workstreams, hire more people, use better tools — none of it substitutes for the simple elapsed time that allows a first idea to reveal its weaknesses.

The client's role

Some of the best decisions we have made on projects were made possible by clients who were willing to wait. Not passively — actively willing, in the sense of trusting that the silence had a purpose.

The Holt & Sons project ran eleven weeks against a brief that most studios would have turned around in four. The extra time was spent almost entirely on the question of tone — specifically, on how to carry the workshop's history without being nostalgic, and how to position handmade work at a price point that the internet tends to distrust. None of that thinking is visible in the final work, which is exactly as it should be. But it is present in every decision the final work contains.

A practical note

We build minimum timelines into every proposal now. Not to protect our own schedule — to protect the quality of the outcome. When a client pushes back, we explain what the time is for and what they lose without it. Most of the time, that is enough. When it is not, we sometimes decline the project. That is not a principled stance so much as a practical one: we have learned that rushed work reflects on us regardless of whose idea the deadline was.