|
| 1 | +--- |
| 2 | +title: Research Hypothesis Generator |
| 3 | +category: ideation |
| 4 | +subcategory: hypothesis-testing |
| 5 | +description: Turn customer data or internal observations into structured, testable hypotheses for MVP experiments. |
| 6 | +llm_tools: |
| 7 | + - ChatGPT |
| 8 | + - Microsoft Copilot |
| 9 | +inputs: |
| 10 | + - Product or initiative description |
| 11 | + - Goal or desired outcome |
| 12 | + - Relevant customer data or insights |
| 13 | +--- |
| 14 | + |
| 15 | +# Research Hypothesis Generator |
| 16 | + |
| 17 | +Use this prompt when you want to frame experiments or MVPs around clear hypotheses. It works equally well for internal initiatives, feature ideas, or customer-facing changes. |
| 18 | + |
| 19 | +## Prompt |
| 20 | + |
| 21 | +```text |
| 22 | +Generate <N> research hypotheses based on the following context. |
| 23 | +
|
| 24 | +Initiative: |
| 25 | +<Describe the product, service, or internal project> |
| 26 | +
|
| 27 | +Goal: |
| 28 | +<State the desired outcome or metric to improve> |
| 29 | +
|
| 30 | +Customer or User Data: |
| 31 | +<Summarize relevant observations, telemetry, or qualitative insights> |
| 32 | +
|
| 33 | +For each hypothesis: |
| 34 | +- State the hypothesis clearly. |
| 35 | +- Explain the rationale behind it. |
| 36 | +- Suggest a method to test it. |
| 37 | +- Describe potential business or product implications if proven true. |
| 38 | +
|
| 39 | +Ensure the hypotheses are specific, testable, and directly tied to improving the product, customer experience, or internal process. |
| 40 | +``` |
| 41 | + |
| 42 | +> [!TIP] |
| 43 | +> Swap “N” for any number of experiments you need, and tailor the testing methods to match the tools or analytics stack your team relies on. |
| 44 | +
|
| 45 | +## Example |
| 46 | + |
| 47 | +```text |
| 48 | +Generate 3 research hypotheses based on the following context. |
| 49 | +
|
| 50 | +Initiative: |
| 51 | +Improving the onboarding experience for new users of our mobile app. |
| 52 | +
|
| 53 | +Goal: |
| 54 | +Increase the 7-day retention rate by 15%. |
| 55 | +
|
| 56 | +Customer or User Data: |
| 57 | +Recent user interviews indicate that many new users feel overwhelmed by the number of features presented during onboarding. |
| 58 | +
|
| 59 | +For each hypothesis: |
| 60 | +- State the hypothesis clearly. |
| 61 | +- Explain the rationale behind it. |
| 62 | +- Suggest a method to test it. |
| 63 | +- Describe potential business or product implications if proven true. |
| 64 | +
|
| 65 | +Ensure the hypotheses are specific, testable, and directly tied to improving the product, customer experience, or internal process. |
| 66 | +``` |
0 commit comments