I think a lot of product work starts too far downstream. Someone comes with a feature idea, there is excitement around it, and the team starts discussing what it should look like, how it should work, and how quickly it can be built. We sometimes do all of this before being clear about the problem we are actually trying to solve.
For me, good product thinking starts with getting specific about the user's current state. What are they trying to accomplish? Where does the friction come from? How often does it happen? What do they do today instead? A feature is only useful in the context of a problem. The same feature can be valuable for one user and completely irrelevant for another.
This is probably one of the reasons I have become more interested in problem definition over time. The difficult part is often not coming up with a solution. There are usually many possible solutions once the problem is well understood. The difficult part is deciding which problem is worth solving, and understanding it well enough that the product decision becomes much clearer.
That also makes product sense less about having great ideas and more about making good decisions when there is still a lot of ambiguity.