DZone
Agile Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > How Do You Decide When a Design is Finished?

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.

Kim Goulbourne user avatar by
Kim Goulbourne
·
Feb. 13, 17 · Agile Zone · Opinion
Like (0)
Save
Tweet
4.62K Views

Join the DZone community and get the full member experience.

Join For Free

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.

Design

Published at DZone with permission of Kim Goulbourne. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • What Emerging Technologies Make Data Centers More Energy Efficient?
  • Applying Domain-Driven Design Principles to Microservice Architectures
  • API Security Weekly: Issue 165
  • Writing Beautiful, Optimized, and Better .NET Code With NDepend Static Analysis

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo