Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
What Customers Want

What Customers Want

Using Outcome-Driven Innovation to Create Breakthrough Products and Services
Stop funding features customers do not need; find the unmet outcomes worth building for.
by Anthony W. Ulwick 2005 256 pages
4.03
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Innovate around the job customers hire products to perform

Start with the task. Ulwick argues that customers usually buy a product or service to get a job done, not because they want a particular feature. A lawn mower helps cut grass; insurance helps manage financial risk. The job is the starting point for discovering what would make an offering valuable. Customers may describe solutions they imagine, but designing those solutions is the company’s responsibility.

A costly lesson. Ulwick’s own turning point was IBM’s PCjr, which failed despite extensive research and a large investment. The book also opens with Motorola’s Iridium satellite phone, an expensive system that attracted too few buyers. In contrast, Cordis found a job that doctors struggled to complete during angioplasty and developed a stent to help prevent the treated vessel from narrowing again. The lesson is not that research guarantees success, but that research should clarify the job before the solution.

Analysis

The job-centered view changes the level at which a company competes. A razor maker can see itself as helping people shave, or as helping them avoid cuts, save time, and care for skin. The broader description can reveal competition from products outside the company’s category. This resembles systems thinking: improve the outcome of the whole task, not one component in isolation. The risk is defining the job so broadly that it becomes unfocused. A useful job statement must still describe a specific task in a recognizable context.

Turn vague requests into measurable outcomes, not literal specifications

Separate the inputs. The book distinguishes three useful kinds of customer information: jobs, outcomes, and constraints. Outcomes are the measures people use to judge how well a job gets done. Constraints are barriers that prevent the job, or a particular part of it, from being done. Requests such as “make it easier” or “add a wider handle” are not outcomes: they describe an impression or a proposed solution, not the result customers need.

Ask what the phrase means. Motorola phone users used “easy to use” to mean different things, including finding a number quickly and avoiding accidental calls. A team should translate such statements into specific performance measures, then check the interpretation with customers. For a circular saw, a useful outcome might concern keeping the cut line visible. Interviewing, observing, or group discussions can all work if the questions uncover these measures.

Analysis

This distinction is valuable because it separates problem definition from solution design. A customer’s proposed feature contains information, but it also carries assumptions about how the problem should be solved. Translating it into an outcome lets designers consider alternatives and trade-offs. The approach also exposes a practical challenge: measurement language can sound artificial unless it reflects the customer’s actual task. Precision is not merely a matter of writing tidy statements. Researchers must preserve context and verify that a metric describes something customers genuinely notice.

Fund important problems customers still struggle to solve

Prioritize unmet value. The book calls an important, insufficiently satisfied job or outcome an opportunity. Its opportunity algorithm adds importance to the positive gap between importance and satisfaction: opportunity = importance + max(importance minus satisfaction, 0). Ratings are scaled from 0 to 10, with higher scores indicating stronger opportunities. Ulwick treats scores above 15 as especially compelling, 12 to 15 as promising, and scores below 10 as generally weak.

Do not confuse more with better. A printer that already meets users’ needs for speed may gain little from printing even faster. Additional features can raise cost, divert effort from genuine problems, or damage performance elsewhere. Overserved outcomes can instead suggest where to simplify or reduce cost. The algorithm is a prioritization aid, not a substitute for judgment about technical feasibility, customer groups, or commercial strategy.

Analysis

The method makes opportunity a comparison between desired importance and experienced performance, rather than a contest between executives’ favorite ideas. That is a useful discipline for allocating limited resources. Its numerical simplicity is also a liability if treated as scientific certainty: ratings depend on how questions are worded, who is surveyed, and whether people can accurately assess satisfaction. Scores should help teams ask better questions, not silence them. A high score identifies a candidate for action, while feasibility, economics, and unintended consequences still require investigation.

Segment by unmet outcomes, not by convenient customer labels

Find groups with different gaps. Traditional categories such as age, industry, or business size can help track sales, but they do not necessarily reveal who shares the same unmet needs. Outcome-based segmentation groups customers according to which important outcomes they find unsatisfied. Ulwick calls these groups segments of opportunity. Job-based segmentation uses unmet jobs instead, helping identify potential new markets.

Motorola found three distinct radio users. One group valued private communication, another needed reliable contact in dangerous situations, and a third used radios to coordinate routine work. A one-size-fits-all product had not served these groups equally. Motorola tailored offerings to their different outcomes and, according to the book, grew revenue by 18 percent in a stagnant market. Demographic and job information can then help describe and reach each segment, but should not be mistaken for the reason it exists.

Analysis

This approach treats segments as patterns in desired value rather than as pre-existing boxes on a marketing chart. That can uncover customers who look different on paper but struggle with the same task. It also makes segmentation directly useful to product design. Still, statistical clusters do not automatically become viable markets. A group must be large enough, reachable, and a sensible fit for the company. Profiling matters because a mathematically distinct segment is only strategically useful if the business can recognize and serve its members.

Choose both the growth path and the real value judge

Innovation has several routes. The book distinguishes improvements to products or services, creation of new markets, operational changes, and disruptive approaches that use a new technology or lower-cost model. Companies can improve an existing job, help customers do related jobs, serve people who cannot use current offerings, or create a solution for a job with no established market.

Map the value chain carefully. The person paying may not be the person using or judging the product. A printer company, for example, may need to understand both end users’ work and IT administrators’ management tasks. A business should contact relevant decision-makers and users directly rather than assume a buyer, channel partner, or salesperson can speak for everyone. Conflicting outcomes across patients, clinicians, purchasers, and administrators are not a reason to ignore those groups; they are a reason to weigh their needs explicitly.

Analysis

The strategic choice of customer is as important as the choice of product. A company can solve the wrong problem very efficiently if it mistakes the purchaser’s priorities for the user’s. Looking across the value chain also reveals that value can be distributed unevenly: a feature that helps one participant may create work or cost for another. The framework is strongest when it prompts teams to identify whose judgment determines adoption, payment, and daily use. It becomes unwieldy if every stakeholder is treated as equally decisive.

Sell the underserved value your current product already delivers

Find value hiding in plain sight. Once a company knows which outcomes matter and remain poorly served, it can check whether current products already perform well on them. If so, better communication may create growth without changing the product. Cordis found that its existing angioplasty balloons addressed three opportunities that customers had not been told about. After revising its sales message, the company’s market share rose from 1 to 5 percent in six months, according to the book.

Make the claim concrete. Instead of saying a razor is “easy to use,” a company can explain how a grip reduces the risk of dropping it when wet. Functional products should generally communicate functional advantages; products that shape identity, such as cars or clothing, may also benefit from emotional positioning. A brand tied clearly to the task it performs can make the product easier to recall when that task arises.

Analysis

This insight connects product development to communication: a market can overlook a real advantage simply because the company describes it in language customers cannot connect to their work. Specific claims reduce the burden on buyers to infer why a feature matters. The emotional-versus-functional distinction is useful as a diagnostic, not a rigid law. People can have identity motives even when buying technical products, and functional products still need trust and clarity. Strong messaging should start with demonstrated value, then fit the emotional character of the purchase.

Kill projects that improve the wrong measures

Evaluate projects against the target. Companies often keep too many initiatives alive because leaders lack a shared way to judge them, project champions become invested, and teams fear missing a competitor’s move. Ulwick recommends comparing each proposal with the outcomes the company has chosen to pursue. A cross-functional team estimates whether each project would improve customer satisfaction on those outcomes and explains which feature supports each estimate.

Reallocate with evidence. A drug-pump example contrasts a feature that improves one specific outcome with a broader product concept that performs poorly overall. The first may merit funding for its focused benefit; the second may deserve cancellation. Projects can also be adjusted to combine useful features. The goal is not to protect every idea but to concentrate resources on initiatives most likely to create customer value, while accounting for effort, cost, risk, regulation, and competitive weakness.

Analysis

A shared evaluation standard can reduce the influence of hierarchy and attachment, making disagreement more productive. It gives teams a common question: what customer outcome changes, and by how much? Yet predicted satisfaction is still a forecast, especially before a product exists. Teams should record assumptions and test uncertain claims through prototypes or market evidence. The framework helps make project decisions explicit, but it cannot eliminate uncertainty. Its benefit is to make uncertainty visible and comparable rather than disguising it as confidence.

Aim creativity at verified gaps, then score concepts against the whole job

Generate fewer, better ideas. Focused brainstorming directs creative work toward outcomes customers value but current offerings fail to satisfy. The team tackles a target at a time, seeks a substantial improvement, and uses constraints such as cost or development effort to keep ideas practical. Bosch’s saw team considered laser guidance but found it too costly. Redirecting the saw’s airflow helped clear the cutting path and debris without that expense; a removable cord also addressed problems caused by damaged or snagging cords.

Test the whole value proposition. The customer scorecard compares a concept’s estimated performance across the full set of customer outcomes, often 50 to 150, rather than judging it by one appealing feature. At Pratt & Whitney, a proposed factory control system offered only about a 3 percent value increase, below the team’s 10 percent goal. A broader service redesign was projected to improve value by 38 percent, guiding the company away from a costly but weak proposal.

Analysis

The scorecard’s most important contribution is its insistence on system-level evaluation. A feature can solve one visible irritation while worsening a more consequential part of the job. That is why ideation and evaluation belong together: creativity needs a target, and every promising idea needs scrutiny across competing outcomes. The numbers can create a false impression of precision when estimates are subjective. Their best use is comparative, helping teams expose trade-offs and make assumptions discussable before committing heavily to development.

Let customer value migrate instead of endlessly polishing yesterday’s advantage

Needs persist, opportunities shift. The underlying outcomes for a job may remain stable, but products can improve how well they satisfy them. Once an important outcome is well served, it stops being the best place to invest; attention should move to other unmet outcomes or related jobs. Bosch’s saw improvements addressed several different frustrations, while Apple’s music player grew beyond playing music by helping users acquire and organize songs.

Use gaps to guide long-term work. Broad-market opportunities may support a shared product theme, a new accessory, or cost reduction in overserved areas. Harder problems can become research and development targets. The book argues that companies should distribute these findings across teams and treat innovation as a managed business process, not a sequence of disconnected brainstorms. The practical test remains whether a proposed change improves a meaningful job without sacrificing more important value elsewhere.

Analysis

Value migration is a useful antidote to feature escalation. It reminds firms that yesterday’s differentiator can become table stakes, while other sources of frustration remain untouched. The idea also applies to internal processes: once one bottleneck is removed, the next constraint becomes more visible. The caution is that changing priorities should not mean chasing every new signal. Companies need repeated customer evidence and enough continuity to build capabilities. A durable innovation system is adaptive, but not restless for its own sake.

Analysis

The book’s central contribution is a shift in the unit of analysis. Rather than treating customer statements as instructions, it asks companies to identify the work customers are trying to accomplish and the measures by which they judge success. This distinction links research to the decisions that follow: which customers to serve, where to invest, how to segment, what to build, and what to say about it. The resulting method is unusually operational. It does not stop at empathy or inspiration; it proposes measurable outcomes, comparative opportunity scores, concept evaluation, and resource allocation.

Its strongest insight is that innovation failures often arise not from a shortage of ideas but from a shortage of validated direction. The Cordis and Bosch examples make that claim tangible: opportunity knowledge can expose hidden value in existing products, redirect a pipeline, and shape a new design. The approach also makes organizational disagreement more tractable because teams can debate evidence against a shared set of customer measures rather than defend personal preferences.

The quantitative language deserves careful handling. Importance and satisfaction ratings are not direct readings of reality. They depend on who is surveyed, how outcomes are phrased, and whether respondents can assess a hypothetical or complex product. The opportunity formula offers a consistent ranking convention, not proof that a particular investment will succeed. Concept scorecards rely partly on expert estimates, which can inherit the biases they are meant to discipline. The book’s reported business outcomes are persuasive cases, but they do not by themselves establish that the method caused every result.

The framework is most useful as a decision system with feedback, not as a machine that removes uncertainty. Interviews reveal candidate measures, quantitative research checks their prevalence, and prototyping or market performance tests the proposed solution. Used in that way, outcome-driven innovation combines customer understanding with engineering judgment. Its durable lesson is to measure the problem before debating the answer, while remaining skeptical of any metric that claims to settle the debate completely.

Summary in 30 Seconds
Customers buy products to accomplish tasks, and judge them by specific outcomes. Rate each outcome’s importance and current satisfaction: high importance paired with a large satisfaction gap signals an opportunity. Segment customers by those unmet needs, then compare proposed products against the full set of outcomes. Motorola tailored radio offerings to distinct user needs and grew revenue 18 percent in a stagnant market. Cordis increased market share from 1 to 5 percent in six months by communicating value its existing product already delivered.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.03 out of 5
Average of 500+ ratings from Goodreads and Amazon.

What Customers Want receives mixed reviews. Many praise its innovative approach to product development, focusing on customer outcomes rather than traditional methods. Readers find the concept valuable for product managers and innovators. However, some criticize the book for being repetitive, self-promotional, and lacking practical implementation details. Critics argue it rehashes old ideas and serves as a marketing tool for the author's consulting services. Despite these critiques, many readers appreciate the book's insights on understanding customer needs and improving product development processes.

Your rating:
4.51
234 ratings
Want to read the full book?

Glossary

Outcome-driven innovation

Innovation guided by customer outcomes

An approach to innovation that identifies the jobs customers want to complete, the outcomes they use to judge success, and the constraints that obstruct them. Companies prioritize unmet opportunities, then develop, evaluate, and communicate solutions against those measures rather than relying primarily on requests for features or vague expressions of need.

Job

Task a customer wants done

A task or activity that an individual or organization is trying to complete. People acquire products and services to help with jobs, such as cutting wood, managing customer leads, or reducing financial risk. In this method, the job provides the context for identifying the measures customers use to judge performance and for finding related tasks that may create new markets.

Desired outcome

Customer’s measure of job success

A metric customers use to judge how well a job is being done. It describes a result customers want to improve, often in terms of time, frequency, likelihood, or amount. Outcomes are distinct from proposed features and broad adjectives because they specify a performance measure that product teams can investigate, prioritize, and use to evaluate ideas.

Constraint

Barrier to completing a job

A condition that prevents customers from doing a job at all, or from doing it in particular circumstances. Constraints may be physical, regulatory, or environmental. Identifying them can reveal opportunities that differ from improving an existing product’s performance, because the customer may first need a barrier removed before the job is possible.

Opportunity algorithm

Importance and satisfaction ranking

A formula used to estimate how strongly an outcome, job, or constraint represents an opportunity: importance plus the greater of zero or the difference between importance and satisfaction. The method gives priority to important, poorly served outcomes and prevents high satisfaction from subtracting value from an outcome’s importance.

Outcome-based segmentation

Grouping customers by unmet outcomes

A market segmentation method that groups customers according to the outcomes they consider important and insufficiently satisfied. Statistical clustering uses opportunity ratings to identify groups with distinct patterns of unmet value. These segments can guide product design and targeting; demographic and behavioral information can then help describe and reach them.

Job-based segmentation

Grouping by unmet jobs

A segmentation approach that uses jobs, rather than product outcomes, to identify groups of customers who have important tasks that current offerings do not adequately serve. It is intended to help discover potential new markets. Once a promising job is identified, the company can investigate the desired outcomes associated with performing it.

Customer scorecard

Concept evaluation against outcomes

A method for comparing proposed products or services with the full set of customer outcomes for a job. A team estimates how well each concept would satisfy those outcomes, especially the highest-priority opportunities, and compares the result with existing offerings. It is designed to reveal both value and trade-offs before full development.

Focused brainstorming

Idea generation aimed at unmet outcomes

A structured ideation method that directs a team to develop solutions for specific, important outcomes that existing offerings do not satisfy well. Instead of rewarding a large volume of ideas, it emphasizes a small number of promising concepts, practical constraints, early rejection of weak ideas, and refinement for value, cost, effort, risk, and defensibility.

Value migration

Shifting opportunities as products improve

The movement of innovation opportunities as products and technologies improve. The underlying outcomes customers care about may remain stable, while satisfaction on particular outcomes rises. Once an outcome is well served, the strongest opportunity shifts toward other important outcomes, related jobs, or unmet customer groups.

Outcome-based brand

Brand linked to a customer job

A brand that makes clear what task a product helps customers perform. The book’s example is a reciprocating saw brand whose name suggests its cutting purpose. By connecting a product with a recognizable job, this type of branding can help customers recall the offering when they need to complete that job.

FAQ

1. What’s "What Customers Want" by Anthony W. Ulwick about?

  • Outcome-Driven Innovation Framework: The book introduces and explains the Outcome-Driven Innovation (ODI) methodology, a systematic approach to creating breakthrough products and services by focusing on the outcomes customers want to achieve.
  • Moving Beyond Customer-Driven: Ulwick critiques traditional customer-driven approaches and argues for a shift toward understanding the "jobs" customers are trying to get done and the metrics they use to measure success.
  • Eight-Step Process: The book outlines an eight-step process for innovation, from formulating strategy to generating and evaluating new concepts, all centered on customer outcomes.
  • Practical Application: Through case studies and real-world examples, Ulwick demonstrates how companies can apply ODI to reduce failure rates and consistently deliver products customers truly value.

2. Why should I read "What Customers Want" by Anthony W. Ulwick?

  • Predictable Innovation Success: The book offers a proven, structured method to make innovation less random and more predictable, addressing the high failure rates of new products.
  • Actionable Tools and Techniques: Readers gain practical tools for gathering customer insights, prioritizing opportunities, and aligning product development with real customer needs.
  • Applicable Across Industries: The ODI approach is relevant for companies in any sector—product, service, B2B, or B2C—seeking growth or market leadership.
  • Challenge to Conventional Wisdom: Ulwick’s critique of the "voice of the customer" paradigm encourages readers to rethink how they approach customer research and product development.

3. What are the key takeaways from "What Customers Want" by Anthony W. Ulwick?

  • Focus on Customer Outcomes: Successful innovation starts by identifying the jobs customers want to get done and the outcomes they use to measure success, not by asking for feature requests.
  • Systematic Process: Innovation can be managed like any other business process by following Ulwick’s eight-step ODI framework.
  • Prioritization is Critical: Not all customer needs are equal; the best opportunities are those that are both important and underserved.
  • Segmentation by Outcomes: Traditional demographic or needs-based segmentation is less effective than segmenting customers by the outcomes they struggle to achieve.

4. How does the Outcome-Driven Innovation (ODI) method by Anthony W. Ulwick work?

  • Jobs, Outcomes, Constraints: ODI starts by identifying the functional, personal, and social jobs customers are trying to get done, the outcomes they desire, and any constraints they face.
  • Quantitative Prioritization: Customer outcomes are rated for importance and satisfaction, and an "opportunity algorithm" is used to identify where the biggest gaps—and thus opportunities—exist.
  • Segmentation and Targeting: Markets are segmented based on clusters of underserved outcomes, allowing for precise targeting of innovation efforts.
  • Idea Generation and Evaluation: Focused brainstorming is used to generate solutions for high-opportunity outcomes, and a customer scorecard quantifies the value of new concepts before development.

5. What are the main differences between the traditional customer-driven approach and the Outcome-Driven Innovation approach in "What Customers Want"?

  • Type of Input: Traditional approaches rely on customer-stated needs, solutions, or specifications, while ODI seeks to uncover the underlying outcomes customers use to judge success.
  • Language and Precision: ODI emphasizes a common, precise language (jobs, outcomes, constraints) to avoid ambiguity and misinterpretation.
  • Process Discipline: The ODI method treats innovation as a repeatable, measurable process, rather than an art or a series of creative guesses.
  • Predictability: By focusing on quantifiable outcomes, ODI increases the predictability of innovation success compared to the trial-and-error nature of customer-driven methods.

6. What are the eight steps of the Outcome-Driven Innovation process in "What Customers Want"?

  • Formulate Innovation Strategy: Decide what type of innovation to pursue and who in the value chain to target.
  • Capture Customer Inputs: Gather data on jobs, outcomes, and constraints, not just wants or feature requests.
  • Identify Opportunities: Use quantitative methods to find which outcomes are important and underserved.
  • Segment the Market: Group customers by shared underserved outcomes to find segments of opportunity.
  • Target Opportunities for Growth: Select which opportunities to pursue for maximum value creation.
  • Position Current Products: Align messaging and branding with the outcomes your products already address.
  • Prioritize Projects in the Pipeline: Evaluate and fund initiatives that best address targeted outcomes.
  • Devise Breakthrough Concepts: Use focused brainstorming and customer scorecards to generate and validate new ideas.

7. How does "What Customers Want" by Anthony W. Ulwick define and use the concept of "jobs to be done"?

  • Jobs as the Unit of Analysis: Customers buy products and services to get specific jobs done, which can be functional, personal, or social.
  • Beyond Demographics: Focusing on jobs shifts attention from who the customer is to what they are trying to accomplish.
  • Growth Opportunities: Identifying ancillary or related jobs can reveal new avenues for innovation and market expansion.
  • Stable Over Time: Jobs tend to remain stable, providing a reliable foundation for long-term innovation strategy.

8. How does "What Customers Want" by Anthony W. Ulwick recommend identifying and prioritizing innovation opportunities?

  • Importance and Satisfaction Ratings: Customers rate each outcome for importance and current satisfaction, creating a data-driven basis for opportunity identification.
  • Opportunity Algorithm: The formula (Opportunity = Importance + max(Importance – Satisfaction, 0)) highlights outcomes that are both important and underserved.
  • Underserved vs. Overserved: High-opportunity scores indicate areas ripe for improvement, while overserved outcomes suggest where cost can be reduced.
  • Avoiding Common Mistakes: The method helps companies avoid improving already satisfied outcomes or focusing on unimportant ones.

9. What is outcome-based market segmentation, and why does "What Customers Want" by Anthony W. Ulwick argue it’s superior?

  • Segments of Opportunity: Outcome-based segmentation groups customers by the specific outcomes they find underserved, rather than by demographics or product usage.
  • Homogeneity and Predictability: These segments are more homogeneous in their needs, making them more predictable targets for innovation.
  • Revealing Hidden Markets: This approach can uncover new or overlooked segments, including those suitable for disruptive innovation.
  • Actionable Insights: Segmentation by outcomes directly informs product development, messaging, and go-to-market strategies.

10. How does "What Customers Want" by Anthony W. Ulwick advise companies to generate and evaluate new product ideas?

  • Focused Brainstorming: Idea generation is directed at specific, high-opportunity outcomes, rather than being a scattershot process.
  • Quality Over Quantity: The goal is a handful of high-value ideas, not hundreds of unfocused suggestions.
  • Customer Scorecard: New concepts are evaluated against all targeted outcomes, quantifying the value they deliver before development begins.
  • Iterative Improvement: The process encourages refining ideas to maximize value, minimize cost, and ensure sustainability.

11. What are the most common pitfalls in innovation that "What Customers Want" by Anthony W. Ulwick helps companies avoid?

  • Vague Customer Inputs: Relying on ambiguous needs, solutions, or benefits instead of precise outcomes leads to misaligned products.
  • Misallocated Resources: Without clear prioritization, companies waste resources on low-value or overserved outcomes.
  • Ineffective Segmentation: Traditional segmentation can create "phantom segments" that don’t reflect real opportunities.
  • Failure to Kill Bad Projects: The ODI process provides objective criteria for stopping projects that won’t deliver customer value.

12. What are the best quotes from "What Customers Want" by Anthony W. Ulwick and what do they mean?

  • “Customers buy products and services to help them get jobs done.”
    This quote encapsulates the core of ODI: focus on the job, not the customer’s stated wants.
  • “The literal voice of the customer does not translate into meaningful inputs.”
    Ulwick warns that simply listening to customer requests often leads to the wrong product decisions.
  • “Innovation is a science—a systematic process for creating products or services that delivers new value to customers—and not an art form that is forever destined to produce random and unpredictable results.”
    This challenges the myth that innovation is inherently unpredictable, advocating for a disciplined, process-driven approach.
  • “Only after knowing what jobs customers are trying to get done and what outcomes they are trying to achieve are companies able to systematically and predictably identify opportunities and create products and services that deliver significant new value.”
    This quote summarizes the book’s thesis: understanding jobs and outcomes is the foundation for successful, repeatable innovation.

About the Author

Anthony Ulwick is a business author and consultant specializing in innovation and product development. He is known for developing the Outcome-Driven Innovation (ODI) methodology, which focuses on understanding customer needs and desired outcomes to create successful products. Ulwick is the founder and CEO of Strategyn, a consulting firm that helps companies implement his innovation strategies. He has written multiple books on innovation and has been recognized for his contributions to the field. Ulwick's work has influenced many product managers and innovators, though some critics argue his approach is not entirely original and serves to promote his consulting services.

Download PDF

To save this What Customers Want summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.40 MB     Pages: 23

Download EPUB

To read this What Customers Want summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.37 MB     Pages: 29
Want to read the full book?
Follow
Listen11 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...