Write a user interview script for this research goal.
Context:
- What I am trying to learn: {{the decision this research feeds, e.g. whether to build X, why trials stall in week 2}}
- Who I am interviewing: {{role, how they relate to the product, how many interviews are booked}}
- Product or workflow in question: {{one or two sentences}}
- What I already believe: {{the assumption I am most tempted to confirm}}
Rules for every question you write:
- Anchor it in a specific past instance: "tell me about the last time you..." rather than "would you use..." or "how often do you...". People are accurate about what happened and generous about what they might do.
- No pitching. The interviewee should not be able to tell what we hope to hear. Rewrite any question that leaks the assumption I listed above.
- Follow the money and the effort. What they currently pay for, cobble together, or tolerate around this problem says more than any stated interest.
Structure the script as:
1. A two-minute opener that sets expectations and gets permission to record, without describing our product idea.
2. Three warm-up questions that establish their actual workflow today.
3. Five or six core questions, each anchored to a specific recent instance, ordered so early answers give context for later probes.
4. For each core question: two follow-up probes for when the answer stays vague, and a note on what a strong signal sounds like versus a polite answer.
5. A closing question that asks who else feels this problem, plus a debrief template I fill in within ten minutes of hanging up: what they did, what they paid or endured, what surprised me, and which of my assumptions took damage.
At the end, list the three ways this script could still mislead me (sampling, question order, my own reactions) and what to watch for in the first two interviews before running the rest.user-researchinterviewsdiscovery