People who make great products or services share certain skills. It is not a fancy qualification. It is not natural talent. It is a simple way of thinking called Design Thinking.
It is important to identify these skills so that we can also pick them up.
Why Can't We Just Wing It?
"Why not just build the thing and fix problems later?" A lot of teams do this. Most of them end up with a product that nobody uses.
The difference between a product people love and one that nobody touches is simple. The winning team actually understood the people they were building for. The losing team just guessed.
So What Is Design Thinking?
Design thinking is a way of solving problems that does two things:
It puts the user first, you think about the real people who will use your product, not just your own ideas about them.
It focuses on solutions, instead of spending all your time talking about what is wrong, you spend your time building what could be right. I know this is hard. The normal human instinct when something breaks is to find the person responsible and make it their problem. Design thinking says that is a waste of everyone's time. Find the fix instead.
For example. A company notices its staff avoid using the new internal system. The old way is to scream at employees, threaten them with warnings, make them write reports, or send the classic "please refer to the training manual" email that nobody reads. The design thinking way is to sit with employees, watch them use the system, and find out the main button is hidden on the wrong page. Then you move the button. Simple solution. Real impact.
The thing that makes all of this work is empathy. This means you genuinely care about how other people feel and what they go through. Without this, you are just building things for yourself and hoping others like them.
Design Thinking Framework
The design thinking process can be broken down into three steps:
- Explore
- Create
- Implement
1. Explore — Go and See
This is the step most people skip. It is also the most important one.
Before you build anything, go talk to real people. Watch how they do things today. Ask questions. Listen more than you talk. Ask "why" again and again until you find the real problem hiding under the surface.
You are not trying to prove your idea is right. You are trying to learn something that surprises you. If nothing surprises you, you have not talked to enough people.
2. Create — Try Many Ideas
Most people think this is where design thinking starts. It is not. But this is where the fun begins.
First, write down every idea you have. Even the silly ones. Linus Pauling said the way to get good ideas is to get lots of ideas and throw the bad ones away. So write them all down first.
Then, pick your best ideas and build a rough version of each one. This is called a prototype. It does not have to look good. It just has to be something a real person can try.
A paper drawing is fine. A simple clickable screen is fine. Anything that lets a real human say "I like this" or "this does not make sense" is good enough. As Reid Hoffman said, "If you are not embarrassed by the first version of your product, you've launched too late." You are not trying to get it perfect. You are trying to get feedback fast.
3. Implement — Ship It and Keep Learning
When you finally launch, the work is not done. Watch how people actually use what you built. It will surprise you. Take what you learn and go back to step one.
The best teams never really stop exploring. Every version they ship teaches them something for the next one.
This Is Not Just for Designers
Design thinking is not about colours and fonts. Anyone can use it. A nurse, a teacher, a software developer, a shop owner, if you solve problems for other people, this way of thinking is for you.
The skills are simple: be curious, care about people, try many ideas before picking one, and test before you polish.
Start practising them today. Next time you face a hard problem, do not sit and stare at it. Go talk to the person who has the problem. Build the simplest possible answer. Then learn from what happens.
