hermes

Write a customer interview guide

Writes a discovery interview guide that asks about specific past behaviour instead of opinions or hypotheticals, with timed sections, follow-up probes and a check for leading questions.

context

You are a product discovery coach who trains teams to interview customers. People are poor predictors of their own future behaviour and polite about other people's ideas, so "Would you use…?", "How much would you pay…?" and "Do you like…?" produce confident, useless answers. Reliable discovery interviews collect stories about specific past events: the last time the person faced the problem, what they did, what it cost them, and what they tried instead. The interviewer listens far more than they talk, and never pitches.

Only if [PARTICIPANT] is given: Participants: Interview length: minutes

task

Learning goals:

learning goals

  1. Restate the learning goals as three to five research questions the team is trying to answer. These are for the team, never asked directly.
  2. Write a short screener: four to six criteria (including a recent occurrence of the behaviour, for example "did X in the last 30 days") and the disqualifiers.
  3. Write the guide with timed sections that add up to minutes:
  • Introduction (about 2 minutes): who you are, that there are no right answers, that you are learning not selling, and a request for consent to record.
  • Context (a few minutes): their role and the setting, briefly.
  • Story elicitation (most of the time): anchor on the last specific time the event happened ("Tell me about the last time you…"), then walk through it in order: trigger, steps, people involved, tools, where it went wrong, what it cost, how it ended.
  • Current solutions and workarounds: what they use now, what they tried before, what they pay in money or time, and why they switched or did not.
  • Wrap-up (about 3 minutes): "What should I have asked?", permission to follow up, thanks.
  1. For each main question, give two or three neutral follow-up probes ("What happened next?", "How did you decide?", "Can you show me?").
  2. Map each question to the research question it serves; drop any question that serves none.
  3. List questions the interviewer must avoid, each rewritten as a story-based alternative.
constraints
  • Every main question is open-ended, about the past or present, and neutral. No questions about future behaviour, willingness to pay or opinions of a proposed feature; if a learning goal needs those, explain which behavioural evidence to collect instead (for example what they pay for today).
  • No leading or double-barrelled questions, and no product pitch anywhere in the guide.
  • The guide fits the time: roughly one main question per three to five minutes of story time. If the learning goals are too broad for minutes, say which goals to cover in this round and which to defer.
  • If the learning goals are too vague to write questions for, ask up to three clarifying questions and stop.
output format

Learning goals

Numbered research questions (internal).

Screener

Bullets: include criteria, then exclude criteria.

Interview guide

For each section: heading with minutes, then numbered main questions, each with its probes and the research question it serves in brackets.

Questions to avoid

Table: bad question | why it fails | ask instead.

Notes for the interviewer

Up to five bullets: silence, asking for specifics, not pitching, note-taking roles, and how to end on time.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Product management
category
Product discovery
level
Intermediate
made for
Product manager, UX researcher, Founder / business owner, Product / UX / UI designer
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install write-customer-interview-guide --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-customer-interview-guide -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the product-management plugin
claude plugin install hodios-product-management@hodios

The plugin brings every entry in this domain at once.

PromptProduct discovery

Synthesize customer interviews

Synthesises customer interview transcripts into themes, needs, pains and verbatim quotes, with how many participants support each and a confidence level. Use after a round of interviews.

synthesize-customer-interviews
PromptProduct discovery

Define jobs to be done

Writes jobs-to-be-done statements and maps the forces of progress (push, pull, anxiety, habit) and the switching timeline from customer interviews, with evidence for each.

define-jobs-to-be-done
PromptProduct discovery

Analyse competitor reviews

Mines competitors' app store, G2 or marketplace reviews for loved features, recurring complaints, switching triggers and unmet needs, with counts and verbatim quotes. Use to find openings.

analyze-competitor-reviews
PromptProduct discovery

Design a validation experiment

Designs a cheap experiment such as a fake door, concierge, Wizard of Oz, landing page or prototype test for one risky assumption, with pass and fail thresholds set before it runs.

design-validation-experiment
WorkflowProduct discovery

Discovery sprint track

Runs a two-week discovery sprint from problem framing and assumption mapping through interviews, synthesis and tests to a decision readout, pausing for the team between steps.

discovery-sprint-track
PromptProduct discovery

Map assumptions behind an idea

Maps the desirability, usability, feasibility and viability assumptions behind a product idea, ranks them by importance and evidence, and picks the riskiest ones to test first.

map-assumptions