user-interview-guide

$npx mdskill add Significant-Gravitas/skills-catalog/user-interview-guide

Use this before a round of discovery or feedback calls.

SKILL.md

.github/skills/user-interview-guideView on GitHub ↗
---
name: "user-interview-guide"
description: "Write an interview guide with a goal, screener, open questions, and a note template."
triggers: ["user interview", "interview questions", "customer discovery", "research guide", "discovery call"]
version: "1"
---

# User interview guide

Use this before a round of discovery or feedback calls.

## Set the learning goal

State what the team needs to learn and the decision it will inform. List
what you already know, with sources, and what you assume. Write a short
screener: who qualifies, who does not, and how many people you aim to talk
to.

## Write the questions

Keep the call to 30 to 45 minutes:

- warm-up: their role and a normal week;
- the last time they did the task, step by step;
- what was hard, what they tried, and what it cost them;
- tools or workarounds they use today;
- close: anything we did not ask, and who else to talk to.

Ask about past behaviour, not future wishes. Use open questions. Do not
pitch, name the planned feature, or ask "would you use". Mark the must-ask
questions if time runs short.

## Note template

Give a template with the participant, date, segment, key moments in their own
words, problems observed, surprises, and follow-ups. Keep quotes and
interpretation in separate columns.

Do not contact participants or schedule calls yourself. Never invent a quote
or write up an interview that has not happened.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.