Research workflow

Create a neutral customer interview guide

Use existing feedback to ask better questions without turning assumptions into conclusions.

◦ Documented~18 minutes · EstimateBeginner

Start with these inputs

  • Anonymized feedback or support themes
  • What you want to learn
  • Interview length and participant type

Follow the workflow

  1. Remove names and sensitive details from the feedback.
  2. Paste the learning goals and interview constraints into Claude.
  3. Rewrite any question that suggests the answer you want to hear.
  4. Pilot the guide with one willing participant and adjust its length.

Your starting prompt

PERSONALIZE THE [BRACKETS] BEFORE USING
Design a [minutes]-minute interview guide for [participant type] using the feedback below.
Write an opening, six neutral questions, useful follow-ups, and a closing. Ask about recent real behavior before opinions. Avoid leading questions, product pitches, and questions that assume the problem exists.
For each question, show the learning goal. List assumptions in a separate section. Do not claim the feedback is representative of the market or invent customer quotes.
Learning goals: [list]
Feedback: [paste anonymized feedback]

Three workflows. One useful email.

Practical guides, copyable prompts, and a short review tip. Every Tuesday. Confirm your email to join; unsubscribe anytime.

Get the weekly workflows

What the output could look like

Illustrative example, not a recorded test result.

Illustrative example using invented sample inputs: Question: Walk me through the last time you organized information from several documents. Follow-up: Where did you pause or redo something? Learning goal: understand the current process before asking about tools.
Review before you use it.
The guide is a research draft. Feedback themes are not evidence of market size or willingness to pay. Time is an approximate planning estimate, not a measured result. Free access has usage limits; features can vary by account.

Sources & review notes

By AI Flow Finder · Reviewed October 14, 2026. Documented means this guide is based on the sources above. It has not yet passed a recorded end-to-end workflow test. Tool access and limits can change.

Pass on a useful workflow