Chapter 2: The Design Thinking Process

Chapter 2 — The Design Thinking Process | UI/UX Design Made Simple
📘 Part 1 — Foundations

The Design Thinking
Process

Every great product — from Google Maps to Zomato — was built using a structured problem-solving process called Design Thinking. In this chapter, you'll learn the 5-stage framework that professional designers use every single day, why it works, and how to apply it yourself.

What is Design Thinking? 5 Stages Double Diamond Agile vs Waterfall 🇮🇳 & 🌐 Examples Activity Quiz Case Studies
Section 2.1
What is Design Thinking?

Most people assume that design starts with making things look pretty. But professional designers know a secret: design starts with deeply understanding people.

Design Thinking is a human-centered, problem-solving framework that helps designers (and teams) build products that people actually want to use. Instead of jumping straight to solutions, Design Thinking forces you to first understand the problem from the user's perspective.

It was popularized by Stanford's d.school and the global design firm IDEO, but today it's used by companies like Google, Infosys, Tata, and every serious design team worldwide.

🇮🇳
Why it matters for Indian designers: India's users are incredibly diverse — different languages, literacy levels, internet speeds, and cultural contexts. A designer in Mumbai can't assume their own experience represents a user in rural Bihar. Design Thinking's emphasis on empathy and research is especially critical when designing for India's 900M+ internet users.
💡
Key Insight: Design Thinking is not just for designers. Product managers, developers, marketers, and even founders use it. If you understand this process, you'll speak the same language as every team you'll ever work with.
Section 2.2
The 5 Stages of Design Thinking

Design Thinking has 5 stages. They're often shown as a linear process, but in reality designers loop back and forth between them constantly. Think of it as a cycle, not a straight line.

1
Empathize
Understand your user deeply
This is the most important stage — and the most skipped. Empathizing means stepping out of your own assumptions and truly understanding who your user is, what they need, and what frustrates them. You do this through user interviews, observation, and surveys.
🇮🇳 India Example
When building Meesho's reseller feature, designers spent weeks with homemakers in Tier 2 cities to understand how they use WhatsApp for business — before designing a single screen.
🌐 Global Example
IDEO redesigned the hospital patient experience by having designers pretend to be patients — lying in hospital beds for hours to feel what patients actually experience.
2
Define
Frame the right problem
After research, you synthesize everything you've learned into a clear problem statement. A good problem statement is human-centered, not solution-focused. The classic format is: "[User] needs a way to [goal] because [insight]." Getting this right is critical — solving the wrong problem beautifully is still failure.
🇮🇳 India Example
❌ Bad: "We need to build a UPI payment feature."
✅ Good: "First-time smartphone users in small towns need a way to pay digitally without fearing mistakes because they've heard stories of sending money to wrong numbers."
🌐 Global Example
Airbnb's problem statement wasn't "build better search" — it was "travelers need a way to find stays that match their desired feeling, not just their destination."
3
Ideate
Generate as many ideas as possible
Now you generate solutions — lots of them. The goal of ideation is quantity over quality first. Wild, impractical ideas are welcome because they often spark the truly innovative ones. Common ideation techniques include Brainstorming, Crazy 8s (sketching 8 ideas in 8 minutes), How Might We questions, and Mind Mapping.
🇮🇳 India Example
PhonePe's team ideated over 30 concepts for their home screen before landing on the icon-grid layout. Early ideas included voice-first UI and WhatsApp-like chat for payments.
🌐 Global Example
Google's "Crazy 8s" technique is used in Google Design Sprints — designers sketch 8 different solutions in 8 minutes to force creative thinking beyond the obvious.
4
Prototype
Build quick, cheap versions to test
A prototype is a simple, low-cost version of your solution built for testing — not shipping. It can be paper sketches, clickable Figma wireframes, or even a cardboard mock-up. The rule is: build just enough to learn. Don't waste weeks perfecting something before you know if it works.
🇮🇳 India Example
Nykaa's team paper-prototyped their "beauty routine tracker" feature by printing screens on paper and having users tap through them with their finger — before writing a single line of code.
🌐 Global Example
Dropbox's original "prototype" was just a 3-minute explainer video. It got 75,000 signups overnight — proving demand before the product even existed.
5
Test
Learn from real users, then iterate
Testing means putting your prototype in front of real users and watching what they do — not what they say they'll do. Users often say "I love it!" while completely failing to complete a basic task. Testing reveals the gap between intention and reality, and sends you back to Empathize or Ideate with better information.
🇮🇳 India Example
Swiggy tested their new checkout redesign with 200 users in Bengaluru before rolling it out nationally — discovering that the "Add tip" button was causing confusion and abandonment.
🌐 Global Example
Spotify found through testing that users ignored their "Daily Mix" feature because the thumbnail images were too similar. One icon change increased plays by 19%.
⚠️
Common Mistake: Many beginners treat the 5 stages as a strict one-way flow. In real projects, you'll loop back constantly. Testing might send you back to Empathize. Prototyping might spark new Define ideas. Design Thinking is iterative, not linear.
Section 2.3
The Double Diamond Framework

The Double Diamond is a visual model from the UK Design Council that shows how design thinking works in practice. It's made of two diamonds — each one representing a phase of divergent thinking (exploring widely) followed by convergent thinking (narrowing down).

The first diamond is about finding the right problem. The second diamond is about finding the right solution. Many failed products got the second diamond right but skipped the first one entirely.

◇◇ The Double Diamond
🔍
Discover
Research widely. Talk to users. Gather all possible insights.
Diverge
🎯
Define
Synthesize research. Write a clear problem statement.
Converge
💡
Develop
Ideate, prototype, and explore many possible solutions.
Diverge
🚀
Deliver
Test, refine, and ship the best solution.
Converge
✅
Double Diamond vs. 5 Stages: Think of the Double Diamond as the macro view (the overall shape of your project) and the 5 Stages as the micro tools (what you actually do at each phase). Both frameworks work together — you'll use them hand-in-hand throughout your career.
Section 2.4
Design in Agile vs Waterfall Teams

As a UI/UX designer, you'll work inside a development team. Understanding how your team works will help you know when to design, when to test, and how to collaborate with developers and product managers.

There are two main ways software teams work — Waterfall and Agile. Most modern Indian startups and global tech companies use Agile.

Aspect
🌊 Waterfall
⚡ Agile
Approach
Linear, phase by phase
Iterative, sprint-based
Design happens
All upfront before build
Continuously each sprint
Feedback
At end of project
After every sprint (2 weeks)
Risk
High — changes are costly
Low — adapt quickly
Used by
Government, banking, legacy IT
Startups, product teams, FAANG
Indian eg.
IRCTC (older builds)
Swiggy, Razorpay, Zomato
Global eg.
Traditional banking software
Google, Spotify, Airbnb
💼
Interview Tip: Interviewers at startups and product companies will ask "Have you worked in Agile?" Know the answer. Even if you haven't professionally, you can say: "I follow an iterative design process — research, design, test, refine — which mirrors Agile's sprint structure."
Hands-On Activity
Activity 2 — Apply Design Thinking

You're going to apply all 5 stages of Design Thinking to a real mini-problem. Read the scenario below and fill in each stage. There are no wrong answers — the goal is to practise thinking like a designer.

☕
The Chai Stall App Challenge
Estimated time: 15–20 minutes
📋 Your Scenario
A popular local chai stall owner in Pune wants to launch a simple mobile app to take pre-orders from office workers nearby. Currently, customers call him on his mobile, he forgets orders, and often runs out of specific items. Apply the 5 stages of Design Thinking to this problem.
1
Empathize
What would you ask the chai stall users?
2
Define
Write a problem statement (use the format: [User] needs a way to...)
3
Ideate
List 3 different app concepts (think wild!)
4
Prototype
Describe your simplest possible prototype
5
Test
How would you test it? What would you look for?
Dual Case Studies
Design Thinking in Action

Let's see how Design Thinking was applied in two real companies — one Indian, one global — and the results it produced.

🌐 Global Case Study
IDEO Redesigns the Shopping Cart
IDEO · ABC Nightline Challenge · USA · 1999 — Still Taught in Design Schools Today
🔍 Empathize — Watching Real Shoppers
IDEO was given 5 days to redesign the supermarket shopping cart. Instead of jumping to sketches, the team went to supermarkets and observed shoppers. Key insight: parents were terrified of children standing in carts and falling. Many shoppers used multiple small baskets instead of the big cart. The cart was designed for stores to fill with products, not for humans pushing them.
🎯 Define — The Real Problem
The real problem wasn't "make the cart look better." It was: "Shoppers need a cart that feels safe for families, easy to navigate in crowded aisles, and adaptable to how people actually shop — not how stores want them to shop."
💡 Ideate + Prototype + Test
The team held wild brainstorming sessions, generating dozens of concepts. They built multiple rough prototypes in hours using pipe, wire, and plastic. They tested these with real shoppers in store aisles, watched what worked, scrapped what didn't, and iterated rapidly over 5 days.
📊 The Result
5
Days to full redesign
30+
Prototypes built & tested
0
Falls from redesigned cart
🏆
Taught in 1,000+ design schools
🎓 Key Lessons
→Observation beats assumptions every time — IDEO's biggest insights came from watching, not asking.
→Rapid, rough prototypes beat slow, perfect ones. 30 prototypes in 5 days is faster than 1 prototype in 5 weeks.
→The real problem is rarely the surface problem. "Make the cart better" was actually "make shopping human-centered."
→Diverse teams (engineers, psychologists, linguists) produce better ideas than homogeneous ones.
Chapter Quiz
Test Your Understanding

6 questions · Scenario-based & multiple choice · India 🇮🇳 & Global 🌐 — no time limit!

📝
Chapter 2 Quiz
The Design Thinking Process
Question 1 of 6
🎉

Chapter 2 Complete!

You now understand the Design Thinking process — the same framework used by Google, IDEO, Meesho, and every top design team in the world. This is your foundation for everything that comes next.

📌 Chapter Summary
✓Design Thinking is a 5-stage framework: Empathize → Define → Ideate → Prototype → Test.
✓It's iterative, not linear — you loop back and forward between stages constantly.
✓The Double Diamond shows the macro shape: find the right problem, then find the right solution.
✓Most modern design teams (Swiggy, Google, Airbnb) work in Agile sprints — learn the language.
✓Meesho's success shows: real field research in India beats assumptions made in air-conditioned offices.
✓Empathy is not a soft skill — it's the most powerful design tool you have.
Location: India

Comments

Post a Comment

Popular Posts