We all know that people "hire" products and services to get a job done. Surgeons hire scalpels to dissect soft tissue. Janitors hire soap dispensers and paper towels to remove grime from their hands. To find ways to innovate, it's critical to deconstruct the job the customer is trying to get done from beginning to end, to gain a complete view of all the points at which a customer might desire more help from a product or service. A methodology called job mapping helps companies analyze the biggest drawbacks of the products and services customers currently use and discover opportunities for innovation. It involves breaking down the task the customer wants to accomplish into the eight universal steps of a job: (1) defining the objectives, (2) locating the necessary inputs, (3) preparing the physical environment, (4) confirming that everything is ready, (5) executing the task, (6) monitoring its progress, (7) making modifications as necessary, and (8) concluding the job. Job mapping differs substantively from process mapping in that the goal is to identify what customers are trying to get done at every step, not what they are doing currently. For example, when an anesthesiologist checks a monitor during a surgical procedure, the action taken is just a means to the end. Detecting a change in patient vital signs is the job the doctor is trying to get done. Within each of the discrete steps lie multiple opportunities for making the job simpler, easier, or faster. By mapping out every step of the job and locating those opportunities, companies can discover new ways to differentiate their offerings.

Eager to grow through innovation, companies are looking to customers to guide them toward unmet needs. But these entities often end up with vague, unusable -- or even misleading -- customer input. Why? The authors studied 10,000 customer need statements from many industries and discovered that companies have not even established a definition of what a customer need is or how user input should be standardized in terms of structure and format. Too often, companies ask customers to react to potential solutions, rather than zeroing in on their expertise: the "job" they need to accomplish with the product or service, and at which steps that experience could use improvement. By deconstructing the job, companies can identify opportunities that are universal and long-standing. In addition, the authors say, companies can collect data that fits their innovation strategy. What the authors propose is a disciplined process for gathering customer requirements that will then be addressed by innovative ideas. They outline the six characteristics that a useful customer statement must possess, including measuring value strictly from a user's perspective -- and not from the factors the company believes should form the basis for the customer's evaluation. The most helpful statements also prompt a clear course of action, specifying what dimensions of the "job" need improvement, such as its sluggish pace or inconsistent quality. The authors set forth six rules for eliciting feedback that will yield the right raw data to craft customer statements that resonate across company functions, so that departments can unite around a single growth strategy. Finally, they define the two broad categories of customer requirements -- job statements and desired-outcome statements -- and link which type works best for different innovation strategies. For CEOs, the authors' message is forthright: Successful innovation is about process, not just the result of brainstorming good ideas.

It's difficult to find a company these days that doesn't strive to be customer driven. Too bad, then, that most companies go about the process of listening to customers all wrong. What usually happens is this: Companies ask their customers what they want. Customers offer solutions in the form of products or services. Companies then deliver these tangibles, and customers just don't buy. The reason is simple--customers aren't expert or informed enough to come up with solutions. That's what your R&D team is for. Rather, customers should be asked only for outcomes--what they want a new product or service to do for them. The form the solutions take should be up to you. Using Cordis Corp. as an example, this article describes a series of effective steps for capturing, analyzing, and utilizing customer input. First come in-depth interviews, in which a moderator works with customers to deconstruct a process or activity to unearth "desired outcomes." Researchers then compile a comprehensive list of outcomes that participants rank in order of importance and degree to which they are satisfied by existing products. Finally, using a simple mathematical formula called the "opportunity calculation," researchers can learn the relative attractiveness of key opportunity areas. These data can be used to uncover opportunities for product development, to segment markets properly, and to conduct competitive analysis.