A product cannot be built from vision alone or from a list of customer requests.
Customers can describe the friction they experience. They may also propose useful solutions. The builder contributes technical judgment, product coherence, and a view of what could become possible.
Bring those forms of knowledge together:
- Observe the problem in context rather than collecting feature requests alone.
- Identify the assumption behind a proposed solution.
- Build the smallest useful test.
- Watch what people actually do with it.
- Revise the solution, and when the evidence warrants it, revise the original view of the problem.
Neither customer use nor founder conviction proves that a product is right. Each test adds evidence to the next decision.
Use this workExplore with AI
Explore this journal
Take this work into your preferred AI system. Choose a ready-made prompt or add your own context. Nothing you enter here is sent or saved by utpalmv.com.
Use the work as a thinking lens without adding personal context.
Optional. Add details when you want the exploration grounded in your situation. Your context remains in this page and is included only in the prompt you copy.
