Decide what to build and how to do it
Reading time: 3 minutes
Last updated
Was this helpful?
Reading time: 3 minutes
Last updated
Was this helpful?
You’ve gathered Insights and explored Opportunities—now it’s time to decide what to build. This stage bridges discovery and delivery, turning ideas into concrete plans. The goal? To make sure your team is working on solutions that truly solve user problems and drive your product forward.
With Timebook, you can connect Opportunities to Solutions and use Assumptions to test ideas, helping you find the best way to improve your product. Let’s dive in!
During the discovery stage of product development, you identify business opportunities based on user feedback. The next step is to develop Solutions—structured approaches to addressing these opportunities. Once validated, Solutions help you confidently decide what to build next and how to approach it.
You can use Opportunity Solution Trees (OSTs) to map out business outcomes and link them to your product discovery items. OSTs help you connect Goals to Opportunities and Solutions, providing a clear view of your product’s objectives, potential improvements, and the paths to achieving them—all in one structured view.
Quick wins with Solutions in Timebook:
Use Solutions to document different ways to address business opportunities.
Leverage the Opportunity Solution Tree (OST) to link Solutions to the relevant Opportunities.
We have a dedicated article explaining Solutions in detail. For more information, see Solution
Solutions act as containers for actual work, bridging the discovery and delivery stages of product development. In Timebook, once you create a Solution, you can populate it with various Work Items, such as Stories, Tasks, Bugs, or Assumptions. These represent the planned efforts to implement the Solution, while Assumptions specifically focus on experimentation and research—helping you determine whether a Solution is worth pursuing.
In Timebook, Assumption is the most common Work Item type to include in your Solutions. An Assumption represents a hypothesis about whether your Solution will work or how it can be best implemented. You can attach multiple Assumptions to a Solution to explore and experiment with different approaches. Use them to document the work needed to test your options and determine the best path for your product development.
Quick wins with Solutions and Assumptions in Timebook:
Populate your Solutions with different types of Work Items to represent the tasks needed to verify or implement them.
Use Assumptions—one of the Work Item types—to document exploration and validation efforts for your Solutions.
Ready to move from discovery to delivery? Use Solutions in Timebook and connect them to Opportunities to track your decision-making process. Then, validate your ideas with Assumptions to ensure you’re building what truly matters. Give it a try in the app or explore other workflows in the Your quick wins in Timebook section:
We have a dedicated article explaining Work Items (including Assumptions) in detail. For more information, see
