Loading summary
A
Welcome to HBR on Leadership case studies and conversations with the world's top business and management experts hand selected to help you unlock the best in those around you. I'm HBR Executive Editor Alison Beard. For business leaders, the struggle between efficiency and innovation is constant. How do companies meet their customers needs while also developing new and improved products and services? In the article why Design Thinking Works from the September October 2018 issue of Harvard Business Review, author Jean Liedtke writes, design thinking creates a natural flow from research to rollout. Design thinking immerses the company in their customer's experience, challenges internal biases, and allows for testing and review of new ideas so you know your business is not just making changes, but implementing effective innovations. In this episode, we bring you the narrated version of Liedka's article.
B
Occasionally, a new way of organizing work leads to extraordinary improvements. Total quality management did that in manufacturing in the 1980s by combining a set of tools, kanban cards, quality circles, and so on, with the insight that people on the shop floor could do much higher level work than they usually were asked to. That blend of tools and insight applied to a work process can be thought of as a social technology. In a recent seven year study in which I looked in depth at 50 projects from a range of sectors including business, healthcare and social services, I have seen that another social technology design thinking has the potential to do for innovation exactly what TQM did for manufacturing unleash people's full creative energies, win their commitment, and radically improve processes. By now, most executives have at least heard about design thinking's tools, ethnographic research, an emphasis on reframing problems and experimentation, the use of diverse teams, and so on if not tried them. But what people may not understand is the subtler way that design thinking gets around the human biases, for example Rootedness in the status quo or attachments to specific behavioral norms. That's how we do things here that, time and again, block the exercise of imagination. In this article, I'll explore a variety of human tendencies that get in the way of innovation and describe how design thinking's tools and clear process steps help teams break free of them. Let's begin by looking at what organizations need from innovation and at why their efforts to obtain it often fall short. To be successful, an innovation process must deliver three superior solutions, lower risks and costs of change, and employee buy in. Over the years, business people have developed useful tactics for achieving those outcomes. But when trying to apply them, organizations frequently encounter new obstacles and trade offs superior solutions. Defining problems in obvious, conventional ways, not surprisingly, often leads to obvious conventional solutions. Asking a more interesting question can help teams discover more original ideas. The risk is that some teams may get indefinitely hung up exploring a problem, while action oriented managers may be too impatient to take the time to figure out what question they should be asking. It's also widely accepted that solutions are much better when they incorporate user driven criteria. Market research can help companies understand those criteria, but the hurdle here is that it's hard for customers to know they want something that doesn't yet exist. Finally, bringing diverse voices into the process is also known to improve solutions. This can be difficult to manage, however, if conversations among people with opposing views deteriorate into divisive debates, lower risks and costs. Uncertainty is unavoidable in innovation. That's why innovators often build a portfolio of options. The trade off is that too many ideas dilute focus and resources. To manage this tension, innovators must be willing to let go of bad ideas to call the baby ugly. As a manager in one of my studies described it unfortunately, people often find it easier to kill the creative and arguably riskier ideas and than to kill the incremental ones. Employee buy in an innovation won't succeed unless a company's employees get behind it. The surest route to winning their support is to involve them in the process of generating ideas. The danger is that the involvement of many people with different perspectives will create chaos and incoherence. Underlying the trade offs associated with achieving these outcomes is a more fundamental tension. In a stable environment, efficiency is achieved by driving variation out of the organization. But in an unstable world, variation becomes the organization's friend because it opens new paths to success. However, who can blame leaders who must meet quarterly targets for doubling down on efficiency, rationality, and centralized control? To manage all the trade offs, organizations need a social technology that addresses these behavioral obstacles as well as the counterproductive biases of human beings. And as I'll explain next, design thinking fits that bill. Experienced designers often complain that design thinking is too structured and linear, and for them that's certainly true. But managers on innovation teams generally are not designers and also aren't used to doing face to face research with customers, getting deeply immersed in their perspectives, co creating with stakeholders, and designing and executing experiments. Structure and linearity help managers try to adjust to these new behaviors. As Karen Hansen, formerly the head of design innovation at Intuit and now Facebook's design product director, has explained, anytime you're trying to change people's behavior, you need to start them off with a lot of structure so they don't have to think. A lot of what we do is habit, and it's hard to change those habits. But having very clear guardrails can help us. Organized processes keep people on track and curb the tendency to spend too long exploring a problem or to impatiently skip ahead. They also instill confidence. Most humans are driven by a fear of mistakes, so they focus more on preventing errors than on seizing opportunities. They opt for inaction rather than action when a choice risks failure. But there is no innovation without action, so psychological safety is essential. The physical props and highly formatted tools of design thinking deliver that sense of security. Helping would be Innovators move more assuredly through the discovery of customer needs, idea generation and idea testing in most organizations, the application of design thinking involves seven activities. Each generates a clear output that the next activity converts to another output until the organization arrives at an implementable innovation. But at a deeper level, something else is happening, something that executives generally are not aware of. Though ostensibly geared to understanding and molding the experiences of customers, each design thinking activity also reshapes the experiences of the innovators themselves in profound ways.
C
Meet Rovo, your AI powered teammate Rovo connects to your organization's knowledge and lives on Atlassian's trusted and secure platform. Connect Rovo to your favorite SaaS apps to get the personalized context you need. Unleash AI with AI powered search, chat, agents and studio. Get started with Rovo, your new AI teammate powered by Atlassian@rovo.com.
B
Many of the best known methods of the design thinking discovery process relate to identifying the job to be done done. Adapted from the fields of ethnography and sociology, these methods concentrate on examining what makes for a meaningful customer journey rather than on the collection and analysis of data. This exploration entails three sets of activities. Immersion Traditionally, customer research has been an impersonal exercise. An expert who may well have pre existing theories about customer preferences, reviews, feedback from focus groups, surveys and, if available, data on current behavior and draws inferences about needs. The better the data, the better the inferences. The trouble is, this grounds people in the already articulated needs that the data reflects. They see the data through the lens of their own biases and they don't recognize needs people have not expressed. Design thinking takes a different approach. Identify hidden needs by having the innovator live the customer's experience. Consider what happened at the Kingwood Trust, a UK charity helping adults with autism and Asperger's syndrome. One design team member, Katie Gaudion, got to know Pete, a nonverbal adult with autism, the first time she observed him at his home, she saw him engaged in seemingly damaging acts, like picking at a leather sofa and rubbing indents in a wall. She started by documenting Pete's behavior and defined the problem as how to prevent such destructiveness. But on her second visit to Pete's home, she asked herself, what if Pete's actions were motivated by something other than a destructive impulse? Putting her personal perspective aside, she mirrored his behavior and discovered how satisfying his activities actually felt. Instead of a ruined sofa, I now perceived Pete's sofa as an object wrapped in fabric that is fun to pick, she explained. Pressing my ear against the wall and feeling the vibrations of the music above, I felt a slight tickle in my ear whilst rubbing the smooth and beautiful indentation. So instead of a damaged wall, I perceived it as a pleasant and relaxing audio tactile experience. Katie's immersion in Pete's world not only produced a deeper understanding of his challenges, but called into question an unexamined bias about the residents who had been perceived as disability sufferers that needed to be kept safe. Her experience caused her to ask herself another new Instead of designing just for residents, disabilities and safety, how could the innovation team design for their strengths and pleasures that led to the creation of living spaces, gardens and new activities aimed at enabling people with autism to live fuller and more pleasurable lives? Sense Making immersion in user experiences provides raw material for deeper insights, but finding patterns and making sense of the mass of qualitative data collected is a daunting challenge. Time and again I have seen initial enthusiasm about the results of ethnographic tools fade as non designers become overwhelmed by the volume of information and the messiness of searching for deeper insights. It is here that the structure of design thinking really comes into its own. One of the most effective ways to make sense of the knowledge generated by immersion is a design thinking exercise called the Gallery Walk. In it, the core innovation team selects the most important data gathered during the discovery process and writes it down on large posters. Often these posters showcase individuals who have been interviewed, complete with their photos and quotations, capturing their perspectives. The posters are hung around a room and key stakeholders are invited to tour this gallery and write down on post it notes the bits of data they consider essential to new designs. The stakeholders then form small teams and in a carefully orchestrated process, their posted observations are shared, combined and sorted by theme into clusters that the group mines for insights. This process overcomes the danger that innovators will be unduly influenced by their own biases and see only what they want to see because it makes the people who were interviewed feel vivid and real to those browsing the gallery. It creates a common database and facilitates collaborators ability to interact, reach shared insights together, and challenge one another's individual takeaways. Another critical guard against biased interpretations. Alignment the final stage in the discovery process is a series of workshops and seminar discussions that ask in some form the question, if anything were possible, what job would the design do well? The focus on possibilities, rather than on the constraints imposed by the status quo helps diverse teams have more collaborative and creative discussions about the design criteria or the set of key features that an ideal innovation should have. Establishing a spirit of inquiry deepens dissatisfaction with the status quo and makes it easier for teams to reach consensus throughout the innovation process and down the road. When the portfolio of ideas is winnowed, agreement on the design criteria will give novel ideas a fighting chance against safer, incremental ones. Consider what happened at Monash Health, an integrated hospital and healthcare system in Melbourne, Australia. Mental health clinicians there had long been concerned about the frequency of patient relapses, usually in the form of drug overdoses and suicide attempts, but consensus on how to address this problem eluded them. In an effort to get to the bottom of it, clinicians trace the experiences of specific patients through the treatment process. One patient, Tom, emerged as emblematic in their study. His experience included three face to face visits with different clinicians, 70 touch points, 13 different case managers, and 18 handoffs. During the interval between his initial visit and his relapse, the team members held a series of workshops in which they asked clinicians this Did Tom's current care exemplify why they had entered healthcare? As people discussed their motivations for becoming doctors and nurses, they came to realize that improving Tom's outcome might depend as much on their sense of duty to Tom himself as it did on their clinical activity. Everyone bought into this conclusion, which made designing a new treatment process centered on the patient's needs rather than perceived best practices proceeds smoothly and successfully. After its implementation, patient relapse rates fell by 60%. Once they understand customers needs, innovators move on to identify and winnow down specific solutions that conform to the criteria they've identified. Emergence the first step here is to set up a dialogue about potential solutions, carefully planning who will participate, what challenge they will be given, and how the conversation will be structured. After using the design criteria to do some individual brainstorming, participants gather to share ideas and build on them creatively, as opposed to simply negotiating compromises when differences arise. When Children's Health System of Texas, the sixth largest pediatric medical center in The United States identified the need for a new strategy. The organization, led by the vice president of Population Health, Peter Roberts, applied design thinking to reimagine its business model. During the discovery process, clinicians set aside their bias that what mattered most was medical intervention. They came to understand that intervention alone wouldn't work if the local population in Dallas didn't have the time or ability to seek out medical knowledge and didn't have strong support networks, something few families in the area enjoyed. The clinicians also realized that the medical center couldn't successfully address problems on its own. The community would need to be central to any solution. So Children's Health invited its community partners to code sign a new wellness ecosystem whose boundaries and resources would stretch far beyond the medical center. Deciding to start small and tackle a single condition, the team gathered to create a new model for managing asthma. The session brought together hospital administrators, physicians, nurses, social workers, parents of patients, and staff from Dallas's school districts, housing authority, ymca, and faith based organizations. First, the core innovation team shared learning from the discovery process. Next, each attendee thought independently about the capabilities that his or her institution might contribute toward addressing the children's problems, jotting down ideas on sticky notes. Then, each attendee was invited to join a small group at one of five tables where the participants shared individual ideas, grouped them into common themes, and envisioned what an ideal experience would look like for the young patients and their families. Champions of change usually emerge from these kinds of conversations, which greatly improves the chances of successful implementation. All too often, good ideas die on the vine in the absence of people with a personal commitment to making them happen. At Children's Health, the partners invited into the project galvanized the community to act and forged and maintained the relationships in their institutions required to realize the new vision. Housing Authority representatives drove changes in housing codes, charging inspectors with incorporating children's health issues like the presence of mold into their assessments. Local pediatricians adopted a set of standard asthma protocols, and parents of children with asthma took on a significant role as peer counselors, providing intensive education to other families through home visits. Articulation Typically, emergence activities generate a number of competing ideas, more or less attractive and more or less feasible. In the next step, articulation innovators surface and question their implicit assumptions. Managers are often bad at this because of many behavioral biases, such as over optimism, confirmation bias, and fixation on first solutions. When assumptions aren't challenged, discussions around what will or won't work become deadlocked, with each person advocating from his or her own understanding of how the world works. In contrast. Design thinking frames the discussion as an inquiry into what would have to be true about the world for an idea to be feasible. See Management Is Much More Than a Science By Roger L. Martin and Tony Golsby Smith, HBR September October 2017. An example of this comes from the IGNITE Accelerator program of the U.S. department of Health and Human Services at the White River Indian Reservation Hospital in Arizona. A team led by Marlisa Rivera, a young quality control officer, sought to reduce wait times in the hospital's emergency room, which were sometimes as long as six hours. The team's initial concept, borrowed from Johns Hopkins Hospital in Baltimore, was to install an electronic kiosk for check in. As team members began to apply design thinking, however, they were asked to surface their assumptions about why the idea would work. It was only then that they realized that their patients, many of whom were elderly Apache speakers, were unlikely to be comfortable with computer technology. Approaches that worked in urban Baltimore would not work in White river, so this idea could be safely set aside. At the end of the idea generation process, innovators will have a portfolio of well thought through, though possibly quite different, ideas. The assumptions underlying them will have been carefully vetted and the conditions necessary for their success will be achievable. The ideas will also have the support of committed teams who will be prepared to take on the responsibility of bringing them to market. Companies often regard prototyping as a process of fine tuning a product or service that has already largely been developed. But in design thinking, prototyping is carried out on far from finished products. It's about users iterative experiences with a work in progress. This means that quite radical changes, including complete redesigns, can occur along the way. Pre Experience Neuroscience research indicates that helping people pre experience something novel, or to put it another way, imagine it incredibly vividly, results in more accurate assessments of the novelty's value. That's why design thinking calls for the creation of basic, low cost artifacts that will capture the essential features of the proposed user experience. These are not literal prototypes, and they are often much rougher than the minimum viable products that lean startups test with customers. But what these artifacts lose in fidelity, they gain in flexibility because they can easily be altered in response to what's learned by exposing users to them and their incompleteness invites interaction. Such artifacts can take many forms. The layout of a new medical office building at Kaiser Permanente, for example, was tested by hanging bedsheets from the ceiling to mark future walls. Nurses and physicians were invited to interact with staffers who were playing the role of patients and and to suggest how spaces could be adjusted to better facilitate treatment. At Monash Health, a program called Monash Watch, aimed at using telemedicine to keep vulnerable populations healthy at home and reduce their hospitalization rates, used detailed storyboards to help hospital administrators and government policymakers envision this new approach in practice without building a digital prototype. Learning in Action Real world experiments are an essential way to assess new ideas and identify the changes needed to make them workable. But such tests offer another, less obvious kind of value. They help reduce employees and customers quite normal fear of change Consider an idea proposed by Don Campbell, a professor of medicine, and Keith Stockman, a manager of operations research at Monash Health. As part of Monash Watch, they suggested hiring laypeople to be telecare guides who would act as professional neighbors, keeping infrequent telephone contact with patients at high risk of multiple hospital admissions. Campbell and Stockman hypothesized that lower wage laypeople who were carefully selected, trained in health literacy and empathy skills, and backed by a decision support system and professional coaches they could involve as needed, could help keep the at risk patients healthy at home. Their proposal was met with skepticism. Many of their colleagues held a strong bias against letting anyone besides a health professional perform such a service for patients with complex issues, but using health professionals in the role would have been unaffordable. Rather than debating this point, however, the innovation team members acknowledged the concerns and engaged their colleagues in the code sign of an experiment testing that assumption. Three hundred patients later, the results were in overwhelmingly positive patient feedback, and a demonstrated reduction in bed use and emergency room visits corroborated by independent consultants, quelled the fears of the skeptics. As we have seen, the structure of design thinking creates a natural flow from research to rollout. Immersion in the customer experience produces data which is transformed into insights which help teams agree on design criteria they use to brainstorm solutions. Assumptions about what's critical to the success of those solutions are examined and then tested with rough prototypes that help teams further develop innovations and prepare them for real world experiments. Along the way, design thinking processes counteract human biases that thwart creativity while addressing the challenges typically faced in reaching superior solutions, lowered costs and risks, and employee buy in recognizing organizations as collections of human beings who are motivated by varying perspectives and emotions, design thinking emphasizes engagement, dialogue, and learning. By involving customers and other stakeholders in the definition of the problem and the development of solutions, design thinking garners a broad commitment to change. And by supplying a structure to the innovation process, design thinking helps innovators collaborate and agree on what is essential to the outcome at every phase. It does this not only by overcoming workplace politics, but by shaping the experiences of the innovators and of their key stakeholders and implementers at every step. That is Social technology at work. You were listening to why Design Thinking Works by Jean Litka Jean Liedka is a professor of Business Administration at the University of Virginia's Darden School of Business.
A
HBR on Leadership will be back next Wednesday with another hand picked conversation from Harvard Business Review. If this episode helped, you, share it with your friends and colleagues and follow the show on Apple Podcasts, Spotify or wherever you listen while you're there, consider leaving us a review. And when you're ready for more podcasts, articles, case studies, books and videos with the world's top business and management experts, find it all@hbr.org OnLeadership's team includes Maureen Hoch, Rob Eckhart, Erica Truxler, Tina Toby Mack, Ramsey Kabaz, Nicole Smith and Ann Bartholomew. Music by Coma Media I'm Alison Beard and thanks for listening.
Date: October 29, 2025
Host: Alison Beard (HBR Executive Editor)
Narrated Article: "Why Design Thinking Works" by Jean Liedtka
This episode explores how design thinking can help organizations break free from the tension between efficiency and innovation. Narrated by HBR, the episode is a deep dive into Jean Liedtka’s influential article, “Why Design Thinking Works,” which argues that design thinking drives effective innovation by immersing companies in customer experience, challenging internal biases, promoting experimentation, and facilitating broad buy-in. Liedtka draws on case studies from business, healthcare, and social services to illustrate design thinking as a “social technology” that unleashes creativity and commitment in teams, improving outcomes while lowering the risks and costs associated with change.
Innovation Outcomes Needed (03:00):
Why Efforts Often Fall Short:
“Defining problems in obvious, conventional ways...often leads to obvious conventional solutions. Asking a more interesting question can help teams discover more original ideas.”
— Jean Liedtka [03:50]
Reference to Total Quality Management (TQM) (01:10):
Design Thinking is compared to TQM in how it integrates tools and insights into a “social technology” that shapes behavior and unleashes creativity.
Addresses Biases:
Design thinking helps organizations get around status quo thinking, and other human biases, by introducing new structured behaviors.
“Design thinking has the potential to do for innovation exactly what TQM did for manufacturing: unleash people’s full creative energies, win their commitment, and radically improve processes.”
— Jean Liedtka [01:25]
Structure & Linearity (06:00):
Non-designers benefit from clear, structured processes that help them navigate the unfamiliar tasks of research, co-creation, and prototyping.
“Anytime you’re trying to change people’s behavior, you need to start them off with a lot of structure so they don’t have to think.”
— Karen Hansen, Intuit/Facebook [06:40, as quoted by Liedtka]
Immersion (08:30):
Innovators “live the customer’s experience” to identify hidden needs, moving beyond data to empathy.
“Design thinking takes a different approach: identify hidden needs by having the innovator live the customer’s experience.”
— Jean Liedtka [08:40]
“Pressing my ear against the wall and feeling the vibrations of the music above...I now perceived Pete’s sofa as an object wrapped in fabric that is fun to pick.”
— Katie Gaudion [09:35]
Sense-Making (11:30):
Tools like the “Gallery Walk” allow teams to surface patterns in ethnographic data and overcome individual bias.
Alignment (13:00): Workshops focus on possibilities, not constraints, helping teams reach consensus on design criteria.
Structured Ideation (15:30):
Diverse stakeholders brainstorm and build on each other’s ideas for holistic solutions.
“Champions of change usually emerge from these kinds of conversations, which greatly improves the chances of successful implementation.”
— Jean Liedtka [18:45]
Challenging Bias and Assumptions (19:30):
Design thinking asks: What would have to be true for this idea to work? This frames discussion as inquiry, not advocacy.
Low-Cost, Incomplete Prototypes (21:00):
Prototypes are designed to be rough, flexible, and invite user interaction—mirroring real-life conditions for feedback and iteration.
Iterative Experimentation (22:15): Encouraging learning through real-world experiments, which both test feasibility and reduce fear of change.
“Three hundred patients later, the results were in: overwhelmingly positive patient feedback, and a demonstrated reduction in bed use and emergency room visits...”
— Jean Liedtka [23:45]
| Segment | Topic | Timestamp | |-----------------------------------|----------------------------------------------------|------------| | Episode Theme & Setup | Definition and introduction of design thinking | 00:03–01:00| | Why Companies Struggle | Biases, trade-offs, and the need for structure | 01:00–07:43| | The Discovery Process | Immersion, sense-making, alignment (with cases) | 08:17–15:30| | Ideation and Community Engagement | Emergence of champions, Children’s Health case | 15:30–18:45| | Challenging Assumptions | Articulation, IGNITE Case Example | 19:30–21:00| | Prototyping & Pre-Experience | Rough prototypes, Kaiser Permanente, Monash Watch | 21:00–22:45| | Learning in Action | Experimentation, Monash Lay Health Coaches case | 22:15–24:30| | Recap & Broader Implications | Social technology, buy-in, employee experience | 24:30–25:50|
Throughout, the episode maintains a practical, research-driven yet accessible tone—combining case study narratives, practitioner quotes, and the step-by-step clarity Jean Liedtka is known for. The mood is encouraging and focused on overcoming real-world organizational and human barriers to creativity.
The episode concludes with a clear message: Design thinking changes not just the solutions organizations generate, but also the way innovators and stakeholder teams experience the work of innovation. By combining structure, empathy, engagement, and intentional dialogue, organizations can break through old habits and realize more impactful, actionable creativity.
For leaders and teams seeking actual change—not just new ideas—this episode details why and how design thinking works.