Design thinking is a process that starts with empathy, curiosity and imagination to create solutions. It has a goal to make the world a better place while addressing current human needs. In this blog post, we’ll explore the Core Principles of Design Thinking Process and the steps involved in developing innovative solutions. Learn how you can apply this method in your business.
A problem-solving approach means that you work through challenges in your business and come up with solutions. These are then applied to your products and services, which helps get you closer to your customers.
In the past, businesses have concentrated on enhancing the functionality and looks of their product to improve sales. But that approach is quickly changing and enhancements are not just about aesthetics.
Businesses want to create a meaningful connection with their customers, and the best way they know how are they constantly asking for feedback. When they listen to what customers need, it’s easier than ever to design services and products that help businesses achieve their goals.
Organizations are always innovating to stay ahead of their competition. Across every industry, organizations want actionable, practical, and innovative solutions that meet their needs. Uber Business Model is a perfect example of disruptive innovation — an improvement in the process of hailing a cab.
However, innovation can’t end there. Game changers Taxi Business like Uber and Airbnb face the challenge of continuous innovation to rank higher in their respective markets. Innovation needs to be a part of the company culture. That’s where design thinking comes in.
| Quick answer: Design thinking is a human-centered, iterative approach to solving problems. Its process has five stages: Empathize, Define, Ideate, Prototype, and Test. It is guided by principles such as user focus, collaboration, experimentation, and iteration. Teams use it to build products people actually need, before investing heavily in development. |
What Is Design Thinking?
Design thinking is a human-centered, iterative method for solving complex or poorly defined problems. Teams understand users deeply, generate many ideas, and validate them through prototypes and testing. It is closely related to the human-centered design process used across UX and product design.
The approach grew out of design research in the 1960s and was popularized by IDEO and taught at the Stanford d.school, whose five-stage model is the most widely used version today.
A common way to evaluate any solution is IDEO’s three lenses. Strong solutions sit where all three overlap:
| Lens | Question it answers |
|---|---|
| Desirability | Do people actually want this? |
| Feasibility | Can we build it with available technology and skills? |
| Viability | Can it sustain a business or organization over time? |
Many teams add a fourth check, sustainability, to consider long-term social and environmental impact.
Why Design Thinking Matters
- Reduces the risk of building the wrong thing. Prototyping and testing expose weak assumptions while changes are still cheap.
- Improves user experience. Products shaped by real user research tend to be simpler and more intuitive across mobile, web, wearables and other devices.
- Handles ambiguity. Problems with many stakeholders, multiple systems, or unclear user needs (such as healthcare services) benefit from a process that learns quickly.
- Supports innovation. Teams that make continuous discovery a habit adapt faster to market change.
- Aligns teams. Shared research and a clear problem statement replace opinion-driven debate with evidence.
Core Principles of Design Thinking
The five stages describe what teams do. The principles describe how teams think while doing it.
- Human-centered focus. Every decision starts with real people’s needs, behaviors, and context.
- Empathy before solutions. Observe and listen before proposing anything.
- Collaboration and diverse perspectives. Designers, developers, business owners and users surface better ideas together.
- Embrace ambiguity. The problem is not fully defined at the start; clarity is an outcome of the process.
- Experiment and prototype. Make ideas tangible quickly so people can react to something real.
- Iterate. Treat each test result as input and loop back as often as needed.
- Bias toward action. Small, fast experiments beat long debates.
The Core Principles of Design Thinking Process
The five stages of the design thinking process are Empathize, Define, Ideate, Prototype, and Test. First, teams research user needs. Next, they define the problem, explore potential solutions, build prototypes, and test those prototypes with users. The process is iterative, meaning teams can return to earlier stages whenever new insights emerge.
| Stage | Goal | Typical output | Common methods |
|---|---|---|---|
| 1. Empathize | Understand users | Research insights | Interviews, observation, surveys, journey mapping |
| 2. Define | Frame the real problem | Problem statement | Personas, empathy maps, “How might we” questions |
| 3. Ideate | Generate solutions | Shortlist of ideas | Brainstorming, Crazy 8s, SCAMPER, dot voting |
| 4. Prototype | Make ideas tangible | Testable prototype | Sketches, wireframes, clickable Figma prototypes |
| 5. Test | Validate with users | Feedback and next steps | Usability tests, interviews, A/B tests |
| [INSERT ORIGINAL INFOGRAPHIC HERE] The Design Thinking Process: Empathize → Define → Ideate → Prototype → Test, with a return arrow labelled “Iterate and revisit earlier stages as needed.”Alt text: Design thinking process showing the five iterative stages: Empathize, Define, Ideate, Prototype and Test. File name suggestion: design-thinking-process-5-stages.webp |
Stage 1: Empathize
Goal: Understand the people you are designing for, including needs they cannot easily articulate.
- Conduct interviews with representative users, using open-ended questions such as “Tell me about the last time you…”
- Observe users in context instead of relying only on what they say.
- Review support tickets, app-store reviews and analytics for patterns.
- Document findings with empathy maps (what users say, think, do and feel) and journey maps.
Output: Evidence-based insights and user personas.
Pitfall: Interviewing only friendly users or asking leading questions.
Stage 2: Define
Goal: Turn research into a clear, specific problem statement.
- Cluster findings into themes using affinity mapping.
- Write a point-of-view statement: [User] needs [need] because [insight].
- Convert it into a “How might we…?” question that invites many solutions.
Example: Instead of “We need a better booking app,” define the problem as: “Busy parents need a quick way to reschedule appointments because phone calls during work hours are impractical. How might we make rescheduling effortless?”
Output: A problem statement the whole team agrees on.
Pitfall: Defining the problem as a solution (for example, “We need a chatbot”).
Stage 3: Ideate
Goal: Generate a wide range of ideas, then narrow to the most promising.
- Diverge first: set a timer and produce quantity without judging (Crazy 8s, brainwriting).
- Invite people beyond the design team; engineers and customer-support staff often add valuable insight.
- Converge second: use dot voting or an impact/effort matrix to select a small number of ideas.
- Check each idea against desirability, feasibility and viability.
Output: A shortlist of ideas ready to prototype.
Pitfall: Evaluating ideas too early.
Stage 4: Prototype
Goal: Build a quick, low-cost version of an idea so you can learn from real reactions.
- Match fidelity to the question: paper sketches for flow, clickable Figma prototypes for interaction.
- Prototype only the part you need to test, not the whole product.
- For software, a validated prototype can feed directly into MVP development.
Output: A testable prototype and a list of the assumptions it tests.
Pitfall: Over-polishing, which makes teams defensive about feedback.
Stage 5: Test
Goal: Learn what works, what does not, and what to change.
- Start with approximately five representative participants per usability-testing round to identify common issues. Increase the sample size when testing different user groups, complex workflows, or high-risk features. Five users is a useful starting heuristic, not a guarantee.
- Ask users to complete realistic tasks while thinking aloud, and avoid explaining or defending the design.
- Track task success, time on task and errors; supplement with A/B tests once the product is live.
- Decide whether to refine the prototype, return to ideation, or redefine the problem.
Output: Validated insights and prioritized changes.
Pitfall: Treating testing as final approval instead of a learning step.
Design Thinking Examples
Airbnb: learning from firsthand observation
In its early days, Airbnb’s founders reportedly visited hosts in person and noticed that listing photos were weak, then experimented with better photography. This is often cited as an example of learning from direct observation. It should not be read as photography alone explaining Airbnb’s growth.
Kaiser Permanente: redesigning nurse shift changes
Kaiser Permanente worked with nurses and design consultants to improve how shift handovers happen. The team studied real handovers and tested changes, focusing on the process rather than on new tools.
Google Design Sprint: a related structured approach
The design sprint, developed at Google Ventures, is a related method rather than a compressed version of the five Stanford stages. It is a five-day structured process covering problem framing, solution sketching, decision-making, prototyping, and testing with users.
Illustrative example: a food delivery app
Hypothetical scenario for explanation only. A team assumed users wanted more restaurant filters. Interviews suggested the deeper frustration was uncertainty about delivery time. The team tested a live order-tracking prototype to evaluate whether clearer delivery updates could reduce customer uncertainty. The insight came from empathy research, not from the original feature request.
Design Thinking vs Agile, Lean UX and the Double Diamond
| Framework | Focus | Best for | Relationship to design thinking |
|---|---|---|---|
| Design thinking | Finding the right problem and solution | Early-stage, ambiguous problems | The foundation |
| Double Diamond (UK Design Council) | Diverge and converge: Discover, Define, Develop, Deliver | Structuring end-to-end design projects | A related model built on the same diverge/converge logic |
| Lean UX | Rapid hypothesis testing | Fast-moving product teams | Applies similar principles in lean cycles |
| Agile | Delivering working software in sprints | Building and shipping | Overlaps in iteration; complementary rather than competing |
How they overlap: Both design thinking and Agile are iterative and value feedback. Design thinking concentrates on understanding the problem and validating solutions; Agile concentrates on delivering working software in increments. Many teams use design thinking to decide what to build, and Agile to build it efficiently, with research continuing between sprints.
Applying Design Thinking to Mobile App Development
Design thinking in UX design and software development follows the same five stages, applied to a product roadmap:
- Discovery. Interview target users and review competitors before writing requirements. Need inspiration? See our guide to mobile app ideas.
- Problem framing. Write a “How might we” statement tied to a measurable outcome, such as faster checkout.
- Ideation workshop. Bring product, design and engineering together to shortlist features.
- Clickable prototype. Build in Figma and test with representative users before development starts.
- MVP. Build what testing supports. See MVP development.
- Post-launch iteration. Use analytics and feedback as continuing “Test” input.
For budgeting context, read how much it costs to design a mobile app.
| Turn Your App Idea Into a User-Friendly Product: Validate your concept with expert UI/UX design, prototyping, and development support.Button: Discuss Your App Idea → https://www.icoderzsolutions.com/contact.php |
Design Thinking in Action: From App Idea to Validated Prototype
Chowman is a Chinese restaurant chain based in Kolkata, India, with 35+ outlets across five Indian cities. The brand needed a food ordering platform that could grow with its business. iCoderz delivered an end-to-end solution covering customer, restaurant and driver apps plus a central admin panel. The project shows how human-centered thinking works when a product serves several groups of users, not just the end customer. Read the full Chowman case study.
Project snapshot
| Client | Chowman, Chinese restaurant chain (Kolkata, India) |
| Starting point | In 2019 the client was already using an on-demand ordering solution with a POS system, but was not satisfied with it |
| What was built | Customer app, restaurant app, delivery driver app and a master admin panel |
| Services supported | Home delivery, takeaway, restaurant table reservation, online payments, call-centre ordering and QR-code contactless menus |
| Technology (per the case study) | Laravel, Node.js and Vue.js for the web backend and frontend; native iOS (Objective-C) and Android (Java) apps |
| Scale (as reported in the case study) | 35+ outlets across five cities, around 150K customers, 8K monthly sign-ups and 250+ delivery fleet members |
Seen through a design thinking lens
The table below maps the documented project work to the five stages. It is an interpretation: the case study describes stakeholder discovery, design and testing, but not formal user interviews.
| Stage | What the project team did | Result or decision |
| Empathize | The technical head listened to the client’s problems, and the team ran a two-week brainstorm to finalize scope. Challenges observed included an outdated platform (Core PHP, HTML, MySQL), careful handling of festival discounts, and the need for third-party integrations. On the business side, about 30% of the customer base did not have a smartphone or did not want to order online. The client also wanted orders from every channel, insight into customer preferences, and a safe way to keep serving customers during COVID-19. | A clear picture of both technical and business pain points, and of four user groups: customers, restaurant staff, drivers and administrators |
| Define | The challenges were grouped into technical (platform upgrade, finance handling, integrations, total cost of ownership) and business (reach non-smartphone customers, omni-channel ordering, customer data, COVID-19 safety). One way to frame the core problem: How might we let Chowman take orders from every customer, on every channel, from one connected platform? (Framing written for this article.) | Scope split into smaller, documented milestones before development began |
| Ideate | The team chose a connected ecosystem instead of only a customer app. It added a call-centre module that sends an SMS payment link, QR-code contactless ordering with a customer feedback system, third-party POS for menu management, analytics integrations, and delivery-service integrations with Dunzo and Borzo. | The call-centre module is reported to have helped retain the 30% of customers who prefer not to order through an app |
| Prototype | The team sketched the mobile app flow for prototyping during the wireframe and design step. Development then proceeded module by module, with integrations added last. | A defined architecture, technology stack and module plan before build |
| Test | Alpha testing combined automation tools and manual testing. Beta testing involved 20 customers, the core development team and Chowman team members. | Issues surfaced before launch, and the product moved into ongoing support and feature updates |
Lessons for your own project
- Design for every stakeholder. A smooth customer experience depends on restaurant staff managing incoming orders and drivers completing deliveries. Empathy has to cover all of them, not only the paying customer.
- Do not design only for the “default” user. About 30% of Chowman’s customers did not order through a smartphone app. A call-centre channel with an SMS payment link served them.
- Respond to context. The COVID-19 period led directly to QR-code contactless menus, which is an example of the iterate-as-you-learn principle.
- Prototype and test before you scale. A documented wireframe step and a beta test with real customers reduce launch risk.
Design Thinking Process Checklist for Product Teams
Research preparation
- ☐ Defined who the target users are and who is out of scope
- ☐ Prepared open-ended interview questions
- ☐ Reviewed existing data (analytics, support tickets, reviews)
Problem definition
- ☐ Clustered findings into themes
- ☐ Written a point-of-view statement
- ☐ Agreed on a “How might we” question with stakeholders
Idea selection
- ☐ Generated ideas without early judgment
- ☐ Included people from different roles
- ☐ Checked shortlisted ideas for desirability, feasibility and viability
Prototype validation
- ☐ Chosen a fidelity level that matches the question
- ☐ Written down the assumptions being tested
- ☐ Recruited representative participants and prepared realistic tasks
Post-test decisions
- ☐ Documented what worked and what failed
- ☐ Prioritized changes
- ☐ Decided: refine, return to ideation, or redefine the problem
Common Design Thinking Mistakes
- Skipping empathy and relying on internal assumptions
- Treating it as a one-time workshop instead of an ongoing practice
- Jumping to solutions before the problem is defined
- Involving participants who are too few or too similar
- Over-investing in prototypes and becoming defensive about them
- Ignoring feasibility and viability
- Leaving research findings unused in a slide deck
Design Thinking Tools
| Purpose | Example tools |
|---|---|
| Collaboration and workshops | Miro, FigJam, Mural |
| Prototyping | Figma, Framer |
| User research and testing | Maze, UserTesting, Dovetail, Lookback |
| Analytics and behavior | Amplitude, Hotjar, Google Analytics |
Optional: add downloadable templates (empathy map, “How might we” worksheet, test plan) as a lead magnet.
How AI Is Changing the Design Thinking Process
AI does not replace empathy, but it can speed up parts of the process:
- Empathize: Summarizing interview transcripts and surfacing themes from large volumes of reviews and tickets.
- Ideate: Producing starting points and unusual angles for brainstorming.
- Prototype: Generating layout and interface variations quickly.
- Test: Helping analyze session recordings and usability data.
Caution: AI-generated personas or “synthetic users” cannot replace conversations with real people. Use AI to accelerate analysis, not to skip research.
Conclusion
The design thinking process helps teams avoid one of the costliest mistakes in product development: building something nobody needs. By staying close to users, framing the right problem, and testing ideas cheaply, you improve the odds that what you launch succeeds.
Start small. Pick one problem, talk to a handful of users, and prototype one idea this week.
Frequently Asked Questions
What is design thinking in simple words?
Design thinking is a way of solving problems by starting with the people affected, testing ideas quickly with simple prototypes, and improving them based on feedback.
What are the 5 stages of design thinking?
Empathize, Define, Ideate, Prototype, and Test. The stages are not strictly sequential; teams often loop back as they learn.
What are the principles of design thinking?
Core principles include a human-centered focus, empathy, collaboration across diverse perspectives, embracing ambiguity, experimentation through prototyping, iteration, and a bias toward action.
What is the difference between design thinking and UX design?
UX design focuses on the experience of a specific product. Design thinking is a broader problem-solving approach that UX designers and other teams use to decide what to build and why.
Is design thinking only for designers?
No. Product managers, engineers, marketers, educators, healthcare teams and public-sector organizations also use it. Its value comes from cross-functional collaboration.
How long does the design thinking process take?
It varies from a few days for a focused sprint to several months for complex programs. Scope the process to the risk of the decision being made.
Is design thinking the same as Agile?
No. Design thinking focuses on understanding the problem and validating solutions, while Agile focuses on delivering working software iteratively. They overlap in iteration and complement each other.
When should you not use design thinking?
When the problem is already well defined and the solution is known, such as a routine bug fix, a lighter process is usually enough.