Customers sometimes do not know what they want

Share Button
Image by Darren Hester via Flickr

The promise of co-creation is that getting customers involved in the innovation process, and letting them inform the design of new products, will mean that you develop a product that is better suited to their needs and will ultimately perform better in the market. Of course, it is not always this simple. Often customers don’t know what they want. They can’t necessarily articulate how they would design the ideal product, nor can they say what is wrong with the existing product. They may never have articulated what they like nor what they dislike, but this doesn’t mean that the product isn’t perfect.

Over the weekend, the New York Times looked at this very subject following revelations from ex-Google visual designer, Douglas Bowman. In an unusual move, Bowman explained on his blog the reason he had left Google. As the New York Times discussed, his description of the design process at Google raises a number of questions:

Can a company blunt its innovation edge if it listens to its customers too closely? Can its products become dull if they are tailored to match exactly what users say they want?

Bowman’s suggestion is that that answer to all of these questions is “yes”. That Google relies too much on data, as a proxy of customer input, and not enough on design skills alone. As the New York Times article report:

Mr. Bowman’s main complaint is that in Google’s engineering-driven culture, data trumps everything else. When he would come up with a design decision, no matter how minute, he was asked to back it up with data. Before he could decide whether a line on a Web page should be three, four or five pixels wide, for example, he had to put up test versions of all three pages on the Web. Different groups of users would see different versions, and their clicking behavior, or the amount of time they spent on a page, would help pick a winner.

This kind of user-input into the design process is what many think of when they think of working with their customers on new product development and design. They think of presenting a number of options to customers (or indeed to potential customers) and then asking them to evaluate each one and choose the one they prefer (or in this case to take their use of a particular design as a proxy for this choice). Of course, this is not necessarily the best way of co-creating with your customers.

Rather than asking people what they think about a particular set of designs they prefer (or which they use most), you can often get a more useful level of insight by engaging with them. Don’t ask them about solutions to a problem but observe what they discuss and say about the problems themselves.

Imagine you are a company designing kitchen equipment. You could involve your customers in the design and innovation process in one of three ways:

  1. Ask them what they want - ask what new equipment, tools or gadgets would make their life in the kitchen easier or allow them to do new things
  2. Ask them to choose between a set of prototypes - present a set of potential new products to them and ask them to choose which they want.
  3. Ask them to talk about what they do in the kitchen, what equipment they use and what problems they have

The last of these is most likely to produce the most insightful outcomes. Rather than asking people to get involved in the actual prototype products themselves, or to tell you what they want, get them involved further up the innovation funnel. Engage them and talk to them about what they use in the kitchen - what makes their lives easier, what would they like to be able to prepare and cook but can’t. Don’t talk to them about the equipment that, you hope, will solve their problems. Talk to them about their problems themselves.

By watching what people do you can then interpret this and begin a design process based on this information and this engagement. Then, rather than just presenting three options to people of potential new designs, you can approach them based on what they have discussed before: “there was a lot of discussion about x, here are some ways we think we could help with that. What do you think?”

This kind of engagement is where online communities really come to their fore. They let you engage your customer in a sustainable way. You can get to know them, their lives and the problems and challenges they face. It isn’t just a short-term process to “do some co-creation”, rather it is long-term engagement that fundamentally changes the way you innovate and develop new products.

Customers sometimes do not know what they want. It’s a fact. They do, however, know how they use what they have, the problems they face and the things they would like to be simplified. Understand what they do know rather than forcing themselves to make choices about things they don’t.

  • Design: it’s not all about you. (designmind.frogdesign.com)
  • Design Or Data? Ex-Googler Spills All After Landing At Twitter [Design] (gizmodo.com)
  • Google designer leaves, blaming data-centrism (news.cnet.com)
Share Button