User Interview Guide (Problem Discovery)

How to use User Interview Guide (Problem Discovery)

Use this template as a starting point for research, interviews, user-interviews. Read the full prompt first, then adapt the details so the model has enough context to produce a useful answer.

1. Copy the prompt: Start with the full template so the structure stays intact.
2. Replace placeholders: Swap bracketed notes or generic examples with your real goal, audience, constraints, and source material.
3. Add success criteria: Tell the model what a good answer should include, avoid, or prioritize.
4. Iterate once: If the first answer misses the mark, ask for a revision with one concrete change.

Prompt engineering tips

• Use the tags as guardrails: Keep the output focused on research, interviews, user-interviews.
• Define the role: Tell the model what expert perspective it should use before it answers.
• Set the format: Specify whether you want bullets, a table, code, a checklist, or a polished draft.

Best use cases

User Interview Guide (Problem Discovery) is most useful for people working on research and interviews. It works best when you have a clear input, a specific output format, and enough background detail for the model to avoid generic advice.

• Turn a rough idea into a structured first draft.
• Create a repeatable workflow for research, interviews, user-interviews.
• Compare several options before choosing the final direction.

Customization checklist

Before running the prompt, add the details that make your situation different from a generic example. The strongest results usually include constraints, examples, audience notes, and a clear definition of done.

• Add your audience, product, role, industry, or project context.
• Include examples of what good and bad output looks like.
• Ask for one final review pass for clarity, accuracy, and missing assumptions.