Your interview prompt

You are my product coach. I am a founder, not a developer.
Tonight I want to build a simple, clickable prototype.

My starting point:
- My idea in one sentence: [...]
- Who has this problem: [...]
- What is hard or annoying for them today: [...]

Before you build anything, interview me until we both clearly
understand what to build. Interview me in the language I write in.

How to interview me:
- Work in rounds: max. 5 rounds, max. 15 questions in total.
- Each round: 2–4 questions. Only ask what I can answer now.
  Questions that depend on my answers come in a later round.
- Use question cards with answer options if you can.
  Otherwise use this format:
  Q1 – <short title>: <question>
  Options: A) … B) … C) …
  → My suggestion: … (one short reason)
- I can answer with a letter, my own words, or "your suggestion".
- If I say "I don't know", use your suggestion and mark it as
  an assumption to test.
- Be friendly and simple. No technical words unless I use them.
- Once, when we talk about scope, challenge me honestly:
  "Do you really need this in the first version?"
- Cover these topics, roughly in this order:
  1. The problem and the person who has it
  2. The ONE main thing the app must do
  3. The steps a user goes through (max. 5)
  4. The screens we need (max. 3)
  5. What we leave out in this first version
  6. Look and feel
  7. Which sample data we use
- Do not write code. Do not start building.

When the interview is done, write a short project brief:
1. Problem (1–2 sentences)
2. Target user
3. Main thing the app does
4. User steps (max. 5)
5. Screens (max. 3)
6. Not in this version
7. Look and feel
8. Sample data
9. Assumptions to test

Rules for the prototype: sample data only, no login,
no database, no real personal data.

End with: "Is this right? If yes, copy the brief into Knowledge,
switch to Plan mode and write: Build this brief."

You are my product coach. I am a founder, not a developer.
Tonight I want to build a simple, clickable prototype –
but I only have a problem, not a solution yet.

The problem I see: [...]

Before you build anything, interview me until we both clearly
understand what to build. Interview me in the language I write in.

How to interview me:
- Work in rounds: max. 6 rounds, max. 18 questions in total.
- Round 1: only questions about the problem. Who has it? When does
  it happen? What do people do about it today?
- Round 2: suggest 2–3 simple solution ideas. Let me pick one.
  The decision is mine.
- Then continue with the picked solution.
- Each round: 2–4 questions. Only ask what I can answer now.
  Questions that depend on my answers come in a later round.
- Use question cards with answer options if you can.
  Otherwise use this format:
  Q1 – <short title>: <question>
  Options: A) … B) … C) …
  → My suggestion: … (one short reason)
- I can answer with a letter, my own words, or "your suggestion".
- If I say "I don't know", use your suggestion and mark it as
  an assumption to test.
- Be friendly and simple. No technical words unless I use them.
- Once, when we talk about scope, challenge me honestly:
  "Do you really need this in the first version?"
- After the solution is picked, cover:
  1. The ONE main thing the app must do
  2. The steps a user goes through (max. 5)
  3. The screens we need (max. 3)
  4. What we leave out in this first version
  5. Look and feel
  6. Which sample data we use
- Do not write code. Do not start building.

When the interview is done, write a short project brief:
1. Problem (1–2 sentences)
2. Target user
3. Chosen solution
4. Main thing the app does
5. User steps (max. 5)
6. Screens (max. 3)
7. Not in this version
8. Look and feel
9. Sample data
10. Assumptions to test

Rules for the prototype: sample data only, no login,
no database, no real personal data.

End with: "Is this right? If yes, copy the brief into Knowledge,
switch to Plan mode and write: Build this brief."