Quotes About User-centric

Services should revolve around those who use them and be fit for the future, not stuck in the past.

A lot of our most successful ideas over the years came from the bottom up, by really understanding user needs.

When The Daily Muse initially wanted to launch a job board, our first ideas were insanely (and needlessly) complex. We wanted to integrate with social networks, gather rich personal data to build predictive algorithms, and put together numerous cool visualization tools before launching out to the world. We were just sure users would love it!

You don't compete against products and services in your category: you compete against anything that gets the job done from the user's point of view.

Product successes and failures have shown repeatedly that users don't care that much about features. Users only care about achieving their goals.

Design must reflect the practical and aesthetic in business but above all... good design must primarily serve people.

Good design isn't about making decisions for your users, it's about making those decisions irrelevant.

Design should not dominate things, should not dominate people. It should help people. That's its role.

The easiest, most straightforward way to create a great product or service is to make something you want to use.

The easiest, most straightforward way to create a great product or service is to make something you want to use. That lets you design what you know—and you'll figure out immediately whether or not what you're making is any good.

It all seems important. But then we step back and think about the specific people who will use our product, and what they'll need to accomplish to be successful. We distill that into a sentence or two. Then we carve away everything we don't need, and we're shocked at how small our viable solution really is. It's magic

The easiest programs to use are those which demand the least new learning from the user

created specifically to separate the problem-solving tasks requiring access to a manufacturer's sticky solution information from those requiring access to users' sticky need information. The same basic principle can be illustrated in a less technical context: food design. In this field, manufacturer-based designers have traditionally undertaken the entire job of developing a novel food, and so they have freely blended need-specific design into any or all of the

The point is that I don't design stuff for myself. I'm a toolmaker. I design things that other people want to use.

The key to solving the problem is interaction design before programming.

Design Is a Big Word

We must design for the way people behave, not for how we would wish them to behave.

Our job as the game creators or developers - the programmers, artists, and whatnot - is that we have to kind of put ourselves in the user's shoes. We try to see what they're seeing, and then make it, and support what we think they might think.

The point is that I don't design stuff for myself. I'm a toolmaker. I design things that other people want to use.

Great software today is often preferable to perfect software tomorrow. If you give your users something to play with early, their feedback will often lead you to a better eventual solution

You've got to start with the customer experience and work backwards to the technology. You can't start with the technology and try to figure out where you're going to sell it.

Instead of trying to use your technology and expertise to make a better product for your users' standard behavior, experiment with inviting the users to change their behavior to make the product work dramatically better.

It's not enough to have a hacker culture anymore. You have to have a design culture, too.

We want the next generation of products being innovated to reflect our users. And when women are not part of the equation, we won't have products that reflect the unique needs and opportunities across our society.