Over a million developers have joined DZone.

How Do You Decide When a Design is Finished?

DZone's Guide to

How Do You Decide When a Design is Finished?

There's a point of diminishing returns when software design works, but it can be hard to recognize - here's how I do it.

· Agile Zone ·
Free Resource

Whatever new awaits you, begin it here. In an entirely reimagined Jira. 

When dealing with code, it’s usually apparent when it’s time to move on to the next feature or wrap up the project. Once the code works and it’s written well you can typically call it a day.

In design, however, drawing that line can be tricky and has the tendency to be very subjective. While others may look at a design and think it’s up to par, sometimes there’s an uneasy feeling that it’s not quite done yet. It’s a feeling that can’t necessarily be put into words, and so instead we keep pushing pixels until it “feels right.” But what makes it feel right in the first place? I chalk it up to a few things that run through my mind subconsciously.

This is challenging because it can easily lead to design overkill. With so many trends and patterns in web design, it’s easy to fall into the trap of using them on every project. While reusing some patterns allows for a more intuitive experience, this doesn’t allow for innovation. My first instinct is thus to always explore options that either put a new spin on a current trend or attempt something completely random and potentially terrible instead. The idea here is to take enough risks until there comes a point where you’ve tried different things and are now satisfied with the outcome.

It’s easy to design something, get excited about it, and think there’s nothing to improve. Design reviews are always nerve-racking for me because while I may think I’ve exhausted all possibilities, occasionally it turns out that I haven’t. On the flip side, this is the very reason getting feedback is so valuable because a new set of eyes and different perspectives are always beneficial for any project and growth as a designer.

With any design work, if you look at it too long you won’t notice the pitfalls. Try to step away from your work periodically. I may step away to take a walk or just put the project on pause for a whole day. Not only does it help to reset my thinking, but I always tend to gain new inspiration.

The awesome thing about deadlines is that it forces you to make better decisions faster because there simply isn’t enough time to thoroughly explore everything. If the project is on schedule, however, then I’ll definitely take the time to massage the design in areas that are most important - though this also serves as a reality check for when it's almost time to move on.

In hindsight, this and the first point I mentioned are probably the ones I’ve noticed the most. If I’m not overly excited about the design then I’m probably going to keep meddling with it. The excitement is directly tied to pride. If I’m not proud of my work then I’ll never fully feel ready to move on.

Being able to identify why you’re not ready to move on from a design is helpful in order to comfortably move forward or make the necessary adjustments.

New roadmaps, more flexible boards, and dozens of new integrations. And that's just the beginning.  

design ,agile ,web design

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}