Is this problem really an issue to all?
In order to identify a problem in any situation, we have to understand where this issue appears in the person or organizations daily activity/schedule. What triggers is, what is the main cause of this person’s daily activity? Does this issue arise, and how can it be fixed. By observing and focusing on every part of the person’s hourly activity, various problems and points will start to pop up, and gradually solution ideas will start to become clear.
While we were creating our customer’s journey map based on the problem we identified, we noticed that some of the necessary daily activities a person goes through, there is always room for improvement to make any process more comfortable and more convenient. Coming up with the idea that will solve a major issue that will guarantee people’s interest in using isn’t an easy thing. Putting ourselves in the user’s or end customer’s place, we had to think of every aspect that will affect the user in the future if we had a solution to this specific problem.
Researching and understanding the field that targets the issue we have raised was quite interesting. Sometimes one person might think of a specific point as an issue, but not necessarily to others. While researching and conducting indirect and some “undercover” interviews, we noticed that some of the points we have stated as an issue wasn’t really an issue to everyone. But when we reworded the How Might We question specifying a targeted point, many saw it as an issue that needed to be tackled.
Here is where we experienced the iterative process of design thinking. Going five steps forward, which then took us ten steps backward in order to find a better and more worthy of a solution that will solve this specific issue for the targeted people.
The solution part is the next phase; this is where the excitement will start, and all the creativity will begin to unleash in order to find the ideal solutions and start testing it via the prototypes.
