Customer interviews framework: facts, examples and context

A framework for interviewing usually means a running order for one conversation. That is the least valuable part. One conversation goes well or badly on its own; a round of them either answers a question or does not, and the difference is decided before the first call.

So this is a design for a round: the question it answers, who is in it, when it stops, and what it hands to the decision waiting on the other side.

What to take away

• A round exists to answer one question and feed one decision. If you cannot name the decision, do not book the calls.
• Design the sample and the stopping rule before you speak to anyone. Both become unarguable once results start arriving.
• Run rounds in small batches with a write-up between, so what you learn can change who you call next.

The six fields

Fill these in before anything is scheduled. It takes twenty minutes and it is the whole framework.

Field	What goes in it	Failing version
The question	One thing this round is meant to establish	"Learn more about our users"
The decision	What you will do differently depending on the answer	Nothing, or something you would do anyway
The sample frame	Who counts, and where you will find them	"Anyone in the industry"
The screener	Two or three factual questions that admit or exclude	Asking whether they are interested
The stopping rule	What tells you the round is finished	A target number of calls
The write-up	Where notes go, and in what shape	Separate documents nobody rereads

The second row kills bad rounds. If both answers lead to the same next step, the round is entertainment, and it will still take three weeks.

Writing the screener

A screener is factual, short, and answerable before you meet. It asks what someone does, not what they think.

Good screening questions have an answer you could check: which tool they use, how often something happened last month, whether they hold a particular role, who they buy from. Bad ones ask whether the topic matters to them, which everyone answers yes to when a stranger is asking. The wording is worth more care than a screener usually gets: how far phrasing and order move an answer is documented at length in the guidance on writing survey questions.

Keep the people you screened out. A list of those who looked right and turned out not to have the problem is a description of your boundary, and boundaries are hard to see any other way.

The stopping rule

Not a number of calls. The rule is about what the calls are producing.

Stop when two or three conversations in a row change nothing in your written problem statement, and you can predict what the next person will say about their current method before they say it. That is saturation for this segment, and the wording matters: for this segment. A round of people you could reach easily saturates fast and tells you nothing about anyone else. The counts worth keeping show how to tell the two apart.

Continue past that point only if the sample frame changes. A new segment is a new round, with its own question and its own screener.

Batches, not a schedule

Book three or four, then stop and write them up. Then decide who to call next.

Booking twelve in advance locks the sample to what you believed on the day you booked. Half the value of early conversations is that they tell you the wrong people are on your list, and a full calendar makes that discovery useless.

Between batches, ask two questions. Did anything change in the written statement? And is there now a kind of person we should be talking to and are not? Those two are the reason to run in batches at all.

The write-up shape

Three columns, one row per conversation, never merged.

• Said. What the person reported, in their words where they were specific.
• Observed. What you saw: two systems open, the file they could not find, the pause before the price.
• Concluded. Your reading. This is the part that will be wrong later, which is why it lives in its own column.

Add two fields beside them: how you got to this person, and what surprised you. The first tells you whether your evidence is about a market or about your address book. The second is the only field containing anything you could not have written in advance.

What the round hands over

A round should end with a written change or a written confirmation, dated, and one of these outcomes.

• The problem statement is narrower, and you can name the segment it now describes.
• You have a list of people who looked right and are not, which is your boundary.
• You know who authorizes a purchase and what a precedent looks like.
• You have the vocabulary customers actually use, which is what your offer will have to be written in.

A round that produced none of these produced encouragement. Run the next one with a different sample rather than more calls, since more of the same sample cannot fix a sampling problem.

Where the framework stops

Interviews can establish what happens today, what it costs, and who decides. They cannot establish that anyone will pay, and they cannot count anything: sizing runs on published sources and a bottom-up chain instead, which is the work the SBA's outline of market research and competitive analysis describes. No number of rounds changes that, because a description is not a transaction. The next evidence comes from a specific offer at a specific price that somebody can refuse.

That is a different apparatus with a different unit of evidence: see minimum viable offers for keeping the first one small, and market validation for the counting work interviews cannot do.

Common questions

How many rounds does a project need?

One per segment you are serious about, plus a repeat whenever the problem statement has changed enough that your screener would now admit different people. Usually two or three, not ten.

Can one round answer two questions?

Only if the same conversation produces evidence for both without the questions interfering. Usually the second changes how you ask the first, and you end up with two half-answers. The claim by claim discipline in the discovery framework applies here too.

What if I cannot fill the sample frame?

That is a finding, and an important one. Being unable to reach twenty of the people you claim to serve is a distribution problem sitting in front of everything else, and it does not improve after you build.

Do I need a formal discussion guide?

A short one: three or four openings and a list of things you want to reach, not a script. What makes a conversation productive is following the friction wherever it goes, and the guide's job is to stop you forgetting the buyer question, not to fix the order. Customer interviews covers the moves inside the room.