What is Design Thinking?

Design Thinking in One Sentence

Design thinking is a human-centred way of solving problems: you start with the people who have the problem, not with the solution you already like. It was popularised by IDEO and the Stanford d.school, and today it shapes how product teams at Google, Flutterwave, Moniepoint and thousands of startups decide what to build.

In Module 1 you met the idea. In this module you will practise it with real tools: personas, journey maps and "How Might We" questions.

---

The Five Stages

1. Empathise

Understand the people you are designing for. Watch them, interview them and, where possible, do the task yourself. If you are designing a bus-ticketing app for Lagos commuters, ride the BRT at 7am. You will learn more in one crowded morning than in a week of desk research.

Outputs: interview notes, observations, photos, quotes.

2. Define

Turn what you learned into a clear problem statement. A good one names the user, their need and the insight behind it:

Market traders in Onitsha need a way to record credit sales quickly, because they serve several customers at once and forget who owes what.

Outputs: personas, empathy maps, a problem statement.

3. Ideate

Generate many possible solutions before judging any of them. Quantity leads to quality. Crazy 8s (eight sketches in eight minutes), brainstorming and "How Might We" questions all help here.

Outputs: sketches, sticky notes, a shortlist of ideas.

4. Prototype

Build cheap, quick versions of your best ideas: paper sketches, clickable Figma screens, even a WhatsApp flow run by a human behind the scenes. A prototype is a question you can hold in your hand.

Outputs: paper prototypes, wireframes, clickable prototypes.

5. Test

Put the prototype in front of real users and watch what happens. Do not defend your design. Listen, take notes and learn.

Outputs: usability findings, a list of changes, new questions.

---

It Is Not a Straight Line

The five stages are drawn left to right, but real projects loop. Testing often sends you back to Define because you discover the real problem was different. A Kenyan agritech team building a crop-price app learned in testing that farmers did not need more prices. They needed to know which buyer would actually turn up. That insight sent them back to the start, and the product that shipped was far better for it.

Think of the stages as modes you switch between, not a checklist you complete once.

---

Why Companies Care

• It reduces waste. Building the wrong feature is the most expensive mistake a team can make. A two-day prototype test can save a three-month build.
• It aligns teams. Engineers, PMs and designers argue less when decisions rest on evidence from users.
• It works in low-resource settings. You do not need a lab or a big budget. A notebook, a phone camera and five conversations are enough to start.

---

Common Mistakes

• Skipping Empathise because "we already know our users". You usually do not.
• Falling in love with the first idea. Ideation should be wide before it is narrow.
• Testing with friends. They are kind to you. Real users are honest.
• Treating it as a one-off workshop instead of a habit built into every sprint.

---

Try It in the Lab

The lab on the right lists real activities from design projects. Sort each one into the stage it belongs to, then check your answers. Some are deliberately tricky. Read the explanation when you get one wrong.