Design Thinking Process

What is Design Thinking?

Design thinking is a human-centred approach to problem-solving. It is a methodology for creating innovative solutions by deeply understanding the people you are designing for, challenging assumptions, and iterating quickly.

It was popularised by IDEO (a global design firm) and Stanford's d.school, and is now used by teams at Apple, Google, IBM, and thousands of other organisations worldwide.

Design thinking is not just for designers. It is a framework that product managers, engineers, founders, and business leaders use to solve complex problems where the right answer is not obvious from the start.

The Five Stages of Design Thinking

Design thinking is typically described as five stages. These are not strictly sequential -- you move back and forth between them as you learn more.

Stage 1: Empathise

The first stage is about deeply understanding the people you are designing for -- not what you think their problem is, but what it actually is.

Methods:

• User interviews: One-on-one conversations that go beyond surface-level answers
• Observation: Watch people doing the task you are designing for in their natural environment
• Shadowing: Follow a user through their day to understand context
• Empathy mapping: Documenting what users say, do, think, and feel

Key mindset: Come in with curiosity, not assumptions. You are there to learn, not to confirm what you already believe.

Example: Designing a mobile payment app for market traders in Lagos. Before designing anything, spend a week at the market. Watch how traders currently handle money. Ask what their biggest payment headaches are. You will likely discover problems you never anticipated.

Stage 2: Define

After gathering insights from empathising, you synthesise what you learned into a clear problem statement. This is harder than it sounds -- you are going from raw, messy user research to a precise, actionable framing.

The Point of View (POV) Statement:

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

Example:

Market traders in Lagos need a way to receive payments from customers
quickly and reliably because unreliable internet and expensive
data plans make existing mobile payment apps frustrating to use
during busy trading periods.

This statement guides all subsequent design decisions. It is specific, grounded in real user needs, and reveals the underlying "why."

The "How Might We" (HMW) question is a useful tool at this stage:

• "How might we make payment confirmation instant even on low internet connections?"
• "How might we reduce the data needed to process a transaction?"

Stage 3: Ideate

With a clear problem definition, you generate as many solutions as possible. This is the creative, generative stage.

Key principle: Separate ideation from evaluation. Quantity before quality. Wild ideas are welcome -- they often lead to better practical ideas.

Methods:

• Brainstorming: Generate as many ideas as possible in a limited time, no judgment allowed
• SCAMPER: Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse
• Crazy 8s: Sketch 8 different interface ideas in 8 minutes (8 minutes total, 1 minute per sketch)
• Mind mapping: Start with the problem and branch out with related concepts and solutions

After generating many ideas, you narrow down using criteria: feasibility (can we build it?), viability (does the business benefit?), and desirability (do users want it?).

Stage 4: Prototype

A prototype is a rough, early version of your solution used for testing and learning. The goal is to make ideas tangible quickly and cheaply.

Prototype fidelity levels:

• Paper prototype: Hand-drawn sketches on paper. Fastest to create. Great for early concept testing.
• Low-fidelity digital: Wireframes in Figma or similar tools. No colour or images, just layout.
• High-fidelity digital: Polished, clickable mockup that looks and feels close to the final product.

The prototyping mindset: Build to learn, not to impress. A prototype is not the finished product -- it is a hypothesis made tangible.

Prototype the riskiest assumptions first. If users cannot log in successfully in your prototype, testing the dashboard design is premature.

Stage 5: Test

Test your prototype with real users -- ideally the people you interviewed in the empathise stage.

Usability testing approach:

1. Give the user a realistic task to complete ("Imagine you want to send 5,000 NGN to a friend. Walk through how you would do that.")
2. Ask them to think aloud as they go ("Tell me what you are thinking as you do this")
3. Observe without intervening (resist the urge to help)
4. Take notes on where they hesitate, get confused, or make errors
5. Ask follow-up questions after they complete (or fail to complete) the task

What you are looking for:

• Where do users get stuck?
• What do they expect to happen that does not happen?
• What language do they use that differs from yours?
• What delights them?

The Iterative Nature of Design Thinking

Design thinking is not a linear process. Testing reveals problems that send you back to define (was the problem framed correctly?), ideate (what other solutions might work?), or prototype (let us try a different approach).

This iteration is not failure -- it is learning. Every cycle brings you closer to a solution that genuinely works for real users.

Why Design Thinking Produces Better Products

Traditional product development often starts with a solution and builds it. Design thinking starts with users and their needs, then designs a solution.

The difference in outcomes is significant:

• Fewer features built that nobody uses
• Less rework after launch
• Products that users recommend to others
• Faster path to product-market fit

Learning to think in this way -- to start with empathy and test relentlessly -- is the most important mindset shift for any aspiring product designer.