# Assumptions Mapping

## The What

Assumptions Mapping is used to find and check assumptions based on desirability, feasibility, and viability. It helps teams focus on testing high-risk assumptions, lowers uncertainty, and improves decision making.

## The How

Access the hypotheses: **Desirability**: Does the market want this idea? **Feasibility**: Can we deliver at scale? **Viability**: Is the idea profitable enough?

<div align="center"><figure><img src="/files/ubuWpsjtm8wr3PhctG8S" alt="" width="375"><figcaption></figcaption></figure></div>

Map out **Evidence** vs **Importance**

<figure><img src="/files/tpyXK4YsuRb3XAJtxwZB" alt="" width="375"><figcaption></figcaption></figure>

Verify the top right quadrant where **critical assumptions** with little evidence are found

<figure><img src="/files/qInuxXX3QCuV645ai8nG" alt="" width="375"><figcaption></figcaption></figure>

## :scroll: Tips

{% hint style="success" %}
Not all hypotheses are equally important; some may not be critical to the business idea's success
{% endhint %}

<https://www.strategyzer.com/library/how-assumptions-mapping-can-focus-your-teams-on-running-experiments-that-matter>

<https://www.producttalk.org/2023/10/assumption-testing/><br>


---

# 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://jamiewen00.gitbook.io/tech-lead-handbook/product/assumptions-mapping.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.