Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Design This

Freshness Warning
This blog post is over 22 years old. It's possible that the information you read below isn't current and the links no longer work.

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.

This discussion has been closed.

Recently Written

Great prodct managers own the outcomes (May 14)
Being a product manager means never having to say, "that's not my job."
Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2024 Adam Kalsey.