Marissa Mayer on Quick Response Time

Google's Marissa Mayer told an audience at a Web 2.0 conference last week that quick response times are a critical - possibly the most important - contributor to usability. Response time is the amount of time it takes for a product to respond (provide useful results or feedback) to user requests. Slow response times lead to user frustration and less usage of your product.

For example:

In a survey on search, Google asked people how many results they would want by default; they responded that more is better, Mayer said. So the company conducted an experiment, providing some searchers with 30 default results. But it took, on average, a half-second longer to get those results than when the default was 10 results, she said. Out of frustration, people conducted fewer searches.

"This indicated extreme unhappiness," Mayer said. "It was clear that we weren't going to make this change."

A half-second increase in response time resulted in a large increase in frustration and consequent reduction in product usage.

The anecdote also supports the notion that giving customers what they say they want is not always a good idea. Sometimes, you can't know what people want until you observe what they actually do, and what they like, in a given situation.

Comments

Dancer Test

Are you left-brained or right-brained? Supposedly, your brain lateralization determines how you view this animation. Some people see her rotating clockwise. Others see her rotating counter-clockwise. Some see her unpredictably changing the direction of her rotation. Supposedly, people who see clockwise rotation are right brained. People who see counter-clockwise rotation are left brained. I originally came across this animation here .

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

Cauvin

Search This Blog