At the moment the design world is obsessed with how fast things can be built. The conversations are about “I shipped a whole product in 2 hours” or “I built a startup in a weekend.”

New tools are creating faster workflows, quicker iterations, and the ability to produce more than ever before. In many ways, our new tools deliver and extend our capabilities as designers. But as always when the focus of conversation shifts to being about tools rather than outcomes, something has been lost in the process.

In music, knowing when to stop is just as important as knowing what to play. The pause gives structure to the sound. Without it, everything becomes noise.

As Mile Davis said “It’s not the notes you play, it’s the notes you don’t play.”

Tools will continuously improve and develop but they’re focused on delivery, shipping, iterations, not pausing or reflection.

These principles for knowing when to stop are not about slowing down for the sake of it. They’re about recognising when a decision has already been made, and when further work stops serving the user and starts serving the designer.

And ultimately understanding why we are building something rather than how quickly we are building something.

1. Stop when the next change is for you, not the user

Not every improvement is meaningful.

When changes are driven by taste, preference, or the desire to explore, are they solving a design problem? At this point, design becomes self-expression rather than problem solving. It’s art, not design.

This is often the quiet moment where good design work starts to drift.

2. Stop when the problem isn’t proven

Design without evidence is speculation.

Is the problem even real? If you can’t clearly point to a problem through research, behaviour, or observable friction you’re no longer solving something real. You’re designing in anticipation of a need that may not exist.

This doesn’t mean certainty is required, but it does mean intent should be grounded.

3. Stop when the question shifts from “why?” to “how?”

The moment the conversation becomes about execution, the decision is already behind you.

“How should this work?”, is not a design question. It’s a delivery question. The risk is that designers continue to iterate as if the core problem is still open, when in reality it has already been resolved.

Continuing to design at this point often leads to unnecessary variation rather than better outcomes.

4. Stop when you’re redesigning not refining

Refinement reduces uncertainty. Redesign introduces it.

Often we’re asked to help with a “redesign” but often we’re just building the same thing but different.

If each iteration creates new questions instead of resolving existing ones, the work is no longer converging. It’s diverging again, often without intention.

This is one of the clearest signals that we’ve crossed from improvement into reinvention.

5. Stop when the design can’t be tested in its current form

Test a design as early and in as fit a state as possible for who you’re testing it with. If it can’t be shown, used, or experienced by someone else, further iteration is disconnected from reality. The only meaningful next step is getting some feedback, not additional polish. The polish can go on forever.

Design only improves through contact with use.

6. Stop when you’re designing for edge cases

Edge cases are important but they shouldn’t lead. Discussions around edge cases can dominate meetings.

When rare scenarios begin to dictate core decisions, it’s often a sign that the central use case hasn’t been fully resolved. Designing for the margins before stabilising the centre creates fragile solutions and is often a very slow and painful journey.

Solve the common case well first. The edges can follow.

7. Stop to allow time to learn

Design doesn’t end when you stop working on it.

The most valuable insights come after pausing for feedback, testing or release, when real behaviour replaces assumptions. Without this pause, there’s no opportunity to understand whether you were close to getting things right.

Stopping isn’t the end of design. It’s a pause that makes learning possible.

You don’t need to stop for long. Stopping doesn’t slow things down. But knowing when to stop is what turns design from activity into decision-making.

I write occasionally about how principles function in real organisations, where they succeed, where they fail, and how they evolve over time.

If that’s useful to you, you can subscribe below.