Identifying Hidden Assumptions

Overview

This prompt is inspired by Teresa Torres' framework for Continuous Discovery Habits, which emphasizes uncovering hidden assumptions, identifying Leap of Faith Assumptions, and testing them effectively. By following this structured five-step process, you'll learn to evaluate your product ideas critically and systematically, ensuring that you're addressing the riskiest parts of your solution early. This prompt is built for teams who need a fast, practical way to move from intention to execution.

In a discovery context, this prompt helps you align stakeholders, surface the right constraints, and structure the output so it is immediately actionable.

Prompt template

You are a product discovery coach helping me uncover and test hidden assumptions, inspired by Teresa Torres' Continuous Discovery Habits.

## Context
{{product_or_solution_summary}}

## Step 1: Surface Hidden Assumptions

Identify 10 assumptions embedded in this product/solution across these categories:
- **Desirability:** Do users actually want this?
- **Usability:** Can users figure out how to use it?
- **Feasibility:** Can we build it with our current capabilities?
- **Viability:** Does it make business sense?

For each assumption, state it as a testable belief:
| # | Assumption | Category | Evidence Strength (None/Weak/Medium/Strong) |
|---|---|---|---|

## Step 2: Identify Leap of Faith Assumptions (LoFAs)

From the 10 assumptions above, select the top 3 that are:
- **Highest risk:** If wrong, the product fails
- **Lowest evidence:** We have little to no data supporting them

These are your Leap of Faith Assumptions. Rank them by risk × uncertainty.

## Step 3: Design an Assumption Test

For the #1 LoFA, design a lightweight test:
- **Assumption to test:** {{selected_assumption}}
- **What we need to learn:** {{learning_goal}}
- **Test method:** {{test_method}} (e.g., interview, smoke test, prototype, survey)
- **Success criteria:** {{success_criteria}} (quantifiable threshold)
- **Timeline:** Completable in 1-2 weeks max
- **Resources needed:** Minimal — what is the cheapest way to learn?

## Step 4: Predict & Plan

Before running the test:
- **Prediction:** What do you expect to find?
- **If validated:** What is the next assumption to test?
- **If invalidated:** How will you pivot — change the solution, the target user, or the problem framing?

## Output Format
Present the full analysis as a structured document with clear tables and actionable next steps.

How to use this prompt

• State the objective and the product context in one sentence.
• Add any constraints such as timeline, target users, or business metrics.
• Ask for a structured output (framework, checklist, or decision summary).

Prompt details