Design Thinking

Today is #WisdomWednesday ๐Ÿคฉ!

Have you ever had an amazing idea, built a product around it, and found out no one wanted it? I have, plenty of times.

Part of the issue is we started from the solution, but there is a better way.

โญ This is a thread on Design Thinking ๐Ÿงต๐Ÿ‘‡


Creating a product, whether a software, a physical thing, or a service, is all about solving a problem.

๐Ÿ‘‰ Someone has a problem, and you offer a solution.

But we often start with a solution, in the hope that someone wants it, and we end up solving an inexisting problem.


This happens because, in real life, problems are not cleanly written in some kanban board.

โš ๏ธ We often know that something is not right, and we think we know how to solve it but, actually, we don't even have a clear idea of what's wrong.

Enter Design Thinking ๐Ÿ‘‡


Everything stems from these principles:

  • 1๏ธโƒฃ The problem is never well defined.
  • 2๏ธโƒฃ The problem and the solution must co-evolve together.
  • 3๏ธโƒฃ The solution is never completed.

And one key idea:

โญ The human being is the most important element of the solution.


Based on these principles, the process itself is a continuous cycle of five steps:

  • ๐Ÿ”ญ Understand
  • ๐Ÿ“ Define
  • ๐Ÿ’ก Ideate
  • ๐Ÿ› ๏ธ Prototype
  • โš—๏ธ Test

๐Ÿ”ญ You start by observing people, your potential users or clients. Ask yourself:

  • โ“ How are they solving the problem now?
  • โ“ What is their critical pain in doing so?
  • โ“ Why is that happening?

๐Ÿค” These questions sound familiar to you?


Useful tools and practices:

  • ๐Ÿ‘‰ Observation. Just watch people in their routine and take notes.
  • ๐Ÿ‘‰ Interviews, but not with standardized questionnaires; instead, talk openly with people, and listen.
  • ๐Ÿ‘‰ Ask "why" at least 5 times to get to the core of the problems.

๐Ÿ“ Then you have to clearly define one problem to solve. Focus is key here.

A good definition is actionable. It describes a situation that is easy to validate when it has been solved.

๐Ÿ”ฌ Go deep, you don't want to solve the superficial problem but the underlying cause.


Here are some techniques:

  • ๐Ÿ‘‰ Use a board (physical or virtual) and put a note for every potential insight or problem.
  • ๐Ÿ‘‰ Make clusters, group similar problems and insights together.
  • ๐Ÿ‘‰ Select (or vote on) one cluster and write a clear definition of the problem it represents.

๐Ÿ’ก Now it's the fun part, it's time to come up with ideas!

This is the creative part of the process, so don't be afraid to have too many ideas. This is a rare case of quantity before quality.

๐ŸŒฉ๏ธ The best tool is a brainstorming session.


A good brainstorm has these qualities:

  • ๐Ÿ‘‰ Only one person talks at a time, no interruption allowed.
  • ๐Ÿ‘‰ Set a maximum time for each intervention, around 1 minute.
  • ๐Ÿ‘‰ No idea is too crazy or impossible.
  • ๐Ÿ‘‰ Build on top of others: instead of "no, because", just say "yes, and".

๐Ÿ› ๏ธ Next, it's time to finally build something!

Select one, or a few related ideas, and turn it into a prototype. You want to build a Minimum Viable Product (MVP), the smallest piece of functionality that lets you learn something new.

๐Ÿ”ฅ Don't overengineer.


You know you are overengineering when:

  • ๐Ÿ‘‰ You care about how it looks (unless that's the problem).
  • ๐Ÿ‘‰ You care about how fast it is (unless that's the problem).
  • ๐Ÿ‘‰ You feel sad if you have to scrap that prototype.

โš—๏ธ Finally, you have to test that prototype.

If your problem was clearly defined, you should know what a successful evaluation looks like.

๐Ÿ’ฌ This is not about software testing. Test the prototype with real people.


Things to keep in mind:

  • ๐Ÿ‘‰ Shut up and watch, people should discover how the thing works by themselves.
  • ๐Ÿ‘‰ Test with a variety of different profiles.
  • ๐Ÿ‘‰ Write down every complaint you get, but don't mind about the proposed solutions.

Once you reach this phase, you should have an answer to the question "is this problem solved?", which probably is:

๐Ÿ”ธ Somewhat, but the problem was not so well-defined as you thought.

That great! You just completed one cycle and learnt something new.

๐Ÿ” Now start over.


โšก Design Thinking applies not only to software but to any creative process.

Whether you are planning an event, writing a book, building a physical gadget, or launching a service, you can use this strategy.


This is not a bureaucratic methodology you have to follow, nor is a silver bullet. The key idea is this:

๐Ÿ”‘ You're trying to solve someone's problem, so you have to understand them first.

Everything else is just tools to help you do that.


As usual, if you like this topic, reply in this thread or @ me at any time. Feel free to โค๏ธ like and ๐Ÿ” retweet if you think someone else could benefit from knowing this stuff.

๐Ÿงต Read this thread online at https://apiad.net/tweetstorms/wisdomwednesday-designthinking


Stay curious ๐Ÿ––


๐Ÿ—จ๏ธ You can see this tweetstorm as originally posted in this Twitter thread.