Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Design This

Freshness Warning
This article is over 18 years old. It's possible that the information you read below isn't current.

Business 2.0’s "Cool Design Won’t Save a Dud Product" is a study of how products that win industrial design awards can still flop in the marketplace. Just because something looks good doesn’t mean it’s useful.

The principles discussed in this article apply to software design, too. You can’t create an unusable piece of software, put an attractive UI on it, and expect it to do well.

Steven Garrity
March 12, 2002 8:31 PM

Good link. 'Design' is too often limited to the visual realm. If a product ends up being a dud, it's probably wasn't 'designed' well in the first place. When I hear people say that something was well designed in concept, but just didn't work in the real world - I always go on a rant: No, it WAS NOT well designed if it didn't work. Maybe it was visually stylish, but design (even the more specific, graphic design), means more than that. Was a product well designed but cost too much to product? Lame - good designers (in whatever the field may be) would understand the importance of factors like production cost. See a good article on the the difference between style and design at Alistapart:

Adam Kalsey
March 13, 2002 9:41 AM

The other problem occurs when design is an afterthought. It usually ends up like putting makeup on a pig. The pretty surface layer doesn't make the whole package any more attractive.

Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.


Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Recently Written

A framework for onboarding new employees (May 15)
There’s no single good way to onboard an employee that works for every role. Here's a framework for creating a process that you can adapt to each situation.
TV hosts as a guide for software managers (May 10)
Software managers can learn a lot from journalists or late night TV hosts and how they interview people.
The Improvement Flywheel (Apr 29)
An incredible flywheel for the improvement of a development team. Fix a few things, and everything starts getting better.
Managers and technical ability (Dec 26)
In technical fields, the closer you are to the actual work being done, the closer your skills need to resemble those of the people doing the work.
Dysfunctions of output-oriented software teams (Sep 17)
Whatever you call it, the symptom is that you're measuring your progress by how much you build and deliver instead of measuring success by the amount of customer value you create.
Evaluative and generative product development (Aug 30)
Customers never even talk to the companies that don't fit their needs at all. If the only product ideas you're considering are those that meet the needs of your current customers, then you're only going to find new customers that look exactly like your current customers.
Product Manager Career Ladder (Aug 19)
What are the steps along the product management career path?
Building the Customer-Informed Product (Aug 15)
Strong products aren't composed of a list of features dictated by customers. They are guided by strong visions, and the execution of that vision is the primary focus of product development.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2020 Adam Kalsey.