We've Got the Wrong Idea About UX

People were creating awesome stuff way before we online product people tried defining this as "user experience design." Just look back at Henry Dreyfuss' Bell Telephone from the 1940s or jump ahead to OXO's angled measuring cup today. They did it by sharing a vision relentlessly centered on providing value to the people they'd serve. They paid close attention to the details both their customers outside their company and their employees within it felt. And they did it by Designing their goods and services with a capital "D."

But we lost our way in software. We're trying to wander back under the banner of "user experience," but that's bound to let us down. It ignores our rich history and blinds us from the real effort we need: getting everybody on our team designing for people.

Chris' post yesterday reminded me that Bill Buxton argues that sketching, both in concept and in practice, is absolutely fundamental to entire organizations that design great things for people. A critical insight most miss is that design cannot be for designers alone, it's the responsibility of your entire team.

If you think a designer or a UX expert will solve all your problems, you're screwed. What "UX" has to imply is a fundamental shift in your organization's thinking and practice. It starts with you and your passion for design, but then has to extend to the others on your team through simple, approachable design techniques like sketching. This will empower them to get the job done.

Getting this right has been called design management since the 1960s, not user experience.

Do you need Design experts? Yes, of course. You need whip smart specialists in teams throughout your organization, but these people need a shared vision and a common language. Put your designers in their own "UX Design" silo and you'll frustrate the hell out of them and end up feeling your organization somehow adds up to less than the sum of its parts. The differences between organizations that figure this out and those that don't are stark.

How does a site like Quora succeed at so many details that their content--smart questions with answers by experts--and interactions seem so much richer and more valuable than Yahoo's? This comes down to a strong shared vision and cross-disciplinary collaboration by Quora's team, whereas Yahoo's team suffered from slower, less effective communication and experienced less ownership over a collective vision.

6 comments

Brian Armstrong says

Great point - I've been sketching more stuff lately and it helps me get out of the engineer mindset and be more creative.

Quora seems like a bad example here (their design feels overwhelming and doesn't have enough whitespace I don't think), but your main point is spot on.


Liza says

All that UI/UX designers staff is like another fashion trend that is highly promoted today. It is absolutely Ok with us, designers, because at last we have an opportunity to show that people need experience and strong knowledge for making our job and that we earn wages not because we are so cute.

Designers do always have the knowledge of synthesis, and it's a lot - to see with other people eyes and turn their ideas into a product. I personally can not manage all that code stuff because I can't split things into needed pieces, and good developers have to do that to construct proper product. But I can gather pieces as a whole, that drives me a lot.


Liza says

BTW Zurb is a great example of design management in business and I've been following you for a couple years already, because your business model is extremely interesting.


Ryan Wilke says

Excellent post, Jeremy. The title drew my attention on Twitter, and I knew that one was going to be a good read.

All great points — spot on. Keep 'em coming ;)


Jeremy (ZURB) says

@Brian, with Quora I might agree about some of their visual design details, but you've got to admit their interaction design is spot on--especially getting you started.

@Liza, absolutely (and thanks for the kind words). Designers have an awesome opportunity to help entire teams do this better. But designers should beware of accepting the UX label without the responsibility of getting design leadership and management in place throughout your organization.