What is design thinking & how it can solve the problem faced by a community?
As a design thinker, you need to empathize with the people or the community involved in the process. Understand the people and what is important to them.
Why do we need to empathize?
Unless we interact with humans, we will not be able to understand their core problems. We have to get deep and find out the issues they are facing in their daily lives and try tackling it. The core human behaviour is open to people’s opinions that easily and empathize to understand the physical and emotional needs, how they perceive the world.
Empathize revolves around three main concepts:
- Observe 2. Engage 3. Watch and List
Observing people and environment around you would give you the most clearance on seeing things with a different perspective. We start to intercept things that provide us with more profound insights.
Ask people why it happened, because it invokes a feeling among the people as people are ready to list. Engage in meaningful conversations to arrive at a better conclusion.
Watch and listen is the essential component of a human character as it gives an idea about how the whole world is revolving around you.
After the empathize process, the transition begins by defining the problem. Mapping out the journeys, notes on the behaviour, answers from the people you had interactions with etc. Visualizing is an essential factor for structuring the problem. When you try defining the issues, it helps in framing the point-of-view and narrowing down the problem into a few single statements. Collecting all the puzzles in front of you will lead to discoveries.
In most cases, people try to work on vague issues which lead to time consumption and less productivity.
Having a fixed problem is just like a fixed mindset. You can start building solutions above it.
After you define the problem next step to create a broad range of possibilities or solutions for addressing the issue. This is the mode in the design process where you concentrate on idea generation. It means going wider in terms of possible concepts and outcomes that can be carried out in this scenario.
While creating the key points always remember to keep a track of:
- Step beyond the obvious solutions.
- Create flexibility (variety) and fluency (volume) in your answers.
- Explore the unexplored parts of your problem
Finally, it reaches a point where the brainstorming, mind mapping is completed. The evaluation of ideas needs to take over.
In this mode, you start creating solutions that are quick and cheap to make. If you gain deep insights, it can be more refined into more complex architecture. It’s necessary to understand failure is a part of this overall procedure.
Why do we need to prototype?
- To understand the issues with the prototype
- To test the possibilities
- It gives efficiency and effectiveness.
Last but not the least build things with the people in mind.
And most importantly to fail faster and move on to the next possible solution.
Test mode is when you gain feedback from the user and have another chance to learn empathy for the people you have designed the whole process. Don’t limit your thought to just asking whether people liked the product or not. Know why they loved or what all improvisations could be done on the project.
Do not tell the user about the prototype, but rather check the product and how people will benefit from the product. Also, ask individuals to compare the product with other prototypes available.
Why do we need to test?
- To refine prototypes and solutions
- To learn more about the user
- To make a more precise point of view.
Try adopting this in your real life and make the difference.