March 10, 2026
When to stop iterating
Three practical signals to close a design without the lingering feeling that something is missing.
The end of a design rarely announces itself. It arrives dressed as “one more improvement”, “let’s try another variant”, “we can polish this a bit”. Knowing how to close is part of the craft.
Signal 1: changes make the whole worse
When comparative tests start coming back tied or worse, the design is close to its local ceiling. Pushing past that is taste disguised as process.
Signal 2: the team can defend it without you
If the client or product owners can explain the decision without your help, the system has consolidated. Another review will only generate new doubts.
Signal 3: your improvement list is the next-version list
When what’s left on the table doesn’t require re-thinking anything, you’re not iterating: you’re maintaining. Document and ship.
What helps
Define three things upfront that need to be true to call the work done. Not “everything perfect”, but three clear conditions. That list is the only thing that protects a design from dying of polish.