Design Thinking: Method, Process, and What Comes Next

You’ve probably attended a design thinking workshop. Maybe even several. Post-its covered the walls, the energy in the room was high, and the team had genuine insights about your users. And then? Three months later, you’re scrolling through photos of the workshop results on your phone, wondering what actually came of it.

If this pattern sounds familiar, you’re not alone. Design thinking is one of the most influential innovation methods of the last 20 years — and one of the most frequently misunderstood. This article explains what design thinking actually is (and what it isn’t), how the process works, where the method hits its limits, and what organizations need when they want to go beyond the workshop.

What Is Design Thinking — and Why Does It Work?

Jeanne Liedtka spent seven years studying 50 design thinking projects across healthcare, business, and social services. Her central finding: design thinking works because it overcomes three cognitive barriers that are pervasive in organizations.¹ First, user research overrides false assumptions — teams that observe users demonstrably solve different problems than teams that plan from their desks. Second, structured dialogues force people to build on each other’s ideas rather than evaluate them. Third, prototyping and experimentation reduce the fear of change because mistakes are cheap and reversible. Liedtka frames the potential: “Design thinking has the potential to do for innovation exactly what TQM did for manufacturing.”¹

That’s the core: design thinking isn’t a creativity workshop — it’s a structured approach to problem-solving that applies the mindset of designers to complex business and organizational challenges.

The intellectual roots go further back than most introductions suggest. Herbert Simon defined design in 1969 as “devising courses of action aimed at changing existing situations into preferred ones.”² Richard Buchanan expanded the perspective in 1992 to “wicked problems” — ill-defined, interconnected challenges with no single correct solution.³ Kees Dorst developed the concept of “frame innovation” in 2011: designers don’t just create solutions — they create new ways of looking at the problem itself, a capability that proves especially critical for complex organizational challenges.⁴ Tim Brown (IDEO) brought design thinking into the business mainstream in 2008: “A human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.”⁵

Modern practice rests on three elements:

1. Empathy as the starting point: Problems are defined not from the company’s perspective but from the lived experience of users.
2. Divergent-convergent thinking: Phases of expansion (generating many options) alternate systematically with phases of synthesis (selecting the most promising ones).
3. Prototyping before commitment: Ideas are made tangible quickly and cheaply, then tested with users before resources flow into implementation.

The Design Thinking Process

The 5-Phase Model (Stanford d.school)

The best-known model comprises five phases:⁶

Phase	Goal	Core Methods	Common Mistake
Empathize	Understand user needs	Interviews, observation, shadowing, empathy map	The team interviews “experts” instead of actual end users. A product manager at an insurance company is no substitute for the customer navigating the claims process.
Define	Articulate the core problem	Point of view, how-might-we questions	The problem definition is too broad (“How might we improve the customer experience?”) instead of focused (“How might we reduce wait times during claims filing to under 5 minutes?”).
Ideate	Generate solution approaches	Brainstorming, Crazy 8s, SCAMPER	In teams with strong hierarchy, the most senior person’s ideas dominate. Experienced facilitators use silent brainstorming: everyone writes ideas individually before the group discusses.
Prototype	Make ideas tangible	Paper prototyping, storyboards, role-playing	The prototype becomes too polished. A paper model built in 30 minutes tests a hypothesis just as well as a functional click-through dummy that takes a week.
Test	Validate with users	Usability tests, feedback grids	The team tests with colleagues instead of real users. Internal feedback confirms assumptions; external feedback challenges them.

The critical point: the phases aren’t linear. Teams jump back, run phases in parallel, repeat them. A test result can send you back to the Empathize phase because you now understand the problem differently than you did at the start.

When to use which model? Use the 5-phase model when your team has design thinking experience and needs to move fast. Use the 6-phase model (HPI) when your team is analytically strong but empathically inexperienced — the explicit observation phase trains field research capability. Use the Double Diamond (below) when you need a governance framework for a longer innovation initiative, not just a workshop.

The 6-Phase Model (HPI Potsdam)

The Hasso Plattner Institute separates the Empathize phase into two distinct steps:⁷

1. Understand — Explore the design brief, gather assumptions and existing knowledge
2. Observe — Qualitative research methods, interviews, immersion
3. Define point of view — Synthesize insights, build personas, set focus
4. Ideate — Develop solution approaches
5. Prototype — Build concrete solutions (products, services, business models)
6. Test — Test with relevant potential users in iterative cycles

The separation of Understand and Observe makes the distinction between analytical research (what do we know?) and empathic research (what do users experience?) explicit. For organizations whose teams are analytically strong but empathically weak, this separation provides an important training effect.

The Double Diamond

The Double Diamond was developed in 2005 by the British Design Council and expanded in 2019 into the “Framework for Innovation.”⁸ It visualizes the rhythm you experience in design thinking workshops:

First diamond (problem space): Discover → Define

• Diverge: Explore the problem space broadly, challenge assumptions, gather user perspectives
• Converge: Synthesize insights, define the right problem

Second diamond (solution space): Develop → Deliver

• Diverge: Generate many solution approaches, experiment
• Converge: Select the most promising approaches, test, refine

The central insight of the Double Diamond: most projects start in the second diamond — they solve a problem without checking whether it’s the right problem. The first diamond forces you to step back.

Design Thinking Workshop: Formats and Structure

Workshop Formats Compared

Format	Duration	Suited For	Typical Outcome
Crash course	2-4 hours	Introduction, mindset building	Method understanding, no project deliverable
Day workshop	1 day	Focused problem statement, team building	One completed mini-cycle, initial prototypes
Intensive format	2 days	Real project question	Validated user needs, tested prototypes
Design Sprint	5 days	Specific product/service question	Tested high-fidelity prototype9

Workshop Preparation Checklist

Space: Large wall surfaces for post-its, standing tables instead of conference tables, no fixed room setup — the arrangement needs to change with the phases.

Team: 4-6 people per working group, as diverse as possible (business unit, technology, sales, customer service). Roger Martin showed: innovation emerges from the tension between analysis and intuition — homogeneous teams tend toward one side.¹⁰

Materials: Timer, post-its in different colors, thick markers (they force concise phrasing), paper and craft materials for prototyping.

Facilitation: Clear time blocks per phase. Equal speaking time — hierarchy must be actively suspended in the workshop. In DACH companies with pronounced seniority, this requires specific measures: (1) Reverse seniority sharing — junior team members present first, so their ideas aren’t colored by the senior leader’s opinion. (2) Anonymous ideation — everyone writes ideas on post-its before discussion begins. (3) Explicit role agreement before the workshop: “In this room, there is no hierarchy. The CEO has the same voice as the working student.” This agreement must be actively confirmed by the most senior participant — otherwise it remains lip service.

Design Thinking in DACH Companies

The story of design thinking in Germany begins with Hasso Plattner. The SAP co-founder donated $35 million to the Stanford d.school in 2005 and founded the HPI d-school in Potsdam in 2007.¹¹ This gives the DACH region one of the strongest institutional anchors for design thinking worldwide — and, at the same time, a corporate culture that structurally resists the approach.

SAP integrated design thinking into its own product development and SAP implementation methodology through AppHaus innovation centers. The AppHaus locations combine design thinking with Architecture Thinking — an SAP-specific extension that systematically incorporates technical feasibility into the ideation process.¹² The result: design thinking is part of the official SAP blueprinting methodology that thousands of implementation projects worldwide go through. The paradox: SAP consultants practice DT daily — many SAP client companies don’t implement it in their own organizations.

Deutsche Telekom transformed its innovation culture through a design thinking program that permeates all business units. In 2014, the top 200 executives participated in a design sprint with the guiding question: “What could the customer experience look like in 2025?” The consequence: design thinking didn’t remain a one-off experiment but was embedded in the HR Lab as a systematic method — with bottom-up initiatives coming from teams and top-down strategy securing resources and mandates.¹³

Bosch used design thinking to connect previously isolated business units. A medical technology team discovered through user research in India that dentists there were using hardware drills instead of professional dental equipment — an insight that would have remained invisible without empathic field research. The outcome: Bosch developed a new product line for the Indian dental market and simultaneously overhauled its bonus system to reward team performance rather than individual performance — a cultural shift that went far beyond the original DT workshop.¹⁴

What Happens After the Workshop — and What Doesn’t

The DACH experience reveals a recurring pattern: high energy in the workshop, followed by organizational inertia. The reasons are structural:

• Budget processes: Workshop insights rarely fit existing budget cycles. An idea in October has to wait until April, when the next planning cycle begins.
• Hierarchical decision paths: In the workshop, everyone had an equal voice. On Monday morning, the department head decides which ideas get pursued — using criteria from daily operations.
• Missing implementation bridge: Design thinking ends with a validated prototype. Between that prototype and an implemented service lies an ocean of questions: What does the process behind it look like? Who is responsible? How do we measure success? How do we scale?

This implementation gap isn’t a failure of design thinking. It’s the boundary of what design thinking was designed for.

Where Design Thinking Hits Its Limits

Design thinking has real strengths — and equally real limitations. An honest reckoning with both is more helpful than uncritical enthusiasm or blanket dismissal.

Why Design Thinking Fails with Systemic Problems

Design thinking breaks complex problems into user-centered questions. That’s its strength with product and interaction problems. With systemic problems — those involving political, economic, and cultural dimensions — user-centeredness isn’t enough. The MIT Technology Review puts it this way: design thinking reduces systems problems to user-experience problems.¹⁵ An example: when an insurance company improves the claims process through design thinking, it optimizes the user interaction. But when the real problem lies in communication between three internal departments, an external assessor, and regulatory approval, user-centeredness falls short.

Why the Process Lacks Quality Control

“The real culprits are practitioners who exploit the popularity of the movement by selling design thinking as a silver bullet.” — Natasha Jen, Partner at Pentagram¹⁶

Jen’s critique is that the design thinking process is missing a critical element: critique. In design education, every draft is followed by a structured crit — a rigorous peer evaluation. Design thinking has no comparable quality mechanism. The consequence: teams confuse the process with the outcome. Having completed the five phases feels legitimizing — regardless of whether the result is good.

Why Workshop Results Don’t Reach the Organization

“More than two-thirds of mid-size and large product teams claim to use design thinking — but product failure rates haven’t measurably improved.”

Jake Knapp, inventor of the Google Design Sprint, observed this problem already at Google: workshop insights rarely reach production.⁹ The reason: design thinking addresses problem-solving, not organizational change. A day-long workshop can open new perspectives, but it can’t change budget processes, KPI systems, or decision cascades that stand between insight and implementation. Steve Blank calls the result “innovation theater” — activity that demonstrates engagement without producing organizational consequences.¹⁷

Why the Evidence Base Is Thin

Liedtka acknowledges that despite positive results, rigorous management studies on organizational DT outcomes remain scarce.¹ A 2024 meta-analysis confirms positive effects on learning (effect size r = 0.436), but focuses on educational contexts, not corporate environments.¹⁸ Corporate decision-makers who need budget approval for DT programs have little robust ROI data to draw on. A Forrester study on IBM’s Enterprise Design Thinking shows 75 percent more efficient teams and nearly double the development speed — but IBM EDT extends classic DT with governance practices (Hills, Playbacks, Sponsor Users) that make comparison difficult.¹⁹

When Design Thinking Is the Wrong Method

Design thinking isn’t the right choice when the problem is already well-defined (then you need execution, not exploration), when the solution is dictated by regulation or technology, or when the organization has no willingness to let user insights influence decisions. In these cases, design thinking creates expectations it structurally cannot fulfill.

Design Thinking Compared to Other Methods

Criterion	Design Thinking	Service Design	Lean Startup	Design Sprint	Agile
Focus	Understand problem, generate ideas	Design holistic service system	Validate business model	Answer focused product question	Develop incrementally
Timeframe	Days to weeks	Weeks to months	Weeks to months	5 days	Sprints (2-4 weeks)
Output	Prototype, validated insights	Service blueprint, implemented system	MVP, validated business model	Tested prototype	Working increment
Strength	Empathy, creativity, perspective shift	Systems thinking, implementation	Market validation, business logic	Speed, focus	Delivery capability, iteration
Limitation	Ends before implementation	Requires organizational maturity	Assumes problem is known	Limited problem exploration	Assumes clear requirements

Decision guide: Design thinking is the right fit when you don’t yet understand the problem. Service design is the right fit when you need to shape the service system as a whole — from the user experience through backstage processes to organizational anchoring. Lean Startup is the right fit when you need to validate a business model. Design Sprint is the right fit when you want to answer a specific product question in one week.

From Design Thinking to Service Design and Service Innovation

When You Need to Outgrow Design Thinking

Four diagnostic questions help you recognize whether design thinking is sufficient for your initiative — or whether you need the next step:

1. Is it about more than a single touchpoint? If your project isn’t just improving one interaction but involves an end-to-end service with multiple channels, backstage processes, and different user groups, you need service design.
2. Does the solution require organizational change? If workshop insights demand new processes, changed responsibilities, or different KPIs, DT as a method isn’t enough — you need a methodology that thinks through organizational anchoring.
3. Should the result be implemented and operated? Design thinking ends with a validated prototype. If you want to operate a service, you need service blueprinting, operational planning, and governance.
4. Do you want to build a capability, not just run a project? If innovation should be a permanent organizational competency rather than a one-off effort, you need a framework that goes beyond the individual workshop.

If you answer “yes” to two or more of these questions, you’ve reached the point where design thinking has already delivered its greatest value — as an entry point and mindset. The next step: building the capabilities that DT doesn’t cover.

If you’re asking “What now?” after the design thinking workshop, you’re at the right point. Design thinking delivers empathy, creativity, and initial prototypes. What it doesn’t deliver: a well-designed service system that works in a real organization.

Design Thinking → Service Design: Service design takes the DT insights and translates them into a complete system. Where design thinking ends with a tested prototype, service design begins with the question: What does the entire service look like — the user experience (customer journey), the underlying processes (service blueprint), the organizational anchoring? Service design closes the gap between “good idea in the workshop” and “functioning service in the organization.”

Service Design → Service Innovation: Those who want not just to improve a single service but to systematically develop new services as a strategic competency need a framework that goes beyond service design. Service innovation integrates user research, business design, and organizational transformation into a coherent process. It’s no longer about a single workshop or project but about the organizational capability to continuously develop and scale innovative services.

This progression — from mindset through methodology to organizational capability — isn’t a devaluation of design thinking. It’s its natural extension:

Level	What It Delivers	What It Doesn’t Deliver
Design Thinking	Empathy, perspective shift, initial prototypes	Implementation, organizational change
Service Design	Holistic service system, process design, anchoring	Strategic innovation capability at the enterprise level
Service Innovation	Systematic innovation competency, portfolio management, scaling	— (highest maturity level)

Each level builds on the previous one. Those who practice service design without the design thinking mindset produce processes without user understanding. Those who pursue service innovation without service design methodology produce strategy papers without execution capability.

Frequently Asked Questions

What is design thinking in simple terms?

Design thinking is a structured approach to problem-solving that starts with the user: first understand what people truly need (Empathize), then define the core problem (Define), generate many solution ideas (Ideate), build rapid prototypes (Prototype), and test with real users (Test). The process is iterative — results feed into new cycles.

What is the difference between the 5-phase and 6-phase model?

The 5-phase model (Stanford d.school) combines user research into a single phase (Empathize). The 6-phase model (HPI Potsdam) separates it into Understand (analytical research) and Observe (empathic field research). The process is substantively identical; the HPI variant makes the distinction between desk research and field research explicit.

What is the Double Diamond in design thinking?

The Double Diamond (Design Council UK, 2005) visualizes the alternation between divergent and convergent thinking in two phases: the first diamond (Discover → Define) ensures the right problem is identified. The second diamond (Develop → Deliver) solves that problem. Most projects fail because they skip the first diamond — they solve the wrong problem.

What is the difference between design thinking and service design?

Design thinking is a domain-agnostic problem-solving approach that begins with user empathy and ends with validated prototypes. Service design applies this mindset to designing complete service systems — including customer journey, backstage processes, service blueprint, and organizational anchoring. Design thinking provides the mindset; service design provides the methodology for complex service ecosystems.

Which companies use design thinking in Germany?

SAP (integrated into product development and implementation methodology), Deutsche Telekom (company-wide transformation program), Bosch (cross-functional innovation projects), Volkswagen Financial Services (customer journey mapping for financial products), and numerous other DACH companies. The Hasso Plattner Institute in Potsdam is one of the world’s leading training institutions.

Why does design thinking fail in organizations?

Design thinking doesn’t fail as a method — it fails because of organizational conditions: workshop insights don’t reach the decision-making level, budget processes can’t accommodate new ideas, hierarchical structures filter workshop results through operational criteria. Steve Blank calls this “innovation theater” — activity without organizational consequence.¹⁷ The solution lies not in better design thinking but in organizational embedding, as described in anchoring service design in the organization.

How can AI be used in design thinking?

AI changes the speed of individual phases, not the logic of the process. In the Empathize phase, LLMs can analyze thousands of customer reviews, NPS comments, or support tickets and identify patterns that a human team couldn’t find in the available time — a product team at a telco provider could cluster 50,000 customer comments by pain points in minutes instead of spending weeks on manual analysis. In the Ideate phase, LLMs serve as sparring partners: they generate variants, challenge assumptions, and bring perspectives from adjacent industries. In the Prototype phase, image generation tools produce visual concepts faster than manual sketches. AI doesn’t replace the core capabilities of design thinking — empathic field research (an algorithm doesn’t observe body language) and creative synthesis (framing remains a human skill) — but it compresses information processing and expands the space of possible ideas.

Methodology & Sources

This article draws on 19 academic and practitioner sources, including the foundational works of Herbert Simon (1969), Richard Buchanan (1992), Tim Brown (2008), Kees Dorst (2011), and Jeanne Liedtka (2018), the process models of the Stanford d.school and HPI Potsdam, the British Design Council’s Double Diamond (2005/2019), IBM Enterprise Design Thinking, and the DACH corporate examples SAP, Deutsche Telekom, Bosch, and VW Financial Services.

SERP finding: The German-language top-10 results for “Design Thinking” are without exception introductory explainer articles (definition + 5/6 phases + tips). None explains the transition from design thinking to service design, addresses the academic critique with sources, or describes what happens after the workshop within the organization. This article closes these three gaps.

Limitations: The DACH corporate examples (SAP, Telekom, Bosch) come from corporate communications and case studies, not independent research. Quantitative data on DT adoption in the German Mittelstand (mid-market) is scarce. Liedtka’s effectiveness study shows positive effects, but the evidence base for organizational ROI measurement remains thin.

Disclosure: SI Labs supports companies in developing service innovation capabilities. We position design thinking as a valuable foundation, not a silver bullet — and have endeavored to present both strengths and limitations with source-based evidence.

References

Footnotes

1. Liedtka, Jeanne. “Why Design Thinking Works.” Harvard Business Review 96, no. 5 (September-October 2018): 72—79. Based on a seven-year study of 50 projects across healthcare, business, and social services. ↩ ↩² ↩³

2. Simon, Herbert A. The Sciences of the Artificial. MIT Press, 1969. Third edition 1996. Design as “devising courses of action aimed at changing existing situations into preferred ones” (Chapter 5). ↩

3. Buchanan, Richard. “Wicked Problems in Design Thinking.” Design Issues 8, no. 2 (1992): 5—21. Extension of Rittel/Webber’s concept of “wicked problems” to design practice. ↩

4. Dorst, Kees. “The Core of ‘Design Thinking’ and Its Application.” Design Studies 32, no. 6 (2011): 521—532. Concept of “frame innovation”: designers solve problems by creating new frames, not just generating solutions within existing ones. ↩

5. Brown, Tim. “Design Thinking.” Harvard Business Review 86, no. 6 (June 2008): 84—92. The article that established design thinking in the business mainstream. Expanded in: Brown, Tim. Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation. Harper Business, 2009. ↩

6. Stanford d.school. An Introduction to Design Thinking: Process Guide. Hasso Plattner Institute of Design at Stanford, 2010. The canonical description of the 5-phase model. ↩

7. Hasso-Plattner-Institut. Design Thinking Process. Potsdam: HPI School of Design Thinking, 2007ff. The 6-phase model with the explicit separation of Understand and Observe. ↩

8. Design Council UK. The Double Diamond: A Universally Accepted Depiction of the Design Process. London: Design Council, 2005. Updated 2019 to the “Framework for Innovation” with expanded principles. Based on Bela H. Banathy’s divergence-convergence model (1996). ↩

9. Knapp, Jake, John Zeratsky, and Braden Kowitz. Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon & Schuster, 2016. Developed at Google from 2010, refined at Google Ventures from 2012. ↩ ↩²

10. Martin, Roger. The Design of Business: Why Design Thinking Is the Next Competitive Advantage. Harvard Business Press, 2009. Concepts: Knowledge Funnel (Mystery → Heuristic → Algorithm), Reliability vs. Validity as the fundamental tension of organizational innovation. ↩

11. Hasso-Plattner-Institut. HPI School of Design Thinking. Potsdam, 2007. Founded with support from the Hasso Plattner Foundation. Sister institute of the Stanford d.school. ↩

12. SAP AppHaus. Our Approach: Combining Design Thinking with Architecture Thinking. SAP SE, 2024. Over 30,000 Mural licenses for collaborative design across the company. ↩

13. Deutsche Telekom. Design Thinking, Digitization and You. Bonn: Deutsche Telekom AG, 2014. 250+ executives in a design sprint at the Leadership Summit. SDN Case Study: “Design-Driven Transformation Deutsche Telekom.” ↩

14. Bosch and HPI. Documented in: Deutschland.de, “Design Thinking: Innovation in Germany.” User research in India led to new product ideas for dental equipment. Uli Weinberg (HPI d-school director) cited as advisor. ↩

15. Ackermann, Rebecca. “Design thinking was supposed to fix the world. Where did it go wrong?” MIT Technology Review, February 9, 2023. Critical assessment of DT as an innovation method. ↩

16. Jen, Natasha. “Design Thinking is Bullshit.” Talk at the 99U Conference, 2017. Critique of the missing quality mechanism (crit) in the DT process. Documented in: It’s Nice That, Core77, Design Week. ↩

17. Blank, Steve. “Why Companies Do ‘Innovation Theater’ Instead of Actual Innovation.” Harvard Business Review, October 2019. Three types of theater: organizational, innovative, process. ↩ ↩²

18. 2024 meta-analysis: “A meta-analysis of the effect of design thinking on student learning.” Humanities and Social Sciences Communications (Nature), 2024. Positive effect on learning (r = 0.436, p < 0.001), but focused on educational contexts. ↩

19. Forrester Research. The Total Economic Impact of IBM’s Design Thinking Practice. Commissioned Study, 2018. Findings: 75% more efficient teams, nearly double development speed, 2x faster project alignment. Based on IBM’s Enterprise Design Thinking (EDT), which extends classic DT with governance practices (Hills, Playbacks, Sponsor Users). ↩