Key Takeaways
Replace the lone-genius myth with a repeatable way to build better solutions
Creativity can be practiced. The book argues that organizational innovation need not depend on rare visionaries. Design thinking is a teachable approach that begins by learning how people experience a problem, then widens the possible solutions, brings stakeholders into making them, and tests ideas in real settings. It helps managers move beyond assumptions and analysis without discarding either. The ten cases range from redesigning an insurance merger to improving meals for older people, showing that the approach applies beyond products and traditional design teams.
A partnership, not a magic trick. The strongest examples pair designers' research and visualization skills with managers' knowledge of the organization and ability to act. The approach is flexible: teams can use a few tools or work through the whole process. Its promise is not instant inspiration, but a more reliable route from an unclear problem to a workable change.
The useful shift is from treating creativity as a personality trait to treating it as a set of learnable practices. That changes who gets invited into innovation: frontline staff, analysts, and operators can contribute without pretending to be professional designers. The partnership model also resists a familiar trap, where a creative team produces an elegant concept that the operating organization cannot deliver. Still, a method cannot neutralize power differences by itself. Managers must give participants real access to users, time to experiment, and authority to change what the research reveals.
Study the lived problem before funding the obvious fix
Observe before prescribing. Toyota initially seemed to need a better database for its customer contact center. Watching representatives work revealed a more tangled problem: staff searched as many as thirteen applications, consulted paper files, and sometimes left their desks while customers waited. The redesign therefore addressed the work process and the software interface, not just a database. At Denmark's Good Kitchen, leaders thought the menu needed updating. Home visits and observation uncovered lost choice and dignity for older customers, alongside kitchen staff frustrated by repetitive work.
A wider view changes the brief. Ethnography means studying people in their ordinary settings through observation and conversation. It can reveal needs people do not articulate directly, as well as constraints hidden from decision makers. The book's cases repeatedly show that the initial problem statement is a hypothesis, not a fact to defend.
Observation is especially valuable when work has become routine enough to be invisible to its designers. A journey map, which traces steps and emotional points in an experience, can expose handoffs, delays, and workarounds that a satisfaction survey misses. Yet close observation is not a shortcut to certainty. A small group of observed users can reveal mechanisms and generate better questions, but it cannot establish how common a behavior is. Discovery should broaden understanding, then be paired with broader measurement when decisions depend on prevalence.
Test rough futures with real people before polishing them
Make an idea tangible. A prototype is a simple, concrete representation that lets people react to an idea before it is fully built. SAP's strategy team used a story-based slide presentation to show what Web 2.0 might mean for the company's products and internal decision making. Executives expected a short presentation, but it opened a three-hour discussion. At IBM, a pilot at the Sibos financial-services event tested a redesigned trade-show experience, including informal workspaces, interactive screens, and trained hosts. IBM reported a 78 percent year-over-year increase in leads at the event.
Learn before scaling. A learning launch is a limited real-world test designed to expose assumptions with actual users. Low-cost prototypes make it easier to revise or abandon an idea early. They are not merely miniature versions of the finished product; they are instruments for learning what people understand, value, and do.
A prototype functions as a shared object that lets people with different expertise discuss the same possibility instead of arguing from private mental pictures. That is why a rough slide, mock-up, or service rehearsal can change a meeting more than another polished report. The caution is that vividness can persuade without validating. A compelling scenario may attract attention while masking operational costs or weak demand. Good testing separates enthusiasm for the presentation from evidence that the proposed service works under ordinary conditions.
Let people build the strategy they are expected to carry
Participation creates ownership. After Suncorp merged with Promina, leaders needed employees from different cultures to build a shared direction. A facilitated strategy process used a city metaphor to help managers imagine how their combined insurance business should work. The leadership team embraced the idea, but a polished image presented to wider staff fell flat. The people hearing the message had not helped create it. Suncorp changed course, asking business units to design their own neighborhoods within the larger city.
Leave room to contribute. The resulting conversations helped employees connect daily work to the new strategy. In one unit, the share of employees reporting that they understood the vision rose from 48 percent before the workshops to 94 percent afterward. The team found that maps with some guidance but unfinished space prompted better discussion than either a fully completed design or a blank page.
This case connects participation to procedural fairness: people are more likely to regard a direction as legitimate when they can shape how it applies to their work. The metaphor helped make an abstract merger discussable, while the unfinished map signaled that employee input could still matter. But participation is not the same as shared power. If leaders invite ideas and then ignore them, the exercise can deepen cynicism. The practical test is whether contributions alter decisions, responsibilities, or resources, not whether a workshop feels energetic.
Turn technical selling into a conversation about customers' future
Show what technology enables. 3M's Electronics and Energy business sold advanced materials that customers could struggle to imagine in finished products. Design strategist Lee Fain observed sales meetings and found that technical presentations explained capabilities but often failed to make future uses feel concrete. He developed visual and physical materials, including future-use videos, demonstrators, and sample models, to give customers something specific to respond to.
Use provocation carefully. Design provocation means presenting a plausible future concept to prompt a reaction and discover what matters to customers. At the Consumer Electronics Show, a video showed possible uses for 3M's patterned transparent conductors. Customers responded with interest, and the material reportedly reached about 300,000 online views. Fain kept the scenarios connected to what the lab could actually achieve, so the vision opened a conversation rather than becoming science fiction.
In technical markets, customers may understand a component's specifications yet struggle to imagine its consequences for their own products. A concrete scenario can bridge that gap and help buyers articulate needs they had not yet framed. It also gives sales teams a more collaborative role than simply transferring product facts. The ethical and commercial boundary matters: aspirational demonstrations must distinguish demonstrated capability from plausible future use. Otherwise, the same storytelling that builds excitement can create expectations the engineering organization cannot meet.
Pair human stories with numbers, because each answers a different question
Different evidence, different jobs. MeYou Health wanted to help people improve well-being through online social support. Healthways had extensive numerical data about health risks, but those measures did not explain how to motivate behavior. Interviews with thirty-six people, using journals, visual exercises, and conversation, helped the team identify different motivations and create seven evidence-based personas. The insights informed small digital challenges and products such as Daily Challenge.
Test the human insight. The company reported that 250,000 members had completed more than six million health-improving actions. A randomized trial with 1,503 adults found that Daily Challenge users' well-being scores improved 2.35 points more than those of the control group after ninety days. Qualitative research helped identify what to build; usage data and the trial assessed whether it was used and whether outcomes changed.
The distinction is epistemic as much as methodological. Interviews can explain how people interpret a situation, while surveys and experiments can estimate frequency or test effects. Treating either as a substitute for the other produces predictable errors: numbers without context can describe a problem without suggesting an intervention, while vivid stories can make a rare experience feel universal. The trial strengthens the case for the product, although a change in a well-being index is still a measured proxy. Long-term health and cost effects require their own evidence.
Redesign the whole service system, not its most visible symptom
Include everyone who shapes the experience. Holstebro's subsidized meal service was meant to help older people, yet many customers ate too little. Researchers observed customers at home and staff in the kitchen. They found that seniors disliked losing control over food choices and often ate alone, while kitchen employees felt their skills were overlooked and their menus were monotonous. The answer required changes to both sides of the service, not just new recipes.
Change the system's signals. The service adopted a restaurant-style identity, more appealing menus, seasonal dishes, flexible meal components, and customer comment cards. Kitchen staff received new uniforms and direct feedback from the people they served. Some dishes saw a fivefold rise in orders in the first week. The story shows how employee pride, customer dignity, communication, and the meal itself can reinforce one another.
Service quality is produced across a network of interactions, not by the visible artifact alone. The meal, the delivery, the menu, the worker's status, and the customer's ability to choose all contribute to the experience. This systems view aligns employee conditions with customer outcomes rather than treating staff as a cost variable. Still, a successful redesign in one municipality does not settle how to balance choice, nutrition, labor, and public budgets elsewhere. The transferable lesson is to map the system before assuming one intervention will solve it.
Make experimentation a daily habit, not a special innovation event
Build the practice into work. Intuit wanted to move beyond making software easy to use and create experiences customers found delightful. Its Design for Delight initiative centered on customer empathy, generating a broad range of options before selecting, and rapid experimentation. The company first tried talks about innovation, then realized that enthusiasm was not changing behavior. It trained Innovation Catalysts to help teams practice the methods in ordinary work and created templates, coaching, and customer access to reduce friction.
Support beats slogans. The Catalyst network grew to nearly two hundred people. Intuit also reduced the average time employees waited to meet customers from eleven days to five. TurboTax teams used weekly experiments during the short tax season, turning candidate ideas into tests and using results to guide the next round. Design thinking became more than a scheduled workshop when leaders and teams used it in their regular decisions.
The case treats organizational capability as infrastructure: people need skills, access to customers, peer support, and leaders who model the behavior. This resembles deliberate practice, where repeated performance with feedback builds competence more reliably than inspiration alone. The scaffolding is useful for novices, but process can harden into ritual if teams focus on completing templates instead of learning. A healthy system should make experimentation easier while preserving the freedom to alter the method when the problem requires it.
Scale design by changing routines, not merely naming a new department
Look for changes beneath the headline metric. Across the cases, design thinking contributed by reframing questions, bringing different groups together, making complex evidence easier to grasp, leaving room for participation, and speeding decisions through small tests. Some results were readily counted, such as IBM's leads or Toyota's shorter customer wait times. Others appeared in conversations and behavior: employees could explain a strategy, sales teams discussed customer problems differently, and staff began testing ideas rather than polishing plans in isolation.
Treat measurement as a chain. Intuit tracked whether employees used the methods and whether customer interactions increased, while business results could take years to appear. The authors caution that no single return-on-investment figure captures every contribution. A practical evaluation can connect activity, behavior, user response, and business or social outcomes, while admitting where attribution remains uncertain.
This is a stronger measurement model than demanding an immediate financial return from every exploratory project. It recognizes that changed routines and conversations can be leading indicators, while revenue, satisfaction, or health outcomes are lagging indicators. The limitation is selection: these are deliberately successful cases, not a comparison group showing how similar projects perform without design thinking. Organizations should therefore treat the book as a source of plausible mechanisms and testable practices, not as proof that the method alone caused every reported gain.
Analysis
The book is a practice-oriented collection of ten organizational cases, framed by a shared argument: creative problem solving can be made more reliable when teams study human experience, make assumptions visible, and learn through tangible experiments. Its most important contribution is not a universal sequence of workshop exercises. It is a shift in managerial attention, from defending an early problem definition to improving it, and from issuing a finished answer to involving the people who must use and deliver it.
Across the cases, the same capabilities recur in different forms. IBM studies how people learn before redesigning trade shows. Toyota maps representatives' work before changing software. Suncorp lets employees shape a strategy metaphor after discovering that a polished message does not create ownership. The Good Kitchen sees food service as a relationship among customers, cooks, and delivery workers. These examples suggest that innovation often depends less on inventing a startling object than on coordinating a system of people, tools, and expectations around a better experience.
The evidence deserves a careful reading. The cases are selected because design thinking appeared to work, and reported improvements are not generally isolated from other changes or compared with control organizations. The numbers are useful demonstrations, not universal forecasts. The strongest causal evidence in the text comes from MeYou Health's randomized trial, but even that evaluates a defined intervention and a particular well-being measure. Other cases provide credible descriptions of mechanisms, such as user involvement improving adoption, without proving that design methods alone caused the business results.
That limitation does not erase the book's value. It clarifies how to use it: borrow the habits, not the success rates. Begin with field evidence, involve people with different forms of expertise, create a low-cost representation of the idea, and test consequential assumptions before scaling. Then track not only outcomes but the behaviors that plausibly produce them. Design thinking is most persuasive here as disciplined organizational learning, not as a guarantee of novelty or a substitute for analysis, operational judgment, or accountability.
Review Summary
The reviews for Solving Problems with Design Thinking are mixed, with ratings ranging from 2 to 5 stars. Readers appreciate the real-world examples and case studies illustrating design thinking principles. Many find the book useful for understanding how design thinking can be applied in various industries. However, some critics note that the book lacks depth in implementation details, metrics, and challenges faced. Several reviewers mention that while the book provides a good introduction to design thinking, it may be too procedural or superficial in its treatment of the subject.
People Also Read
Glossary
Design thinking
Human-centered problem solvingAn approach to organizational problem solving that combines user-focused discovery, broader problem framing, collaborative idea development, visualization, and real-world experiments. In the book, it is presented as a learnable practice for managers and designers, not a mysterious gift reserved for artistic geniuses. It can be used across products, services, internal processes, strategy, and civic challenges.
Learning launch
A real-world concept testA limited pilot that exposes a proposed idea to actual users in a live setting so a team can test key assumptions before committing to broad deployment. The goal is to learn from behavior and feedback, revise the concept, and reduce the risk of scaling an idea that works only in a meeting or presentation.
Design provocation
A concept that prompts reactionA way of using a visual or tangible concept to elicit a response and deepen discussion with customers. Rather than waiting for people to describe needs in the abstract, a team presents a plausible possibility and observes what they find useful, troubling, or irrelevant. The concept is a conversation tool, not a promise that the proposed solution already exists.
Design for Delight
Intuit's customer-centered practiceIntuit's initiative to extend its focus beyond ease of use and build a company-wide capability for creating customer value. Its core practices emphasize understanding customers deeply, generating a wide range of possibilities before choosing, and testing ideas quickly. The initiative aimed to make these behaviors part of ordinary work rather than activities confined to special innovation sessions.
Journey mapping
A map of lived experienceA visual account of the steps a person takes through an experience, including actions, interactions, and emotional highs and lows. Teams use journey maps to see where friction, delay, confusion, or unmet needs occur. The book applies the method not only to customer experiences but also to employees' internal work processes, as in Toyota's contact center.
Ethnography
Observation in everyday settingsA research approach that studies people in the environments where their ordinary activities take place, often using observation and in-depth interviews. In the book's cases, it helps teams understand behavior and context that may not emerge from surveys or secondhand reports. It is used to generate insights and hypotheses, not to estimate how common a behavior is across an entire population.
Minimum viable product
A usable early productAn early version of a product with enough working functionality for real users to try it. It goes beyond a nonfunctional mock-up by enabling interaction and feedback. MeYou Health used minimum viable products to release simple digital experiences quickly, learn from actual use, and improve features rather than spending many months building a complete product before testing demand.
Innovation Catalyst
An internal design facilitatorAn Intuit employee trained to help colleagues apply design practices in their own work. Catalysts facilitate teams rather than arriving as experts with finished solutions. The program emphasized practical skills, supportive managers, and networks of peers, enabling design methods to spread across business units and become part of routine work.
FAQ
What's "Solving Problems with Design Thinking" about?
- Overview: "Solving Problems with Design Thinking" by Jeanne Liedtka, Andrew King, and Kevin Bennett explores how design thinking can be applied to solve complex business and social problems.
- Structure: The book is structured around ten real-world case studies that demonstrate the successful application of design thinking in various organizations.
- Purpose: It aims to demystify design thinking and show how it can be a practical tool for managers to drive innovation and solve problems creatively.
- Audience: The book is targeted at managers, designers, and anyone interested in learning how to apply design thinking to improve organizational performance.
Why should I read "Solving Problems with Design Thinking"?
- Practical Insights: The book provides practical insights into how design thinking can be applied across different industries and sectors.
- Real-World Examples: It includes ten detailed case studies that illustrate the effectiveness of design thinking in solving real-world problems.
- Actionable Tools: Readers will gain access to a variety of design thinking tools and techniques that can be implemented in their own organizations.
- Broader Perspective: It offers a broader perspective on innovation, emphasizing collaboration, empathy, and experimentation.
What are the key takeaways of "Solving Problems with Design Thinking"?
- Reframing Problems: Design thinking helps in reframing problems to ask better questions, leading to more innovative solutions.
- Collaboration and Engagement: The process emphasizes collaboration and engagement, leveraging diverse perspectives to drive innovation.
- Prototyping and Experimentation: Rapid prototyping and real-world experimentation are central to testing and refining ideas.
- Empathy and User-Centricity: A deep understanding of user needs and empathy are crucial for creating solutions that truly resonate with stakeholders.
How does "Solving Problems with Design Thinking" define design thinking?
- User-Centric Approach: Design thinking is defined as a user-centric approach to problem-solving that emphasizes empathy and understanding of user needs.
- Iterative Process: It involves an iterative process of ideation, prototyping, and testing to develop innovative solutions.
- Collaboration: The approach encourages collaboration across different functions and disciplines to leverage diverse perspectives.
- Focus on Experimentation: Design thinking is characterized by a focus on experimentation and learning from failure to refine solutions.
What are some examples of design thinking in action from the book?
- IBM's Trade Show Transformation: IBM used design thinking to transform its trade show experience, focusing on human interaction and engagement.
- Toyota's Customer Contact Center: Toyota redesigned its customer contact center by involving employees in the design process, leading to improved service.
- The Good Kitchen in Denmark: The Good Kitchen used design thinking to improve meal services for the elderly, focusing on both customer and employee needs.
- Suncorp's Postmerger Integration: Suncorp applied design thinking to align strategy and vision during a complex postmerger integration.
What is the "What is? What if? What wows? What works?" framework?
- What is?: This stage involves understanding the current reality and gathering insights through research and observation.
- What if?: In this stage, multiple options and ideas are generated to envision a new future.
- What wows?: This involves narrowing down the options to focus on the most promising ideas that align with user needs and organizational capabilities.
- What works?: The final stage involves testing the ideas in the real world through prototypes and experiments to refine and implement solutions.
How does "Solving Problems with Design Thinking" suggest measuring the impact of design thinking?
- Behavioral Changes: The book suggests looking for changes in behaviors, conversations, and mind-sets as indicators of design thinking's impact.
- Quantitative Metrics: While challenging, some quantitative metrics like cost savings, increased leads, and customer satisfaction can be tracked.
- Qualitative Insights: Qualitative insights, such as improved employee engagement and customer empathy, are also important measures.
- Long-Term Effects: The book emphasizes patience, as the full impact of design thinking may take time to manifest in measurable outcomes.
What are the challenges of implementing design thinking according to the book?
- Cultural Resistance: Overcoming cultural resistance within organizations is a common challenge when implementing design thinking.
- Fear of Ambiguity: Many managers are uncomfortable with the ambiguity and open-ended nature of the design thinking process.
- Need for Collaboration: Successful implementation requires collaboration across functions, which can be difficult in siloed organizations.
- Measuring Success: Demonstrating the tangible impact of design thinking can be challenging, especially in the short term.
What role do empathy and user-centricity play in design thinking?
- Understanding Needs: Empathy is crucial for understanding the unarticulated needs and desires of users, leading to more relevant solutions.
- Building Connection: A user-centric approach helps build a deeper connection with stakeholders, fostering trust and engagement.
- Guiding Design Criteria: Insights gained from empathy work guide the development of design criteria that shape the solution.
- Driving Innovation: By focusing on real user needs, design thinking drives innovation that is meaningful and impactful.
How does "Solving Problems with Design Thinking" address the role of leadership in design thinking?
- Support and Advocacy: Leadership support is essential for fostering a culture that embraces design thinking and innovation.
- Modeling Behavior: Leaders are encouraged to model design thinking behaviors, such as empathy and experimentation, to inspire others.
- Removing Barriers: Effective leaders work to remove barriers and create an environment that supports collaboration and creativity.
- Vision and Alignment: Leaders play a key role in aligning design thinking efforts with the organization's strategic vision and goals.
What are some best practices for applying design thinking in organizations?
- Start Small: Begin with small projects to build confidence and demonstrate the value of design thinking.
- Involve Stakeholders: Engage a diverse group of stakeholders early in the process to gather insights and build buy-in.
- Iterate and Learn: Embrace an iterative approach, learning from failures and refining solutions through experimentation.
- Provide Training: Offer training and resources to build design thinking competencies across the organization.
What are the best quotes from "Solving Problems with Design Thinking" and what do they mean?
- "Design thinking is not a silver bullet." This quote emphasizes that design thinking is a tool, not a cure-all, and must be applied thoughtfully.
- "Innovation is a team sport." It highlights the importance of collaboration and leveraging diverse perspectives in the innovation process.
- "Stay in the question." This encourages embracing ambiguity and exploring the problem space thoroughly before jumping to solutions.
- "Manufacture your own miracles." It suggests that innovation is about building bridges through disciplined effort, not waiting for sudden breakthroughs.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.