21 Customer Interview Questions for Clinicians
Twenty-one questions, split into five groups by what each is built to surface: how a clinician actually works today, where that work hurts, what they already do to cope, who controls the budget if a fix costs money, and whether they'll commit to something real. Every question below is built to survive a clinician who wants to be encouraging rather than honest — which, if you've run one of these interviews before, is most of them.
Quick Answer: Ask about a clinician's actual workflow and past behavior, not their opinion of your idea. The 21 questions below split into five groups — context, pain, workarounds, buying influence, and commitment — each built to dodge the polite, hypothetical answer a busy clinician defaults to when you let them.
Selection criteria: why these questions pass the Mom Test
A clinician interview question earns a place on this list only if it asks about something that already happened, not something that might happen. That's the entire test Rob Fitzpatrick lays out in The Mom Test: people are unreliable narrators of their own future behavior, and unfailingly polite about your idea, but they're accurate — and usually candid — about what they actually did yesterday.
Three filters decide whether a question survives contact with a real clinician.
- Does it ask about the past, not a hypothetical? "Would you use this?" gets a yes from almost anyone. "When was the last time you needed this?" gets a real answer, or an honest "never."
- Does it ask about their life, not your idea? A question that mentions your product invites a compliment. A question about their Tuesday invites the truth.
- Does it produce a specific, checkable detail? "It's frustrating" is an opinion. "I re-enter the same allergy list into three systems every admission" is a fact you can build against.
Clinicians fail this test more often than most interview subjects, for two reasons that compound each other. They're trained to reassure — a bedside habit that doesn't switch off in a conference room — and they're almost always short on time, which pushes them toward the fast, agreeable answer over the slow, honest one. If you want the mechanics of the full conversation these questions live inside — outreach, framing, timing, and debrief — how to interview doctors about your startup idea covers that structure end to end. This piece stays scoped to the questions themselves.
One more filter matters once you're running more than one or two interviews: does the question repeat cleanly across clinicians? Teresa Torres, in Continuous Discovery Habits, argues for treating discovery as a standing weekly habit rather than a one-time research sprint — a handful of clinician conversations every week, compounding into a pattern, beats a single all-day research push that goes stale the moment your product changes. Every question here is phrased to be asked the same way in interview one and interview twenty, so the answers actually stack into a pattern instead of twenty unrelated anecdotes.
Group 1: Context and workflow questions (questions 1-5)
Before you can find pain, you need the shape of an ordinary day. These five questions build that map without ever mentioning your product, which is deliberate — a clinician describing their Tuesday has no reason to perform for you.
- "Walk me through what a typical shift or clinic day looks like for you, start to finish." Trap it avoids: stops you from projecting your own mental model of their job onto the interview.
- "Where in that day does this specific problem area actually come up?" Trap it avoids: locates the exact moment, instead of accepting a vague "sometimes."
- "What systems or tools do you touch to handle that?" Trap it avoids: surfaces the real toolchain, including the shadow spreadsheet nobody put on the vendor list.
- "Who else is involved when that happens — who do you have to loop in?" Trap it avoids: exposes the other stakeholders your product will eventually need to satisfy, not just the person across from you.
- "How often does that specific situation come up — daily, weekly, or rare enough you'd forget it by next month?" Trap it avoids: separates a frequent, budget-worthy annoyance from a memorable but rare edge case.
Group 2: Workflow pain questions (questions 6-9)
Once you have the shape of the day, dig into the moment that actually hurts. Every question here anchors to one specific past instance, because "what's frustrating about X" invites a general complaint while "tell me about the last time X happened" invites a story with details you can act on.
- "Tell me about the last time this specific problem happened. Walk me through exactly what you did." Trap it avoids: forces a concrete story instead of a summarized grievance.
- "What was the most annoying part of that particular instance?" Trap it avoids: narrows a broad "it's all annoying" down to the one step actually worth fixing.
- "What have you already tried to fix or work around it?" Trap it avoids: surfaces prior failed attempts, which tells you what solutions clinicians have already rejected, and why.
- "Roughly how much time does that cost you in a normal week?" Trap it avoids: pushes past "it's a hassle" toward a number, even an imprecise one, that you can compare across interviews.
Group 3: Current workarounds questions (questions 10-13)
Nobody stands still while a problem goes unsolved. This group finds out what a clinician is already doing — because whatever that is, your product has to be a clear upgrade over it, not just an upgrade over nothing.
- "What are you using today to handle that — even if it's a workaround, not a real solution?" Trap it avoids: captures informal tools — a personal spreadsheet, a sticky note, a group text — that a clinician wouldn't volunteer unprompted because they don't consider them "real" answers.
- "Walk me through exactly how you used it, step by step, the last time you did." Trap it avoids: replaces a self-reported summary with an observable sequence you can compare against your own product's flow.
- "What do you actually like about that workaround?" Trap it avoids: surfaces the workaround's real strength, which is usually the thing your pitch has to match before a clinician switches.
- "What made you choose that option instead of the alternatives available to you?" Trap it avoids: exposes the selection criteria clinicians use in practice, which rarely matches the feature list vendors assume matters.
Group 4: Buying influence questions (questions 14-17)
A clinician who loves your product is not the same as a clinician who can buy it. This group maps who actually controls money and process — because in healthcare, as in most institutional buying, the enthusiastic user and the signing authority are frequently different people. Provider, patient, payer, and employer economics split even further apart once money enters the picture, so treat this group as the point where you start testing that split directly instead of assuming the person across from you can say yes.
- "If you wanted to change how this is handled, who would you actually have to convince?" Trap it avoids: names the real decision-maker instead of letting the interview imply the person in front of you has purchasing authority they don't.
- "Has your team or department adopted a new tool or process in the last year? Walk me through how that happened." Trap it avoids: replaces a hypothetical buying process with a real, recent, checkable one.
- "Who controls the budget for something like this?" Trap it avoids: forces a specific role or name instead of a vague "the hospital" or "administration."
- "What would leadership need to see before they'd say yes to something like this?" Trap it avoids: surfaces the actual evidence bar rather than the clinician's personal enthusiasm, which is not the bar that matters.
Group 5: Commitment and closing questions (questions 18-21)
The interview only proved something if it ends with a request for something real — time, an introduction, or a next step with a date attached. A clinician saying "this sounds great" costs them nothing. These four questions each ask for something that does.
- "Would you be willing to try a working version of this with real patients, even a rough one?" Trap it avoids: asks for a real commitment instead of accepting enthusiasm as a substitute for one.
- "Is there anyone else dealing with this you think I should talk to?" Trap it avoids: a genuine referral is one of the strongest signals available — a clinician doesn't spend a colleague's time on something they don't believe in.
- "What would make this a must-have for you, instead of a nice-to-have?" Trap it avoids: forces a concrete bar instead of a soft, deflecting "I'd definitely consider it."
- "What's the one thing that would make you stop using what you use today, tomorrow?" Trap it avoids: names the specific threshold you have to clear, instead of leaving "better" undefined.
Weak clinician questions vs. strong rewrites
The table below pairs common first-draft interview questions with the rewrite that actually produces usable data, plus the specific failure the weak version invites. Use it to audit a draft interview script before you sit down with a real clinician.
| Weak question | Why it fails | Strong rewrite |
|---|---|---|
| "Would you use something like this?" | Invites a polite hypothetical yes with no cost to the clinician | "When was the last time you needed something like this, and what did you do?" |
| "Is this problem frustrating for you?" | Leading — almost guarantees agreement regardless of the real answer | "Tell me about the last time this happened. What did you do next?" |
| "How much would you pay for this?" | Hypothetical pricing questions produce fictional numbers | "What are you spending — in money or time — on your current workaround?" |
| "Do you think doctors need this?" | Asks for a guess about other people instead of their own behavior | "Is this something you deal with, or is it more common for a colleague?" |
| "Does this sound useful to you?" | A compliment question — costs nothing to answer yes | "Would you be willing to try a working version of this with real patients?" |
The pattern across every row is the same: a weak question asks for an opinion about the future, and a strong rewrite asks for a fact about the past. That single substitution is most of what separates a script that flatters you from one that tells you the truth.
Key Takeaways
- Ask about the past, not the hypothetical. "When did this last happen" beats "would you use this" in every group above, because clinicians are accurate about yesterday and unreliable about tomorrow.
- Anchor every question to their life, not your idea. The moment a question mentions your product, you invite a compliment instead of a fact.
- Workarounds tell you what you're actually competing against. A clinician's spreadsheet or sticky-note system is the real baseline your product has to beat, not "doing nothing."
- Buying influence is a separate question from enthusiasm. Map who controls budget and process before you assume the person across from you can say yes — who actually pays in healthcare rarely matches who uses the product.
- Close every interview with an ask, not a wrap-up. A pilot commitment, a referral, or a defined next step is the only proof the conversation produced something real.
- Run this as a steady habit, not a one-time sprint. A handful of clinician interviews every week, asked the same way, compounds into a pattern that a single big research push never produces.
- The 21 questions here are a component, not a complete script. Pair them with how to interview doctors about your startup idea for the full conversation structure, and with the complete guide to customer research for founders for the discipline that applies before you ever sit down with a clinician.
Frequently Asked Questions
How many clinicians should I interview before I trust a pattern?
There's no fixed number, but most founders start seeing a repeatable pattern somewhere around eight to twelve conversations within the same specialty and setting — sooner if the pain is sharp and consistent, later if answers are scattered. Keep interviewing until new conversations stop surfacing new information.
Should I record clinician interviews?
Ask first, and expect some clinicians to decline given how sensitive their work already is around documentation and liability. If they agree, recording frees you to listen instead of scribbling notes; if they decline, write up your notes immediately after the conversation while the specifics are still fresh.
Is it okay to interview clinicians I already know?
Yes, but treat their answers as a starting point, not proof. A clinician who knows you personally is more likely to soften an honest answer into an encouraging one, so weight interviews with strangers more heavily when you're looking for a real pattern.
How is interviewing a clinician different from interviewing a typical B2B buyer?
Clinicians are harder to reach, shorter on time once you have them, and trained to reassure rather than critique — a bedside habit that carries into a discovery call. The questions themselves follow the same Mom Test logic as any B2B interview; the discipline required to actually ask them, instead of drifting into a pitch, has to be tighter.