Principles for When to Stop Designing
Knowing when to stop is as important as knowing where to start. These principles help designers recognise when a decision has been made and further work risks serving the designer rather than the user. Each principle marks a natural stopping point, where more iteration adds noise rather than clarity.
-
Stop when the next change is for you, not the user
If the improvement satisfies taste or the need for creativity rather than problem solving, it’s no longer meaningful.
-
Stop when the problem isn't proven
If you can’t point to evidence, you’re making an assumption.
-
Stop when the question shifts from why to how
Once the focus shifts to execution, the design decision has already been made.
-
Stop when you're redesigning not refining
If each iteration opens new questions rather than closes them, you’ve started over without admitting it.
-
Stop when the design can't be tested in its current form
If it can’t be put in front of users, it’s not ready for more work.
-
Stop when you're designing for edge cases
When rare scenarios start driving decisions, the centre hasn’t been resolved yet.
-
Stop to allow time to learn
The gap between designing and releasing is where you find out if you were right.