Problem to solution(Validation)

I have learnt that sometimes the users we are supposedly creating a solution are not interested in it. They don’t know if they need the solution we are offering because they have found substitutes to solve the problem or to them it’s not a problem at all. They feel like you are creating a problem that they will need your product in order to solve. So the big question to us is whether we are solving a problem or are we creating one so that our product solves it? It’s no science, just by identifying the pain point we can answer this. We should know whether our solution is vitamin or pain killer. These are things we should be able to explain from the word go.

No one wants to work harder or spend more than they have to, if it’s not necessary. Therefore, it’s important to understand whose problem we are solving. Some personal aspects about these people come in handy. Not in the beginning, but later in the process, we see the importance of having such information. In the ideation stage, we can use some of it. This of course is the most brutal stage and it takes so long. We have so many things running in our minds as individuals and also as a team. To come to a consensus and agree on one thing that we are going to work on is not a walk on the park.

Once we have an idea, we need to validate it. We want to validate that the problem we have identified actually exists and that it’s not unique to a few people. We want to create a product that can be used by many people. Secondly, we want to be sure that people are actually willing to pay for our product. Otherwise, what’s the use? We are running a business. The best way to do this is using a prototype. This way, the customers have the feel of how the product will operate and whether or not it is actually solving their problem. Sometimes problems evolve and we need to keep in touch with the customers to be aware when this happens.

In as much as the product is solving the problem, it should be easy to use too. No one wants to do rocket science on the product. They want easy and simple products to use. Starting from the on boarding process to the end of the process, they should be able to navigate through without any problems. Meaning our design should be dope. The product, especially an app should not freeze up! The user doesn’t have time for a mannequin challenge! We need to make sure that doesn’t happen. To make sure every feature works, does what it is supposed to do. The user doesn’t care how it works, he/she just wants it to work, period.

Like what you read? Give Mercy Kinoti a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.