It Isn’t About Ugly Design,
It’s About Functional Design

There’s been talk all over the interweb about whether ugly design is successful design, generally discussed in the context of sites like craigslist.

This discussion has for the most part been misguided though. When I’m talking about design, I find it helpful to break the discussion into functional, process and aesthetic categories and I deal with them in that order.

  1. What’s the functionality I’m trying to offer?
  2. What process is needed in order to allow the user to use that functionality?
  3. Lastly, what aesthetic choices would best serve both function and process?

You can answer questions of functionality and process and never make any choices on question three and still have a phenomenally successful project, but if you have the time and awareness for smart aesthetic choices, your customers will be better served.

It isn’t about ugly design. It’s about functional design and functional design doesn’t have to be ugly. In fact, when most people are talking about ugly design, they’re really talking about spare design (i.e. craigslist.) Craigslist could be prettier and just as useful and even more usable, but given Craigslist’s large user base, design changes at this point in it’s life should be made with great care.

I’m a big fan of a healthy aesthetic sensibility when it comes to creating software, but lead with function, understand completion and then think about aesthetic design as an aide to the first two.