top of page

Common Design Thinking Myths

Updated: Jan 29

Despite decades of research and proven results, Design Thinking faces persistent myths and misconceptions that create barriers to effective implementation. These misunderstandings range from concerns about artistic abilities to skepticism about business relevance.


Understanding and addressing these misconceptions is crucial for anyone seeking to introduce Design Thinking to their organization or overcome resistance from stakeholders who may have heard conflicting information.


Hands gesturing over a laptop, tablet, and phone in a modern office. Visible screen displays with digital graphics, conveying business focus.

The "Creativity" Myths


Myth #1 "Design Thinking Is Only for Creative People"


The Misconception: Design Thinking requires artistic talent, creative flair, or "right-brain" thinking that only certain personality types possess.


The Reality: Design Thinking is not about artistic creativity. It's about problem-solving creativity—the ability to approach challenges from new angles and generate multiple solutions.


As we explored in the Who Are Design Thinkers post, the six Design Thinking capabilities are innate human abilities that everyone possesses to varying degrees. You don't need to be able to draw, design graphics, or consider yourself "artistic" to be an effective Design Thinker.


What This Means: Engineers, accountants, project managers, and operations specialists can be exceptional Design Thinkers. Some of the most effective Design Thinkers I've worked with come from highly analytical backgrounds.


How to Address: Focus on problem-solving examples rather than creative outputs. Show how Design Thinking helps solve logical challenges through systematic exploration.


Myth #2: "We're Not Creative Types"


The Misconception: Entire teams or organizations believe they lack the creative capacity for Design Thinking because their work is technical, analytical, or operational.


The Reality: Every human brain is capable of both analytical and creative thinking. The issue isn't capability—it's confidence and practice. Many "non-creative" professionals have simply never been encouraged to use their creative problem-solving abilities.


What This Means: Organizations often have untapped creative problem-solving potential in unexpected places. The quiet analyst who always finds alternative solutions or the operations manager who improvises elegant workarounds may be natural Design Thinkers.


How to Address: Start with small, low-risk challenges that demonstrate creative problem-solving in familiar contexts. Build confidence before tackling larger initiatives.


The "Fluffiness" Myths


Myth #3: "Design Thinking Is Just Fluffy Brainstorming"


The Misconception: Design Thinking is unstructured, feel-good activity that lacks rigor and doesn't produce concrete business results.


The Reality: Effective Design Thinking is highly structured and rigorous. It requires disciplined attention to human needs, systematic exploration of possibilities, and careful evaluation of solutions against desirability, viability, and feasibility criteria.


As we saw in Post #1, Design Thinking balances creative and analytical thinking. The analytical component is just as important as the creative component.


What This Means: Design Thinking sessions should produce concrete outputs: clear problem definitions, testable prototypes, actionable next steps, and measurable outcomes.


How to Address: Emphasize the analytical rigor, show concrete deliverables, and connect activities to business outcomes. Focus on the systematic methodology rather than just the collaborative aspects.


Myth #4: "It's Just About Sticky Notes and Workshops"


The Misconception: Design Thinking is primarily a workshop format involving sticky notes, whiteboards, and team-building activities.


The Reality: While workshops can be useful, Design Thinking is fundamentally about developing problem-solving capabilities and mindsets that apply across all work contexts.


As emphasized in Post #5, the real value comes from building capabilities rather than just conducting activities. The sticky notes are tools, not the goal.


What This Means: Effective Design Thinking becomes embedded in how people approach challenges daily, not just in special sessions or workshops.


How to Address: Demonstrate how Design Thinking capabilities apply to everyday work challenges. Show examples of individual application rather than just group activities.


The "Business Relevance" Myths


Myth #5: "Design Thinking Doesn't Work for Serious, Complex Business Challenges"


The Misconception: Design Thinking only applies to consumer products, simple challenges, or problems involving obvious human interaction.


The Reality: Some of the most powerful Design Thinking applications involve complex B2B challenges, technical problems, and systemic organizational issues.

My research includes successful applications in:

  • Manufacturing process optimization

  • Financial services compliance

  • Healthcare system redesign

  • Technology infrastructure planning

  • Regulatory change management


What This Means: The human-centered approach applies wherever humans are involved in creating, implementing, or using solutions—which covers virtually all business challenges.


How to Address: Share examples of Design Thinking applied to problems similar to those your audience faces. Emphasize the human elements in seemingly technical challenges.


Myth #6: "It Takes Too Long and Costs Too Much"


The Misconception: Design Thinking requires extensive time investment, expensive facilitators, and lengthy processes that delay decision-making.


The Reality: Effective Design Thinking often reduces overall project time and cost by preventing expensive mistakes and ensuring solutions actually work for their intended users.


As demonstrated in the Fonterra case study mentioned in Post #5, Design Thinking approaches can solve complex challenges in weeks rather than months or years.


What This Means: The upfront investment in understanding and testing prevents downstream costs of failed implementations, user resistance, and solution redesign.


How to Address: Compare total project costs including failure costs, not just upfront design costs. Show examples of rapid results and prevented failures.


The "Effectiveness" Myths


Myth #7: "Design Thinking Is Just a Fad That Will Pass"


The Misconception: Design Thinking is the latest management trend that will be replaced by the next big thing, making investment unwise.


The Reality: As we explored in Post #3, Design Thinking has 60+ years of academic research behind it and addresses fundamental human problem-solving capabilities that won't become obsolete.

The core insight from Herbert Simon in 1969 remains relevant: design is concerned with transforming current situations into better ones. Until we create a world without problems, this capability will be valuable.


What This Means: While specific methodologies may evolve, the underlying capabilities and approaches represent durable competitive advantages.


How to Address: Emphasize the research foundation and long-term relevance. Focus on capability development rather than methodology adoption.


Myth #8: "We Tried Design Thinking and It Didn't Work"


The Misconception: Previous negative experiences with Design Thinking prove it's ineffective for the organization or type of work.


The Reality: Most failed Design Thinking initiatives suffer from the problems we identified in Post #5: focus on process rather than capabilities, lack of environmental support, or misapplication to inappropriate challenges.

As we discussed in Post #4, different types of problems require different approaches. Design Thinking isn't appropriate for every challenge.


What This Means: Previous failures often indicate implementation issues rather than fundamental methodology problems.


How to Address: Diagnose what went wrong in previous attempts. Address capability development, environmental factors, and appropriate application rather than dismissing the entire approach.


The "Scope" Myths


Myth #9: "Design Thinking Is Only for Innovation Projects"


The Misconception: Design Thinking should be reserved for special innovation initiatives, new product development, or designated "creative" projects.


The Reality: Design Thinking capabilities apply to any challenge involving human needs, complex stakeholder dynamics, or uncertain solutions—which covers most organizational challenges.

Applications include:

  • Change management initiatives

  • Process improvement projects

  • Technology implementations

  • Strategic planning processes

  • Conflict resolution situations


What This Means: Design Thinking capabilities enhance everyday problem-solving rather than just special innovation work.


How to Address: Show how Design Thinking capabilities improve routine work challenges. Demonstrate applications beyond product innovation.


Myth #10: "You Need Special Training to Use Design Thinking"


The Misconception: Design Thinking requires extensive certification, specialized training, or expert facilitators to be effective.


The Reality: While training helps, the core capabilities are innate human abilities that can be developed through practice and environmental support.

Many people naturally demonstrate Design Thinking capabilities without formal training. The goal is recognizing and developing existing strengths rather than learning entirely new skills.


What This Means: Organizations can build Design Thinking capability through coaching, practice, and supportive environments rather than just formal training programs.


How to Address: Emphasize capability development over certification. Show examples of natural Design Thinkers who've never taken formal training.


The "Scale" Myths


Myth #11: "Design Thinking Only Works for Small Teams"


The Misconception: Design Thinking approaches become unwieldy or ineffective with large groups, complex organizations, or enterprise-scale challenges.


The Reality: Design Thinking principles and capabilities scale effectively when properly applied. Large organizations successfully use Design Thinking approaches for system-wide transformations.

The key is adapting application methods rather than abandoning the approach. Capabilities like empathetic exploration and collective collaboration become more important, not less important, at larger scales.


What This Means: Scaling requires different techniques but the same underlying capabilities. Large organizations can develop Design Thinking capabilities across multiple levels and departments.


How to Address: Share examples of large-scale applications. Focus on capability development across the organization rather than just team-level workshops.


Myth #12: "Senior Leaders Don't Need to Understand Design Thinking"


The Misconception: Design Thinking is a tactical approach for project teams rather than a strategic capability requiring leadership understanding and support.


The Reality: Leadership understanding and support are crucial for creating environments where Design Thinking capabilities can flourish. Without this support, even well-trained teams struggle to apply their capabilities effectively.

As we learned from the capability research, environmental factors significantly influence capability expression. Leadership behavior is one of the most important environmental factors.


What This Means: Successful Design Thinking implementation requires leadership engagement at multiple levels, not just team training.


How to Address: Emphasize the strategic value and leadership role in creating supportive environments. Show how leadership behavior enables or hinders capability development.


Addressing Misconceptions Effectively


Understanding the Source

Most misconceptions arise from:

  • Limited exposure to well-implemented Design Thinking

  • Bad experiences with poorly facilitated workshops

  • Media oversimplification that emphasizes tools over capabilities

  • Consulting approaches that focus on process delivery rather than capability development

  • Cultural biases that undervalue collaborative or experimental approaches


Strategies for Response

Lead with Examples Share concrete examples of Design Thinking applied to challenges similar to those your audience faces. Make it relevant and relatable.

Address Specific Concerns Listen for the underlying worry behind the misconception. Are they concerned about time, cost, effectiveness, or relevance? Address the real concern, not just the surface objection.

Start Small Propose low-risk applications that demonstrate value without requiring major organizational commitment. Build credibility through results.

Focus on Capabilities Emphasize capability development rather than methodology adoption. Help people recognize Design Thinking capabilities they may already possess.

Show the Research Reference the 60+ years of academic foundation and proven business results. Design Thinking isn't experimental—it's evidence-based.

Connect to Current Challenges Demonstrate how Design Thinking addresses specific problems the organization currently faces rather than abstract future possibilities.


The Path Forward


For Individual Advocates

If you're introducing Design Thinking to skeptical colleagues:

  • Understand their perspective and legitimate concerns

  • Start with their problems rather than Design Thinking theory

  • Show rather than tell through small demonstrations

  • Build on existing strengths they already demonstrate

  • Connect to business outcomes they care about


For Organizational Champions

If you're building organizational Design Thinking capability:

  • Address misconceptions systematically rather than hoping they'll disappear

  • Create positive experiences that counter negative associations

  • Develop internal examples that demonstrate relevant applications

  • Build capability gradually rather than expecting immediate transformation

  • Measure and communicate results to counter skepticism with evidence


For Leadership Teams

If you're considering organizational Design Thinking investment:

  • Understand what you're really buying (capabilities vs. processes vs. tools)

  • Set appropriate expectations for timeline and outcomes

  • Create supportive environments rather than just providing training

  • Measure capability development alongside project outcomes

  • Model the behaviors you want to see throughout the organization


Key Takeaways

  1. Most misconceptions stem from limited exposure to well-implemented Design Thinking or bad experiences with poor implementations

  2. Address underlying concerns rather than just surface objections when encountering resistance

  3. Start with relevant applications that demonstrate value in familiar contexts before expanding to new areas

  4. Focus on capability development rather than methodology adoption to overcome skepticism about training and certification

  5. Leadership understanding and support are crucial for creating environments where Design Thinking can succeed

  6. Evidence and examples are more persuasive than theoretical arguments when addressing misconceptions


Conclusion: Moving Beyond Myths to Mastery

Understanding and addressing these common myths and misconceptions is essential for anyone seeking to introduce or improve Design Thinking in their organization. The goal isn't to convince everyone that Design Thinking is perfect for every situation, but to clear away the barriers that prevent thoughtful consideration and effective application.


As we've seen throughout this series, Design Thinking is:

  • A proven approach with solid research foundations

  • Applicable to a wide range of organizational challenges

  • Based on innate human capabilities that can be developed

  • Most effective when focused on capability building rather than just process following

  • Valuable for both innovation and everyday problem-solving


The myths and misconceptions often reflect real concerns about time, resources, relevance, and effectiveness. By addressing these concerns directly and demonstrating Design Thinking's value through relevant examples and appropriate applications, we can help organizations move beyond skepticism to productive implementation.





Comments


bottom of page