Design Is Wrong
This is a real conversation I had just recently:
“We really need to improve the design of this product.”
“No. We don’t have time to work on the design. Let’s just make it usable.”
I have this conversation a lot. I say design and they hear fancy icons. Most software developers associate design with prettiness rather than usability. That leads me to a simple conclusion: design is wrong. The idea is good, but the word isn’t saying what I want it to say. I’ve started a search to find a better word for good design.
User experience is an academic term. It is accurate, but it doesn’t give people the feeling that it should be part of the process from the beginning.
Usability also feels like it comes last. “We’ll do the architecture and then spend a little time on the usability.”
Improve the interface also feels like just a part of the process; the icing on the cake.
So I’m looking for a new term. Something that conveys the need to prioritize the human who will use the software and how they want to use it. It needs to show people that design is part of the process from the beginning and design can drive technical specifications. I’m probably preaching to the choir by writing here.
How do you handle this issue? What terms do you use to make people who don’t think much about design start thinking about it? Which terms do you use to convey a feeling that design is more than pretty icons?