Module 1: The Design Thinking Mindset
Why Design Thinking Works
Many products, services and projects fail not because they were built badly but because they solved the wrong problem, or solved the right problem in a way people did not want. Design thinking is a practical, human-centred approach to problem solving that reduces this risk. It asks you to understand people deeply, frame the problem carefully, generate many ideas and test them cheaply before committing serious time and money. This course will teach you how to use it on real challenges at work, in a business or in your community.
What design thinking is
Design thinking is a structured way of solving problems that borrows methods designers have long used and makes them available to anyone. It became widely known through the design firm IDEO and the Hasso Plattner Institute of Design at Stanford University, often called the d.school. It is not only about visual design. Teams use it to design services, processes, policies, apps, products, customer experiences and even internal ways of working.
Three ideas sit at its heart:
- Human-centred: start from the needs, behaviours and context of the people you are designing for, not from your own assumptions or the technology you already have.
- Iterative: move in short cycles of making something and learning from it, rather than one long plan executed once.
- Experimental: treat ideas as hypotheses to test, so failures are small, early and cheap.
Why it works
Design thinking works because it tackles the most common reasons new solutions fail:
| Common cause of failure | How design thinking responds |
|---|---|
| The team assumes it knows what users need | Research with real users before deciding |
| The problem is defined too narrowly or wrongly | Spend time framing the problem from the user's point of view |
| The first idea is chosen too quickly | Generate many options before narrowing down |
| Large sums are spent before learning | Build quick, cheap prototypes and test them early |
| Different departments see only their part | Use cross-functional teams and shared visual tools |
It also helps teams handle uncertainty. When a problem is new or poorly understood, detailed upfront planning often fails because the plan rests on guesses. Design thinking replaces guesses with evidence gathered step by step.
Balancing desirability, feasibility and viability
A useful framework popularised by IDEO says strong solutions sit where three things overlap:
- Desirability: do people actually want this, and does it meet a real need?
- Feasibility: can we build or deliver it with available technology, skills and resources?
- Viability: can it be sustained financially or organisationally?
Design thinking starts with desirability, because that is where teams most often make mistakes, but a good solution must pass all three tests.
Worked example: a savings group app that nobody used
Imagine a small fintech start-up in Nairobi builds an app to help chamas, informal savings groups, record contributions. The team assumes members want detailed reports and charts. After months of development the app launches, but few groups use it. When the team finally visits several chama meetings, they learn that the treasurer, often managing records on paper or in a phone notebook, is the key user, that members mainly want quick confirmation that their contribution was received, and that many members prefer simple SMS messages to installing another app.
Had the team used design thinking from the start, they would have spoken to treasurers and members first, framed the problem as "treasurers need a quick, trusted way to confirm contributions to members", tested a paper or SMS prototype within days, and avoided building features nobody needed. This is a hypothetical scenario, but the pattern is very common.
Common mistakes to avoid
- Treating design thinking as a one-day brainstorm. Ideas without research and testing are still guesses.
- Thinking it is only for designers. Anyone can learn and use the methods.
- Skipping straight to solutions. The time spent understanding users and framing the problem is what makes the solutions better.
- Ignoring feasibility and viability. A loved solution that cannot be delivered or paid for is not a solution.
Exercise
Think of a product, service or process you know that failed or that people avoid using. Write down what its creators probably assumed about users. Then list two things you would ask or observe with real users to test those assumptions, and say which of desirability, feasibility or viability was most likely the weak point.
Key points
- Design thinking is a human-centred, iterative and experimental approach to solving problems.
- It reduces failure by researching users, framing problems carefully and testing cheaply.
- Strong solutions are desirable, feasible and viable.
- Anyone can use it, not just designers.