Stop 06 · Design Collaboration & UXTopics · 1/10

Design Thinking

Part of the Product Management Roadmap

In short

Most failed features solve a problem nobody had. Design thinking makes you meet the people first, then build cheap guesses and let real users break them.

A problem-solving approach moving through Empathize, Define, Ideate, Prototype and Test — less a rigid process, more a mindset of staying user-centered before jumping to solutions.

The purple blob as a tailor measures a happy customer, with a paper pattern on the table.

Think of it like this

The tailor who measures first

A good tailor doesn't cut cloth the moment you walk in. He asks where you'll wear it, measures you, makes a paper pattern, and pins a trial fit. Only then does the scissor touch the fabric.

Watch it happen

One idea through the five stages

Empathize
Define
Ideate
Prototype
Test

1/6You sit with five hostel students ordering food late at night. You watch, you don't pitch.

The big ideas

What you need to know

Start with people

Watch and listen to real users before deciding what to build. Your own habits are not the market.

Frame the problem well

A sharp problem statement, like "how might we…", points the whole team at the same target.

Go wide, then narrow

Generate many ideas before picking. The first idea is rarely the best one.

It loops

Test results often send you back to Define or Ideate. That's the method working, not failing.

Save yourself the pain

Common mistakes

Oops

Running one brainstorm and calling it design thinking.

Do this instead

Do the empathy work first and test with real users at the end. Brainstorming is only one stage.

Oops

Building a polished prototype before testing.

Do this instead

Test the cheapest thing that answers your question. Paper beats code at this stage.

Your mission

Run a mini design sprint

~45 min

Quick check

Your test shows users don't understand the problem you solved. What does design thinking suggest?

Go deeper

  1. 1Run a lightweight design thinking pass on a problem you're familiar with.
  2. 2Notice how often teams skip straight to 'Prototype', skipping empathy and definition.
  3. 3Learn the origin (IDEO, Stanford d.school) for more context on where it came from.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge