📘 Week 1 – Introduction to Design Thinking

1.1 What is Design Thinking?

 Definition (general):
Design Thinking is a human-centered, iterative approach to problem
solving that combines empathy, creativity, and rationality to meet
user needs and create innovative solutions.

 Definition (as per course):

A systematic method of solving problems by starting and ending
with humans. It involves observing, interviewing, or experiencing a
situation to understand people’s needs, and then improving the
situation by solving problems for them.

 Core Idea:
Traditional problem solving often begins with a solution (e.g., “let’s
build an app”) → but design thinking starts with the human (“what
problem does the person actually face?”).

1.2 Why Do We Need Design Thinking?

 Problems today are often wicked problems (complex, ambiguous,

involving multiple stakeholders).

 Example:

o Improving urban transportation is not just about building more

roads — it requires understanding commuters, policies,
environment, costs, accessibility.

 Linear, engineering-style methods fail because they assume the

problem is well defined.

 Design Thinking helps to:

o Reframe vague/ambiguous challenges into solvable ones.

o Keep focus on user needs instead of jumping to technology.

o Create solutions that are not only technically feasible, but also
desirable and viable.

1.3 Principles of Design Thinking

 1. Human-Centered – Always focus on people’s needs, behaviors,
and emotions.

2. Empathy – Step into the shoes of the user; understand their

perspective.

3. Collaboration – Diverse teams create better ideas.

4. Iteration – Solutions are tested, refined, re-tested.

5. Experimentation – Try things quickly with prototypes.

6. Fail Early, Fail Cheap – Mistakes are valuable if they come early in
the process.

1.4 Process Overview

This course uses a 4-phase model:

1. Empathize – Understand user experience (observe, map journey,

identify needs).

2. Analyze – Make sense of data; identify root causes; frame

opportunities.

3. Solve (Ideate) – Generate multiple possible solutions.

4. Make & Test (Prototype) – Build quick models, test with users,
refine.

👉 Note: Some models (like Stanford [Link]) use 5 phases (Empathize →

Define → Ideate → Prototype → Test). This course compresses “Define” into
Analyze and “Prototype/Test” into one step.

1.5 Design Thinking vs Traditional Problem Solving

Aspect Traditional Design Thinking

Approach Linear Iterative

Technology / business
Focus Human needs
goals

Problem already
Start Point Problem often redefined
defined

Empathy, ideation,
Tools Data analysis, logic
prototyping
Aspect Traditional Design Thinking

Risk Embrace small failures to

Avoid risk
Handling learn

Innovative, user-desirable
Outcome Functional solutions
solutions

1.6 History & Origins

 1960s–70s: Herbert Simon’s book “The Sciences of the Artificial”

introduced design as a way of thinking.

 1980s–90s: Stanford’s [Link] (David Kelley, IDEO founders)

popularized the term “Design Thinking.”

 2009: Tim Brown’s book Change by Design brought Design Thinking

into mainstream business.

 Today: Used by companies like Apple, Google, IBM, Infosys, TCS,

and NGOs for social innovation.

1.7 Why “Design” in Design Thinking?

 “Design” here does not mean only graphic or industrial design.

 It means designing solutions: shaping processes, systems,

products, and services in ways that meet user needs.

 Examples:

o Service Design (banking apps, hospital services).

o Experience Design (theme parks, shopping malls).

o Product Design (mobile phones, wearables).

1.8 Mindsets Required

 Beginner’s Mind: Drop assumptions, ask fresh questions.

 Optimism: Believe that solutions exist.

 Bias to Action: Don’t just discuss — build and test.

 Learning from Failure: Every failed prototype is useful feedback.

  Integrative Thinking: Combine analysis (logic) with creativity
(intuition).

1.9 Case Study Examples

1. Airbnb (early days)

o Problem: Low booking rates despite many listings.

o Empathy: Found that photos uploaded by hosts were poor.

o Solution: Founders personally took high-quality photos of

apartments.

o Result: Bookings shot up → company scaled globally.

2. GE Healthcare (MRI machine for children)

o Problem: Kids were scared of MRI machines, often had to be

sedated.

o Empathy: Designer Doug Dietz interviewed children, parents.

o Solution: Redesigned machine as a “pirate adventure” with

colorful decals and stories.

o Result: Children saw MRI as a game, sedation dropped

drastically.

1.10 Applications of Design Thinking

 Business / Startups – identifying customer pain points.

 Healthcare – improving patient experiences.

 Education – designing engaging learning methods.

 Government & Policy – citizen-centered services.

 Technology – apps, interfaces, devices.

1.11 Learning Outcomes of Week 1

By end of Week 1, you should:

 Define Design Thinking clearly.

 Explain why human-centered design matters.

  Compare Design Thinking with traditional methods.

 Recall the phases (Empathize, Analyze, Solve, Prototype/Test).

 Understand basic principles: empathy, iteration, prototyping,

collaboration.

1.12 Key Explanations (Integrated Exam-Style Content)

 Define Design Thinking. How does it differ from traditional

engineering design?
→ Design Thinking is a human-centered, iterative approach
that focuses on solving real user problems by empathizing,
reframing, ideating, prototyping, and testing. Unlike
traditional engineering design, which assumes problems are
well defined and solutions are judged by technical
feasibility, design thinking redefines problems, embraces
ambiguity, and seeks innovative solutions that are feasible,
viable, and desirable.

 Explain the principles of Design Thinking with examples.

→ Principles include empathy (e.g., Airbnb photos),
collaboration (cross-functional teams at IDEO), iteration
(multiple rounds of prototyping), and “fail early, fail cheap”
(GE MRI redesign was tested cheaply with stickers before
reengineering machines). These principles ensure solutions
stay people-centered.

 Why is empathy important in Design Thinking?

→ Empathy reveals latent needs—things users may not
express directly. For instance, children never said “make
MRI fun,” but empathy uncovered their fear. Without
empathy, solutions risk being technically sound but
irrelevant to users.

 Describe the phases of the Design Thinking process used in

this course.
→ The course model: Empathize → Analyze → Solve →
Prototype/Test. Each step builds on the other: empathize
with users, analyze data to reframe problems, generate
possible solutions, and test prototypes with users to refine.

 Explain “Fail early, fail cheap.” Why is it encouraged?

→ Early-stage prototypes (paper sketches, mockups) cost
little but reveal flaws quickly. Learning through early
 failures prevents expensive mistakes later. It shifts failure
from being negative to being a source of valuable feedback.

📘 Week 2 – Empathize Phase

2.1 Introduction to Empathy in Design Thinking

 Empathy is the ability to understand and share the feelings,

thoughts, and needs of others.

 In design thinking, empathy means going beyond what people say

to uncover what they feel, think, and struggle with.

 Why it matters:

o Users often don’t know how to articulate their problems.

o Observing and engaging with them uncovers hidden pain

points.

o It ensures we design for real human needs, not just

assumptions.

👉 Example:
When IDEO designed shopping carts, they didn’t just ask people what they
wanted; they watched people shop. They discovered parents worried
about kids’ safety and theft of small items. These insights led to design
improvements.

2.2 Role of Empathy in Design Thinking

  Foundation of human-centered design: Without empathy,
solutions risk being irrelevant.

 Helps identify latent needs (unspoken, unconscious needs).

 Builds trust with users, making them open up.

 Guides reframing: Often the problem we start with is not the real
problem.

Illustration:

 A company may define the problem as “low sales of washing

machines.”

 After empathizing with rural customers, they may find the real issue
is lack of running water or electricity → leading to frugal, innovative
solutions like semi-automatic or hand-cranked machines.

2.3 Methods for Empathizing

Empathy is gathered through qualitative research methods. Main

approaches:

2.3.1 Observation (Shadowing)

 Watch users in their natural environment.

 Focus on behavior, not just words.

 Note down surprises, workarounds, frustrations.

 Tools: Field notes, photos, video recordings.

👉 Example: Observing how nurses prepare patients revealed extra “hidden

work” like calming anxious families.

2.3.2 Interviews

 Conduct one-on-one conversations with users.

 Ask open-ended questions (“Tell me about the last time you…”)

instead of yes/no questions.

 Goal: Dig into stories, emotions, and motivations.

👉 Example: When designing a travel app, instead of asking “Do you like
using apps?” ask “Tell me about your last trip planning experience.”
2.3.3 Immersion (Experience as User)

 Designers place themselves in the user’s situation.

 Helps feel the pain firsthand.

👉 Example: A hospital redesign team spent a night as patients to

understand discomfort in waiting rooms, food delivery, and noise.

2.3.4 Empathy Mapping

A visual tool with 4 quadrants:

1. Says – What the user says (“I hate waiting in line”).

2. Thinks – Thoughts not spoken (“Maybe I should switch to another

service”).

3. Does – Actions taken (scrolling phone while waiting).

4. Feels – Emotions (frustration, boredom).

Benefit: Helps capture both explicit and hidden aspects of user

experience.

2.3.5 Personas

 A persona is a fictional character representing a group of users.

 Built from research data (age, goals, frustrations, behaviors).

 Used to keep the team focused on real users, not stereotypes.

👉 Example Persona:
Name: Anita, 28, working professional.
Goal: Wants quick, healthy meals after work.
Pain Point: No time to cook, online food apps are costly.
Implication: Opportunity to design affordable meal kits.
2.3.6 Customer Journey Mapping

 Plot the user’s step-by-step journey through an experience.

 Identify touchpoints where they feel positive, negative, or neutral.

 Useful for service design (banks, airports, hospitals).

👉 Example: Mapping a hospital patient journey from admission → waiting

→ diagnosis → discharge reveals pain points like long wait times.

2.4 Tools and Frameworks in Empathy Phase

 5 Whys Technique: Keep asking “Why?” until the root cause is

uncovered.

 Contextual Inquiry: Observe + interview at the same time.

 AEIOU Framework: Record observations under Activities,

Environments, Interactions, Objects, Users.

 Extreme Users: Studying people at the extremes (e.g., tech

experts vs. complete beginners) to reveal new insights.

2.5 Case Studies in Empathy

1. Designing for Illiterate Farmers

o Problem: Government wanted to distribute info about crop

prices.

o Empathy: Farmers couldn’t read SMS alerts.

o Solution: Voice-based services (IVR in local languages).

2. Uber Pooling in India

o Empathy research revealed users worried about safety and

time delays.
 o Result: Features like real-time ride tracking, emergency SOS,
upfront ride sharing time.

2.6 Outcomes of Empathize Phase

By the end of this phase, teams should have:

 A deep understanding of user needs (both spoken and

unspoken).

 Personas representing target users.

 Empathy maps capturing feelings, thoughts, and behaviors.

 Journey maps showing pain points.

 A research repository of quotes, photos, and observations.

2.7 Learning Outcomes of Week 2

You should be able to:

 Define empathy in design thinking.

 Explain why empathy is essential.

 List and describe key methods (observation, interviews, immersion).

 Use tools like empathy maps, personas, and journey maps.

 Relate empathy findings to problem definition.

2.8 Integrated Explanations (Exam-Oriented Content)

 Why is empathy important in design thinking?

→ Because it prevents designing irrelevant solutions. It reveals
unspoken needs and ensures products are desirable. Without
empathy, design becomes technology-driven instead of human-
centered.
  What methods are used in the empathize phase?
→ Observation, interviews, immersion, empathy maps, personas,
journey mapping. Each uncovers different aspects of user
experience.

 How do empathy maps and personas help?

→ Empathy maps structure raw observations (say, think, do, feel).
Personas create a relatable profile, helping teams remember they
are designing for real people, not abstract markets.

 Example of empathy-driven innovation?

→ GE Healthcare’s child-friendly MRI redesign: empathy uncovered
fear in kids → solution turned MRI into a game → increased patient
cooperation and reduced sedation.

📘 Week 3 – Analyze Phase

3.1 Introduction

 After empathy work, we now have lots of raw data: interviews,

observations, quotes, photos, emotions, pain points.

 The Analyze phase helps convert this chaos into clarity by:

1. Synthesizing findings.

2. Identifying patterns and themes.

3. Framing a clear, actionable problem statement.

 This step is often called “Define” in the Stanford model.

👉 Without analysis, teams risk solving the wrong problem.

3.2 Why Analyze?

  Empathy gives rich data, but raw insights can be overwhelming.

 Analysis helps:

o Spot real user needs behind symptoms.

o Avoid problem jumping (immediately offering solutions

without understanding the root).

o Align team understanding.

o Reframe broad, vague challenges into focused opportunities.

Example:

 Symptom: “Students score low in exams.”

 Root need: They want interactive learning tools and

personalized feedback, not just more lectures.

3.3 Key Activities in Analyze Phase

3.3.1 Data Synthesis & Affinity Mapping

 Write down all observations/quotes on sticky notes.

 Cluster similar insights together (e.g., “waiting too long,” “boring,”

“uncertain”).

 Themes emerge → used to define needs.

👉 Example: Bank customers mention “long queues,” “confusing forms,”

“slow counters.” → Theme = time inefficiency.

3.3.2 5 Whys Technique

 Keep asking “Why?” until you find the root cause.

 Prevents stopping at superficial problems.

👉 Example:

 Kids skip school → Why? Long distance.

 Why distance is an issue? No transport.

  Why no transport? School bus not provided.

 Root cause → Lack of infrastructure, not laziness.

3.3.3 Point of View (POV) Statements

 A POV statement frames the problem clearly:

[User] needs [need] because [insight].

👉 Example:

 “College students need affordable, healthy food because they lack

time and cooking facilities.”

 Good POVs are specific, user-centered, and inspiring for ideation.

3.3.4 “How Might We” (HMW) Questions

 Convert POVs into open-ended design challenges.

 Start with “How might we…”

o Encourages possibilities, not fixed solutions.

o Opens space for creativity.

👉 Example:

 POV: “Young professionals need quick dinner options because they

get home late.”

 HMW: “How might we help working people prepare dinner in under

15 minutes?”

3.3.5 Prioritization

 Not all problems are equally important.

 Use tools like:

o Feasibility vs. Impact Matrix – choose problems that are

solvable and impactful.
 o Value vs. Effort Chart – pick high-value, low-effort
opportunities first.

3.3.6 Root Cause Analysis Tools

 Fishbone Diagram (Ishikawa): Categorizes causes under

headings (People, Process, Technology, Environment).

 Mind Mapping: Connects related issues visually.

 Pareto Analysis (80/20 Rule): Focus on vital few causes creating

most of the problems.

3.4 Importance of Reframing

 Many times, the first problem statement is wrong.

 Reframing allows us to look from another angle.

👉 Example:

 Original problem: “How to reduce hospital waiting times?”

 Reframed: “How to make waiting time more comfortable and

productive?”

 This could lead to solutions like entertainment screens, better

communication, or appointment systems — not just adding more
doctors.

3.5 Case Studies in Analyze

1. Reframing Banking Queues

o Bank wanted faster service.

o Analysis revealed customers didn’t mind short waits but hated

uncertainty.
 o Reframed problem: “How might we give transparency about
wait times?”

o Solution: Digital token system showing expected waiting time.

2. School Dropouts in Rural India

o Government assumed poverty was main cause.

o Empathy + analysis revealed that girls dropped out due to

lack of toilets.

o Solution: Build sanitation facilities → reduced dropout rate

significantly.

3.6 Outcomes of Analyze Phase

 Clear problem definition.

 POV statements.

 HMW questions.

 Prioritized opportunity areas.

 Alignment among team members.

3.7 Learning Outcomes of Week 3

By end of Week 3, you should be able to:

 Organize and synthesize empathy data.

 Apply tools like affinity mapping, 5 Whys, and fishbone diagrams.

 Write effective POV statements.

 Frame HMW questions.

 Reframe problems to unlock better solutions.

3.8 Integrated Explanations (Exam-Oriented Content)

 What is the purpose of the Analyze phase?

→ To synthesize raw data from empathy work, uncover real user
needs, and define clear, actionable problems. It prevents solving the
wrong problem.
  How do Point of View (POV) statements help?
→ They condense research into a user-centered problem statement:
“[User] needs [need] because [insight].” This clarity directs the next
ideation phase.

 Why are “How Might We” questions important?

→ They turn problem statements into open-ended, solution-
generating prompts. Instead of locking into one solution, they invite
multiple creative possibilities.

 Why is reframing necessary? Give an example.

→ Reframing changes perspective to reveal hidden opportunities.
Example: Instead of “reduce waiting time,” reframing to “improve
waiting experience” leads to more diverse solutions.

 Which tools can uncover root causes?

→ 5 Whys, Fishbone diagrams, Pareto analysis, and affinity mapping.
Each digs deeper into why a problem occurs.

Week 4 – Solve, Prototype & Test Phase

4.1 Introduction to the Solve Phase

 After empathy and problem definition, we reach the solution

generation stage.

 The goal is not to find the first workable idea, but to explore a
wide range of possibilities.

 This stage thrives on:

o Creativity (quantity over quality in the beginning).

o Divergence → Convergence (start broad, then narrow

down).

o Collaboration (cross-disciplinary input).

4.2 Ideation Principles

 Divergent Thinking → Generating many, often wild ideas without

judgment.

 Convergent Thinking → Narrowing down ideas to those that best

fit the problem.

 “Yes, and…” mindset → Build on others’ ideas instead of

dismissing them.

 Deferral of judgment → All ideas are welcome in the early stage.

4.3 Ideation Techniques

1. Brainstorming

 A structured group activity for idea generation.

 Guidelines:

o Focus on quantity.

o Encourage wild ideas.

o Defer judgment.

o Build on others’ ideas.

o Stay focused on the problem.

 Variants:

o Brainwriting (silent written brainstorming).

o SCAMPER method (Substitute, Combine, Adapt, Modify, Put to

another use, Eliminate, Reverse).

2. Mind Mapping

 Visual representation of ideas around a central theme.

 Helps reveal hidden connections between concepts.

3. Morphological Analysis

 Decompose problem into attributes → generate variations for each

→ combine them.
  Example: Designing a chair → attributes: material, legs, backrest,
adjustability → mix and match.

4. 6 Thinking Hats (De Bono)

 Structured ideation through role-based perspectives:

o White = facts

o Red = emotions

o Black = risks

o Yellow = benefits

o Green = creativity

o Blue = process management

4.4 Prototyping Phase

 A prototype is a simple, low-cost, tangible representation of an

idea.

 Purpose:

o Make ideas visible and testable.

o Collect feedback early.

o Fail fast, fail cheap.

Levels of Prototyping

1. Low-Fidelity

o Paper sketches, storyboards, clay models.

o Quick, cheap, disposable.

2. Mid-Fidelity

o Wireframes, mock-ups, role-playing.

o More detailed but still flexible.

3. High-Fidelity

o Working models, software simulations, functional prototypes.

 o Close to final product.

Prototyping Tools

 Paper & pen, cardboard, 3D printing, digital prototyping tools

(Figma, Sketch), Lego, role-play scenarios.

4.5 Testing Phase

 Testing is not the end but part of the iteration cycle.

 Objective: Validate assumptions, refine ideas, improve usability.

 Process:

1. Select target users (real or representative).

2. Give them the prototype.

3. Observe behavior and collect feedback.

4. Identify what works, what fails.

5. Iterate → redesign → re-test.

4.6 Iteration & Feedback Loop

 Design thinking is non-linear → testing often reveals new problems.

 Iteration cycle: Ideate → Prototype → Test → Refine → Retest.

 Each cycle should reduce uncertainty and bring solution closer

to feasibility and desirability.

4.7 Role of Team Dynamics

 Collaboration is key during solve phase.

 Diverse teams (engineering, design, business, users) → richer ideas.

 Conflict can be constructive if managed well.

4.8 “Fail Early, Fail Cheap” Revisited

 Encourages risk-taking at low cost.

 Prototyping + Testing help eliminate poor ideas early.

 Saves time, money, and effort in later product development.

4.9 Case Studies

1. IDEO Shopping Cart Project

 Redesign of shopping cart using design thinking.

 Multiple prototypes were built quickly.

 Early failures helped uncover safety, usability, and theft-prevention

issues.

2. Post-it Notes (3M)

 Originated as a “failed” adhesive.

 Iterative prototyping and testing revealed its potential as sticky

notes.

4.10 Key Takeaways

 The Solve phase emphasizes creativity and exploration.

 Prototyping makes abstract ideas tangible.

 Testing validates ideas and reveals hidden insights.

 Iteration is central → success comes from cycles of improvement.

 The philosophy: Fail fast, fail cheap, learn more.

Embedded Theory Q&A (for understanding, not exam-style)

 Q: Why do we prototype instead of going directly to final product?

A: To validate ideas cheaply, reduce risk, and ensure user-centered
design.

 Q: How is brainstorming different from traditional idea meetings?

A: Brainstorming emphasizes quantity, suspension of judgment, and
collaboration.

 Q: What’s the importance of iteration in design thinking?

A: Iteration prevents premature solutions, incorporates feedback,
and ensures continuous improvement.