Solve for Pain Point NOT the Solution
Most clients who are new to product sense/design cases often think about solving for the concept and not the user pain.
For Example:
Build an app in the education space >> focus on forcing kids to learn rather than why learning X is important, what problem does it solve.
Improve the cheese shopping experience >> Fixate on the cheese and not the user’s need for the cheese or users pain with cheese.
Design an app for travel >> Focusing on the mechanics of travel rather than the point of travel or the pain of travel.
Don’t forget, we use products because they ultimately solve a problem, not because of the mechanics of the solution.
Let’s look at my favorite product: OpenSnow.
It is a weather app, but the solution isn’t about the mechanics of the weather but rather the decisions I need to make with the weather so that I can enjoy skiing.
Recently they added a water ratio rating for the snow. The solution isn’t about the mechanics of the number but about the decision-making I will do with this information.
