Start with one user and one problem
Write down who the product is for and what they cannot easily do today. Describe the outcome rather than a list of screens. This gives design and engineering a shared definition of value.
Define the smallest useful release
Separate essential workflows from enhancements. A first release should complete a meaningful task from beginning to end. A long feature list is less useful than a clear sequence of actions.
Map constraints early
List the platforms, integrations, data types, ownership requirements, budget range, and target timing. Unknowns are normal; recording them makes discovery more productive.
Prepare a short project brief
Include the problem, target users, three essential features, examples you admire, and what success looks like. Use our project inquiry to start the conversation.