Design thinking is not just a process — it is a mindset to deeply understand users and create solutions that truly matter.
Design thinking is the core approach that separates product managers who build user-centered innovations from those who ship features nobody wants. It is a structured way to understand your customer’s world, define the right problem, and co-create solutions through rapid iteration.
The trap most PMs fall into is skipping straight to solution mode — brainstorming features, writing specs, and pushing for delivery — without fully grasping the user’s experience or the problem’s root cause. That leads to wasted effort, missed opportunities, and products that don’t stick.
This lesson walks you through the five phases of design thinking — empathize, define, ideate, prototype, and test — with practical guidance on how to apply each in Indian product contexts. You will learn to frame problems from the user’s perspective, generate creative solutions, and validate them early and often.
The design thinking mindset is about people first
Before we dive into the phases, understand this: design thinking is not a checklist. It is a mindset of curiosity, empathy, and experimentation.
You start by immersing yourself in the user’s world. You seek to understand not just what they say, but what they do, feel, and struggle with. You suspend judgment and assumptions. You look for surprises and contradictions.
Then you define the problem in a way that captures the user’s true needs — not just the symptoms or what stakeholders say. This problem frame guides ideation and solution exploration.
You generate many ideas without fear of being wrong. You build quick, low-fidelity prototypes to make abstract ideas tangible. And you test with real users to learn fast and iterate.
This iterative, human-centered approach reduces risk and increases the chance of product-market fit.
The five phases of design thinking
Design thinking breaks down into five phases. These are not strictly linear — you will often cycle back and forth between them as you learn.
| Phase | What it means | Indian product example |
|---|---|---|
| Empathize | Understand users deeply through observation & interviews | Studying kirana store owners’ ordering pain points |
| Define | Synthesize insights to frame the core problem | "How might we reduce stockouts for small retailers?" |
| Ideate | Generate diverse ideas without constraints | Brainstorming app features, SMS alerts, credit lines |
| Prototype | Build quick, rough versions of solutions | Paper mockups of order screens or voice bots |
| Test | Validate assumptions with users, gather feedback | Field testing prototypes with shopkeepers |
1. Empathize: get out of the building and listen
The first phase is about gaining empathy for your users. You want to see the world through their eyes.
This means:
- Conducting qualitative research — interviews, shadowing, contextual inquiry.
- Observing user behavior in real contexts — not just surveys or online data.
- Looking for explicit needs (what users say) and implicit needs (unspoken behaviors or frustrations).
- Being humble. Assume you don’t know the problem yet.
Example: Meesho’s product team spent months visiting tier-2 and tier-3 resellers, watching how they searched for products and negotiated prices. They noticed many users struggled to type English queries, leading to a vernacular-first search experience.
2. Define: synthesize to frame the right problem
After gathering raw data, the next phase is to process and synthesize your findings to create a clear problem statement.
This involves:
- Identifying patterns, pain points, and surprising insights.
- Distinguishing symptoms from root causes.
- Crafting a user-centered problem statement — often framed as a "How might we" question.
- Prioritizing which problem to solve based on impact and feasibility.
Example: Instead of defining the problem as "Build an inventory app," Meesho’s team framed it as "How might we help kirana store owners avoid stockouts without adding complexity?"
This reframing focuses efforts on the user’s real pain and guides ideation toward practical solutions.
Choose a product or service you use regularly — a local grocery store, a ride-hailing app, or a payment service. Write down:
- What are the explicit problems the user mentions?
- What are the implicit or unspoken struggles you observe?
- Based on these, formulate a “How might we” problem statement that captures the core need.
3. Ideate: generate ideas without judgment
The ideation phase is about exploring diverse solutions.
Key points:
- Encourage wild, creative ideas.
- Defer judgment to keep the flow of ideas.
- Use brainstorming, mind mapping, or other creativity techniques.
- Include cross-functional teams to get varied perspectives.
Example: Swiggy’s team brainstorming ways to improve last-mile delivery included ideas from better route optimization algorithms to crowdsourced delivery and even partnering with local auto-rickshaw drivers.
This phase is about quantity and diversity of ideas, not immediate feasibility.
Swiggy product brainstorming session
You (PM): “Let’s list all the ways we can reduce delivery time — no idea is too wild.”
Priya (Design): “What if we allow customers to track delivery agents live on map?”
Karthik (Engineering): “We could optimize routes using real-time traffic data.”
Neha (Operations): “Can we tap into local auto-rickshaw drivers for flexible delivery?”
You: “Great ideas. Let’s cluster and prioritize them after.”
Balancing creative freedom with business constraints
4. Prototype: build to think and learn fast
Prototyping is about making your ideas tangible and testable quickly.
Guidelines:
- Build low-fidelity prototypes first — paper sketches, wireframes, clickable mockups.
- Focus on key interactions or value propositions.
- Use prototypes to communicate ideas and gather early feedback.
- Avoid spending excessive time polishing at this stage.
Example: Razorpay’s early checkout flow prototypes were simple wireframes tested with merchants to validate if the payment process was intuitive before investing in development.
Pick one idea from your ideation list. Sketch a simple prototype on paper or use a tool like Figma to create a low-fidelity mockup. Focus on:
- The core user interaction.
- How it solves the defined problem.
- What you want to learn from testing this prototype.
5. Test: validate assumptions and iterate
Testing is critical to avoid building the wrong thing at scale.
You should:
- Test prototypes with real users early and often.
- Observe how users interact and listen to their feedback.
- Identify what works, what confuses, and what frustrates.
- Iterate rapidly based on learnings.
Example: Flipkart’s team tested their mobile app checkout prototypes with users in tier-2 cities to identify friction points caused by slow networks or unfamiliar UI patterns.
Why design thinking matters in Indian product contexts
India’s diversity — linguistic, cultural, economic — means user needs can vary widely even within a single city. Design thinking helps you:
- Capture nuanced user behaviors beyond surveys or analytics.
- Identify hidden pain points that only emerge through observation.
- Avoid building one-size-fits-all solutions that fail across segments.
- Innovate with frugal, context-aware prototypes that suit local constraints.
For example, Meesho’s vernacular search and Flipkart’s regional language interfaces emerged from deep empathy and iterative prototyping with Indian users.
Common pitfalls and how to avoid them
- Skipping empathy: Jumping to solutions without user understanding leads to irrelevant features.
- Defining the wrong problem: Solving symptoms or stakeholder requests instead of user pain.
- Fear of failure: Avoiding prototyping or testing due to perfectionism delays learning.
- Ignoring feedback: Treating user feedback as optional rather than essential.
Let me be direct about this: if you cannot answer “Who is the user?” and “What is their core problem?” with evidence, you are not ready to build.
Test yourself: The vending machine redesign challenge
You are the PM for a new vending machine product to be launched in Mumbai train stations. Initial sales are low. You have access to a small team and two weeks to improve the product-market fit.
The call: What is your first step in applying design thinking to improve the vending machine?
Your reasoning:
You are the PM for a new vending machine product to be launched in Mumbai train stations. Initial sales are low. You have access to a small team and two weeks to improve the product-market fit.
Your task: What is your first step in applying design thinking to improve the vending machine?
your reasoning:
From the field: Design thinking in Indian startups
Field Exercise: Apply design thinking to a real product
Choose a product you use daily (Google Pay, Swiggy, Ola, or a local service). Go through these steps:
- Empathize: Interview or observe one user. What are their pain points? What frustrates them?
- Define: Write a “How might we” problem statement based on your empathy work.
- Ideate: Brainstorm 5 possible solutions without filtering.
- Prototype: Sketch or describe a simple prototype of one solution.
- Test: Share your prototype with the user and note their reactions.
Reflect on what you learned and how it changes your understanding of the product.
Where to go next
- Build your user research skills: User Research Methods
- Learn to translate insights into requirements: Discovery and Requirements Definition
- Master prototyping and experimentation: Rapid Prototyping and Testing
- Develop product vision grounded in user needs: Product Vision and Strategy
PL alumni now work at Flipkart, Razorpay, Swiggy, PhonePe, Amazon, Microsoft, and 30+ other companies.