Use Customer Interviews in a Deck Without Turning Quotes Into Market Proof

An interview can show you the shape of a problem. It can put an audience inside the moment a coordinator rebuilds a schedule late at night, and it can make that moment feel real in a way no bullet point manages. What it cannot do is tell you how many people live in that moment, what they would pay to leave it, or whether the thing you are building would actually get them out. Most interview slides fail by asking those last three questions of material that only answers the first.

The fix is unglamorous. Keep three things apart, on the slide and in your own head: what the person reported, what your team concluded from it, and what you decided to do next. The UK Government Digital Service's service manual describes analysing a research session in roughly those moves — extract observations, determine findings, decide actions. That page was last updated in 2016, and it comes out of UK government service research, which is neither a US market study nor a seal of approval on any particular workshop. What is worth borrowing is narrow and sturdy: the observation should arrive before the finding drawn from it, and the finding before the action. A quote that jumps straight to a market claim has skipped both steps.

The example in this article is invented, and its notes are paraphrased rather than quoted, because that is the only honest way to show the moves without pretending to a real transcript. Everything it teaches about scale and sourcing is the same whether the notes are yours or made up.

Start with the episode the person described

The invented team here is building a scheduling tool. Before writing anything, they talked to four coordinators of small teams. The coordinators were found by convenience — through the team's own network, not through a sample anyone would call representative. Refer to them as A, B, C and D.

A and B gave accounts that rhymed. Both draft a roster, share it, watch availability shift after it is out, and rebuild it. A put a number on the habit: a couple of evenings a week, she said. C worked differently. C's schedule is fixed well in advance and mostly holds, but it breaks when someone is unexpectedly absent and a replacement has to be found before the shift starts. Then there was D. When the interviewer described an automatic calendar, D said that would be useful.

Three distinctions sit inside those four short paragraphs, and they are the ones a deck tends to blur.

The first is observation versus interpretation. The observation is what was said and heard in the session. It is not a verified account of how the team actually works. You heard a person describe her week; you did not watch it happen. That gap is fine and normal, but it changes the wording you are allowed to use. "A described rebuilding the roster a couple of evenings a week" is a report. "Coordinators rebuild rosters twice a week" is a claim the session cannot support, because you have one person's estimate and no second observer.

The second distinction is between a task and its circumstances. A and B were talking about re-coordinating after a change. C was talking about covering an absence. Those sound like variations on "scheduling is hard," which is exactly the flattening that turns interesting notes into a forgettable slide.

The third is the one that trips up the most careful teams. D's enthusiasm for the automatic calendar arrived after the interviewer put the idea on the table. That makes it a response to a prompt, not a need D raised on her own. It is still real data about how D reacts to a described feature, and it is worth noting. It is not evidence that D independently wants an automated calendar, and it is not evidence the calendar would help. A prompted yes is the easiest thing in a research file to misread, because it sounds like the customer said it.

Group observations without erasing disagreement

With four accounts in hand, the temptation is to sort them into a theme and move on. Do the sorting, but keep the seams visible.

A and B point at the same episode type: work that happens after a roster is shared, when a late change forces a redo. That is a genuine pattern within this set, and it is worth naming. C points somewhere else. C's roster is stable; the failure is an unplanned absence, and the work is finding cover, not re-drafting. C is not a contradicting data point to be averaged away or quietly dropped because the theme was cleaner without her. She marks a condition — how fixed the schedule is — that changes what the problem even is. A schedule that holds is a different environment from one that shifts, and the coordinator's work differs accordingly.

This is the useful move with a lone account: ask what condition it reveals rather than whether it fits. An account that spoils a neat theme is often telling you the theme was too broad.

Two limits belong right next to the finding, not in a footnote the audience never reads. The first is recruitment. Four coordinators, drawn from the team's existing network, all from small teams, is a convenience set. It can tell you these four people described these things. It cannot tell you how common any of it is, and it may over-represent teams the team already knew and liked. The second limit concerns numbers inside an account. A's "couple of evenings a week" is one person's estimate of her own habit. Repeating it as "coordinators spend two evenings a week" quietly promotes a single recollection into a rate. If you want a rate, you need a different instrument.

The word to avoid in this section is "validate." Nothing in four convenience interviews validates anything. It surfaces possibilities, conditions and vocabulary — all useful, none of them proof.

Write the finding at the scale the material supports

Here is where the deck usually overreaches. The tempting slide reads: The market wants an automated calendar. Every part of that sentence outruns the notes. The market was not sampled. The calendar was the interviewer's idea before it was D's. And no one tested whether an automatic calendar would touch either problem A, B or C described.

The narrower finding stays inside what the notes can carry:

Among four convenience-recruited coordinators of small teams, handling change produced two different kinds of coordination work: re-drafting a roster when availability shifted under variable schedules, and finding cover for unplanned absence under fixed schedules. The interviews did not establish how common either pattern is and did not test an automated calendar.

Notice that this finding contains a phrase the participants never used — "two different kinds of coordination work." That is yours. It is the interpretation, and marking it as yours is what keeps the slide honest. The participants described a rebuild and a search for cover; you noticed they were two species of the same genus. Say so. An audience trusts a team that shows where its own reasoning entered, because it can then judge the reasoning instead of having to take it on faith.

The UK Government Digital Service sequence is useful here for the same reason it was useful at the start: it will not let a finding masquerade as an observation. That guide is about service research in government, and it does not turn a qualitative quote into a population estimate. Neither does anything else.

A table can hold the whole thing without pretending to more rigor than exists:

Now the quote question. A short excerpt — or, better here, a paraphrase — can make the shape of an episode legible. It can show an audience what "rebuilding the roster" actually looked like at nine at night. It cannot show frequency, willingness to pay, or the effect of a product that has not been built. Select excerpts that keep the speaker's meaning intact, trim only the identifying detail the deck genuinely needs, and check the recording or notes before you print anything as a quotation. A sentence lifted past the point where it still means what the person meant is not a stronger slide; it is a liability waiting for someone in the room who was also in the interview.

Show what the finding changes next

A finding that changes nothing is decoration. So the last move is to say what happens because of it, and to keep the uncertainty honest where the material has not resolved it.

In the invented case, the decision is not "build the automatic calendar." It is to investigate the two workflows separately, because the notes suggest they are not the same problem wearing different clothes. For the variable-schedule coordinators, that might mean following a real roster cycle as it changes rather than asking about it afterward. For the fixed-schedule coordinator's world, it means looking at how absence cover actually gets arranged, which may have nothing to do with a calendar feature. Those are two research questions, not one validated feature.

This is a smaller decision than the original slide wanted, and that is the point. The slide wanted "the market wants an automated calendar," which would have justified building it. The notes support something more modest and more useful: here are two kinds of coordination work, here is where each one lives, and here is the next thing we need to learn about each. An audience that is deciding whether to fund the next step can act on that. An audience handed a market claim it suspects is really four people in a room tends to discount the whole deck, including the parts that were solid.

The bounded finding, in one sentence, is this: two of four convenience-recruited coordinators described rebuilding rosters after late availability changes, a third described a different problem entirely, and a fourth responded favorably to a feature the interviewer introduced — so the next move is to study the two workflows on their own terms rather than to declare a calendar validated. Retain C's account and D's prompt in the room, because they are the difference between a slide that tells the truth about its evidence and one that recruits four people's words to prove a conclusion the interviews never reached.

Frequently asked questions

What can an interview quote honestly show in a deck?

It can make a problem's shape legible, such as a coordinator rebuilding a schedule late at night. It cannot establish how many people share that experience, what they would pay, or whether a product would help. Keep what the person reported, what the team concluded, and what the team decided next as separate steps.

How should a favorable reaction to a feature the interviewer described be treated?

As a response to a prompt, not as a spontaneous need statement. In the invented example, D called an automatic calendar useful only after the interviewer introduced it. That is real data about reaction to a described feature, but it does not show independent demand or that the calendar would help.

What should a team do when one participant's account does not fit the emerging theme?

Ask what condition the account reveals instead of averaging it away or dropping it. In the invented set, A and B described re-drafting after availability changed; C described finding cover when a fixed schedule broke. C marks how fixed the schedule is, which can change what the problem is.

What limits belong beside findings from convenience-recruited interviews?

The set can say these particular people described these things, not how common any pattern is. Four coordinators drawn from the team's network, all from small teams, may over-represent teams the team already knew. A participant's estimate, like 'a couple of evenings a week,' is one recollection, not a rate.

How can a deck phrase a finding without overreaching?

Write at the scale the notes support and mark the team's interpretation as the team's. The article's narrow finding is that among four convenience-recruited coordinators, handling change produced two different kinds of coordination work, while the interviews did not establish commonness or test an automated calendar. 'The market wants an automated calendar' outruns the notes.

Further reading

• Build an Internal Decision Deck Around the Choice That Is Still Open — Once the interview material enters a decision meeting, use this to frame the deck around the choice still open and give every slide a job.