Stop 01 · UI/UX Design FoundationsTopics · 5/9

Design Thinking Fundamentals

In short

Design thinking is a fancy name for a simple habit: understand people first, try cheap ideas, learn fast. You can use it for an app, a hostel problem or a college event.

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 jaadu hands out small breakfast packets to sleepy students rushing to class.

Think of it like this

Fixing the hostel breakfast

Half the hostel skips breakfast. Instead of adding more dishes, you ask why. Turns out it ends at 8:30 and class starts at 9. So you try a grab-and-go packet for one week and see who takes it.

Watch it happen

The five modes, using the breakfast problem

Empathise

Define

Ideate

Prototype

Test

1/5Talk to students who skip breakfast and watch the mess at 8 am. Listen, don't pitch ideas yet.

The big ideas

What you need to know

Start with empathy

Understand the person's real situation and feelings before deciding anything. Your own guess is just a starting point.

Frame it as 'How might we'

'How might we make breakfast fit a rushed morning?' invites many ideas instead of one fixed answer.

Cheap prototypes win

A paper sketch or a one-week trial teaches you more than a month of discussion.

Not a straight line

Testing often sends you back to empathise or define. The modes are a loop you keep going round.

Save yourself the pain

Common mistakes

Oops

Running one brainstorm with sticky notes and calling it design thinking.

Do this instead

The sticky notes are the easy part. Talking to real people and testing ideas is what makes it work.

Oops

Building the full solution before testing anything.

Do this instead

Test the smallest version first. If nobody picks up the 30 packets, you've saved a lot of money.

Your mission

Design-think one campus problem

~45 min

Quick check

Your team has a great idea but hasn't spoken to a single user. Which mode did they skip?

Go deeper

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