Use Claude to Turn Customer Interview Notes into a Quote-to-Theme Matrix

Customer interviews are easy to summarize badly. A polished paragraph can hide which words came from a customer, which pattern appears more than once, and which question the notes do not answer.

This guide uses Claude to create a quote-to-theme matrix from two fictional interviews. The artifact helps a product or commercial team decide what to investigate next. It does not measure customer demand or choose a roadmap item.

Evidence label: Documentation-based and illustrative. The file upload and project steps come from Claude’s current help documentation. The interviews and sample output are fictional. No Claude session or customer research result is claimed.

What you will make

You will create a table with:

an exact quote or a short source excerpt
the interview and speaker label
a cautious theme
supporting or conflicting evidence
an open question
a suggested next check

The decision is whether a theme is ready for a follow-up question, not whether it is proven.

Prerequisites

Use Claude on a surface where file uploads are available. Claude’s help documentation lists TXT, DOCX, PDF, CSV and other supported formats. You can attach files with the plus button and choose Add files or photos, or place them in a Project’s Files section for reference across chats. Availability, limits and workspace rules vary, so confirm the current surface before using real material.

Create these two fictional text files, or paste their complete contents into one chat.

interview-ana.txt

Interview: Ana, operations manager at Northstar Foods
Date: 12 October 2026

"Our weekly stock report takes about an hour to assemble because the warehouse export and the finance sheet use different product names."

"I can usually spot the obvious gaps, but I do not trust a report that changes a number without showing me the source row."

"The painful part is not writing the update. It is finding out which number needs checking before the meeting."

interview-omar.txt

Interview: Omar, finance lead at Northstar Foods
Date: 14 October 2026

"The report is useful once it is reconciled. The handoff is where we lose time."

"If a tool gives us a clean exception list with the original row beside it, I would review that. I would not let it update the ledger."

"We have not agreed which product-name differences are harmless and which ones need a correction."

Use approved notes for real research. Do not upload personal data or confidential interviews unless your policy allows that surface and use.

Three steps

1. Attach the bounded source set

Start a new Claude chat and attach both files. If your account uses a Claude Project for this work, add the files to the project’s Files section and open a chat inside that project. Keep unrelated sales or roadmap material out of the exercise.

2. Ask for a traceable matrix

Paste this prompt after the files are attached:

Create a quote-to-theme matrix from only the two attached interview files.

Return a table with these columns:
Interview | Exact quote or short excerpt | Theme | Evidence status | Supporting or conflicting source | Open question | Next check

Rules:
- Use only the attached files.
- Quote the source exactly where possible. Do not combine two quotes into one.
- Treat a theme as a tentative interpretation, not a customer fact.
- Mark a theme SUPPORTED when at least two separate interviews support a similar point.
- Mark it SINGLE SOURCE when only one interview supports it.
- Mark it CONFLICTING when the interviews point in different directions.
- Do not invent frequency, urgency, willingness to pay, a roadmap priority, a time saving, or a customer segment.
- Do not turn a request into a purchase commitment.
- If the notes do not answer a question, write UNKNOWN.

End with:
1. Three follow-up questions, each tied to a source gap.
2. Claims the team must not make from these two interviews.
3. A short list of possible next checks that do not change a source system.

3. Check the matrix before making a decision

Read each row beside the original files. The phrases about an exception list and not changing the ledger belong to different people, so the matrix should preserve both the shared need and the boundary around it.

A useful follow-up question might ask which product-name differences are safe to ignore. It should not claim that most customers have the same problem, that the team will buy a tool, or that the workflow saves an hour.

Checkable artifact

You should have:

a matrix with source-linked quotes
a status on every theme
open questions tied to missing evidence
a next-check list that does not make an external change

If a row has no quote or source file, remove it or mark it for review.

Acceptance checks

The workflow passes when:

every quote can be found in one of the two files
Ana and Omar remain separate interview sources
the shared reconciliation problem is not presented as measured demand
the ledger boundary is preserved
unsupported urgency, revenue, savings and buying claims remain absent
the next step is a question or a reversible check

Troubleshooting

Claude writes a smooth summary instead of a matrix. Ask it to return one row per source excerpt and include the exact quote column. Do not accept a paragraph as a replacement for traceability.

Every theme is marked supported. Add A single interview is not enough for SUPPORTED and ask for a source-count column. A larger table does not create more evidence.

A quote is shortened until its meaning changes. Compare the shortened excerpt with the source and restore the full sentence or mark it as an editor summary.

The files are not available on your surface. Paste the complete fictional text inside <source> tags, or use a surface approved for the files. Do not broaden access just to complete the exercise.

Limits and decision

This workflow organizes qualitative notes. It does not prove market demand, rank customers, calculate return, or decide a product roadmap. Two interviews can suggest a follow-up question. They cannot support a population claim.

TRY it for a small set of approved interviews when a researcher can check each quote.

SKIP it when the notes contain sensitive information that the chosen surface is not approved to receive, or when the team needs statistically representative evidence.

USE the matrix when a human has checked the quotes, theme status and next question.

For a related source-grounded workflow, see Use a Claude Project to Turn Product Notes into a Source-Linked FAQ. The next task is to write one approved follow-up question before collecting more notes.

Want one practical AI-for-work lesson each week? Join The Weekly Verdict.