User Testing Quotes

You may be trying to drive in a particular direction that people don't necessarily understand at first. In our case, we knew the users we had in mind for this product. So in the early days, we looked at our customers, really just testers at that point, and we paid extra attention to the teams we knew should be using Slack successfully.

It's really hard to design products by focus groups. A lot of times, people don't know what they want until you show it to them.

The utmost thing is the user experience, to have the most useful experience.

My sweet spot is figuring out how to make a product that people love and how to refine it to make them love it more. All the rest is business noise.

We do not focus test our games and never had. People ask why we don't, and I say, 'I have so many opinions in this studio, I don't need anymore!' We really debate everything - and it's a good debate. That's why the games turn out well: it's not me - it's not this guy - it's the collective. Together, we figure out what we want.

User-centered design means understanding what your users need, how they think, and how they behave - and incorporating that understanding into every aspect of your process.

You can't start a product simply by building it. You have to know why you're building it, and you might go down the wrong rabbit hole, waste time, and confuse things. Spending long afternoons with a sketchbook or talking through your ideas with other people can save a year in software development later on.

Get your product into users' hands as quickly as possible and incorporate the crowd's feedback to iterate. Your customers will provide the data you need to chart the best course for your company and bury any competitor that goes it alone.

With 100 million people, somebody is using your product in some interesting way. If you change it... you're going to break some use cases.

It's incredibly important to be - once you do have a product - acutely observational about the trends.

I describe the design process as like the tip of the iceberg. What you don't see is the long haul: all the endless auditing and things like that.

You should always look for opportunities to test innovations on a subset of users if you can.

Betting all your funds on the belief that you know what consumers want and are willing to pay for is like jumping into a river to test its depth - you'll need a lot of luck to stay afloat. To have a truly successful product launch, the conversations with your customers must start long before you write your first line of code.

If you're going to build a lean enterprise, you can test and measure how often the company ships iterations, how often it fails, how often it is putting things in front of people that don't work.

From the very first inkling of a concept, founders need to gather a target group of five to ten potential users to begin the feedback loop. We all think we know how the market will react to new ideas, but actual users live with the pros and cons of the existing market conditions every day. They are the market experts.

If you're an entrepreneur and you're starting a company, I think the first thing you do is you go and talk to a bunch of people. But then the next thing you probably should do is figure out if there's a broader demand than just people you know. That's where I think SurveyMonkey is pretty valuable to people.

Building the right product requires systematically and relentlessly testing that vision to discover which elements of it are brilliant, and which are crazy.

User-centered design means working with your users all throughout the project.

In many cases, the user interface to a program is the most important part for a commercial company: whether the programs works correctly or not seems to be secondary.

To me, 'design thinking' is another way of saying empathize with the customer. It's consideration for the person you're designing for.

The most important thing in startups is getting a product to market, as imperfect as it may be, and then iterating on it and continually making it better. A first rev of a site that has a few typos may not be perfect, but it was the start of something that I deeply believed in.

One of the hard parts about building a service that you use yourself is that it's easy to forget what it was like the very first time someone signs up. Every once in a while, I'll create a brand new account and give it a try and see how hard it is to find things that I really love, see if I'm using it or thinking about it differently.

When talking to first-time entrepreneurs, I often ask them: 'How do you know that people want your product or service?' As you can expect, the answer is often that they don't yet, but will know once they launch. And they're right. That's why it's critical to launch as quickly as possible so you can get that feedback.

I mean, making simulations of what you're going to build is tremendously useful if you can get feedback from them that will tell you where you've gone wrong and what you can do about it.

There are major benefits to building a game once and improving it over a long period of time based on user feedback and behavior. It's kind of depressing to have to build a game once, take all the user feedback, and then spend the next 3 years building another game.