# Decide what to build and how to do it

## **From discovery to delivery: Making the right choices**

You’ve gathered [Insights](/hc/product-guide/core-concepts-and-objects/research-and-planning-objects/insight.md) and explored [Opportunities](/hc/product-guide/core-concepts-and-objects/research-and-planning-objects/opportunity.md)—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!

***

## Solutions: Tools to address product opportunities

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.

<div align="left"><figure><img src="/files/WoAg4oSghWvP9b6D5wNH" alt=""><figcaption><p>Timebook has a dedicated module to manage all Solutions in one place.</p></figcaption></figure></div>

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](/hc/product-guide/strategy-objects/goal.md) to [Opportunities](/hc/product-guide/core-concepts-and-objects/research-and-planning-objects/opportunity.md) and Solutions, providing a clear view of your product’s objectives, potential improvements, and the paths to achieving them—all in one structured view.

<div align="left"><figure><img src="/files/QqQLutflO4dnlC6HFVOy" alt=""><figcaption><p>Use the OST feature to map out your Opportunities and connect relevant Solutions to them.</p></figcaption></figure></div>

{% hint style="success" %}
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](/hc/product-guide/core-concepts-and-objects/timebook-objects/solution.md)
{% endhint %}

***

## Assumptions: Put your Solutions to the test

**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](/hc/product-guide/core-concepts-and-objects/delivery-objects/work-item.md), 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.

<div align="left"><figure><img src="/files/tyJ6hRfM3iQISu3CRDDl" alt=""><figcaption><p>This Solution contains different types of Work Items: Stories, Tasks, and Assumptions.</p></figcaption></figure></div>

In Timebook, **Assumption** is the most common [Work Item](/hc/product-guide/core-concepts-and-objects/delivery-objects/work-item.md) 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.

<div align="left"><figure><img src="/files/JqO1ZWatPvE6ZmQjKEJv" alt=""><figcaption><p>A typical Assumption in Timebook, linked to a specific Solution.</p></figcaption></figure></div>

{% hint style="success" %}
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.

We have a dedicated article explaining Work Items (including Assumptions) in detail. For more information, see [Work Item](/hc/product-guide/core-concepts-and-objects/delivery-objects/work-item.md#work-items-for-discovery-and-delivery)
{% endhint %}

***

## Get started today!

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:

[Build your strategy](/hc/legacy/your-quick-wins-in-timebook/build-your-strategy.md)

[Clarify the needs](/hc/legacy/your-quick-wins-in-timebook/clarify-the-needs.md)

[Define product opportunities](/hc/legacy/your-quick-wins-in-timebook/define-product-opportunities.md)

[Manage delivery and resources](/hc/legacy/your-quick-wins-in-timebook/manage-delivery-and-resources.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.timebook.ai/hc/legacy/your-quick-wins-in-timebook/decide-what-to-build-and-how-to-do-it.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.