In this week's episode, Ricardo talks about the Problem Statement. He explains that we often receive a problem with a solution from our customers.

The given solution is not always the correct one; before thinking about how to implement the solution, we need to be clearer about what problem our project is trying to solve.

It is necessary to listen to the user and write down everything to understand the problem and question whether there are alternatives beyond the conventional.

Ricardo also gives an example of a problem that already came with a solution, but when the scope of the problem is better understood, we may have several other alternatives.

Listen to the #5minpodcast to know more.