An idea usually starts as a very good sentence. You tell someone; it sounds strong. In your mind the first screen, the logo and even the announcement are already there. But a product is not measured by how beautiful that sentence is. It starts to exist the moment it helps a person do a job more easily, more clearly or more safely.
That is why the question I like to ask at the start is not “What can we build?” but “How is this job done today?” Are people preparing the same file three times? Are they gathering information from different places without being sure it is right? Are the steps needed to make a decision multiplying for no reason? Questions like these are a better starting point than a polished pitch.
The first version does not need to cover every possibility. Often it is better when it does not. Building a small flow that works end to end for one person, in one situation, teaches more. You can see where the user stops, what they ask again and what they skip. These are not assumptions; they are signals coming from the product itself.
There is a trap here: adding every possible feature to a product you started in order to make one job easier. Every new button and every new option asks for a little more explanation. Sometimes progress is not adding a feature but removing one you kept only because you could not decide.
For me, the measure of going from idea to product is this: can someone use it to finish their job, and when the same need comes up the next day, do they want to open it again? If the answer is still no, it does not have to be a bad idea. Maybe the problem is not understood well enough. Maybe we have not talked to the right person. Or maybe the solution is much smaller than we thought.
A good product is not just something that was made. It is something that can say which problem it solves, and show it in the life of the person using it.
◆