Plan, test, refine
Turn an idea into requirements, a working build, and a product worth using.
3 lessons · Use the arrows or scroll to move between boards.
Messy speech can become a useful product brief.
Jason starts with a long voice dump: the idea, desired outcome, constraints, and whatever else is in his head.
shareHe asks the AI to organize it and ask one question at a time. His “98% confident” prompt means keep probing; it is not a measured confidence level.
shareHe then considers each stakeholder’s needs, access, and integrations before treating the brief as complete.
share
ask one question at a time until you're 98% confident in building a product requirements doc or a PRD
Passing tests is the start of product judgment.
If the domain is unfamiliar, interview the people who will use the product. Then translate their requirements into a technical specification.
shareJason asks for tests alongside implementation, followed by additional checks and user testing.
shareA first build may function while still missing the intended experience. Refinement begins when he can use and judge it.
share
then that's when the real work begins to make the product amazing
The first release can be small without being a dead end.
Jason wants the bigger vision written down early, including what the product may eventually need to support.
shareHe pairs that vision with a phased build: design for the destination, then choose the MVP to implement now.
shareJohn’s example shows the integration problem: useful standalone tools become harder to maintain when their data and workflows must connect.
share
but we're going to do a phased build