Start with the decision your notes need to inform
Customer interview notes become useful when they help you make a specific decision. Before sorting them, write down the question you are trying to answer. A freelance designer might ask, “Where do clients get stuck before approving a proposal?” A small support team might ask, “Which parts of onboarding require too much help?” These questions are narrow enough to guide action, but open enough to leave room for unexpected answers.
Gather notes from the conversations that relate to that question. Keep enough context to understand each comment: the type of customer, what they were trying to do, and what prompted the remark. You do not need a perfect transcript. You do need to avoid turning a brief note such as “pricing confusing” into a confident claim about what the customer meant. If a detail is unclear, mark it as unclear rather than filling in the gap.
Handle notes with care. Remove names or identifying details when they are not needed for the decision, and share only what colleagues need to see. This makes it easier to discuss customer experiences without treating private information as general team material.
Separate observations from interpretations
As you review each interview, distinguish what the person said or did from what you think it means. Suppose a prospect says, “I sent the proposal to my colleague and waited a week.” That is an observation. “Our price is too high” is one possible interpretation, but the delay could also involve approval rules, an unclear scope or a busy colleague. Keeping those layers separate prevents an early guess from becoming the basis of your plan.
A simple note format can help: record the situation, the customer’s words or behavior, your possible explanation, and any unanswered question. For example: “Needed an estimate before booking; asked whether revisions were included; may be worried about extra work charges; follow up on how they compare estimates.” Where possible, preserve a short phrase in the customer’s own words. It may reveal a distinction that your summary would erase.
Do not force every note into a problem category. Customers may describe workarounds they like, expectations you already meet, or constraints you cannot change. Those details help you understand which parts of the experience to preserve as well as which ones might need improvement.
Group notes into themes without losing the exceptions
Next, look across conversations for notes about the same task, friction or desired outcome. You could group them under plain-language labels such as “unclear next step after inquiry,” “difficulty comparing service options” or “needs internal approval.” A theme should describe what customers experience, not prescribe your preferred solution. “Customers cannot tell what happens after they submit the form” is more useful at this stage than “Add an automated email.”
For each theme, note which conversations support it and whether the situations were similar. Three comments from people buying different services may not point to one shared problem. Conversely, one detailed account of a serious obstacle may deserve attention even if nobody else mentioned it. Interview notes show what happened in these conversations; they do not, by themselves, tell you how common an issue is across all customers.
Keep a small space for exceptions and conflicting accounts. If one client wants more calls while another prefers fewer, the insight may be that communication preferences vary. The action could be to ask about preferred contact at the start of a project rather than impose one schedule on everyone.
Translate a theme into a decision you can test
Choose a theme by considering its relevance to your current goal, the difficulty it creates for customers, and your ability to address it. You do not need a complicated scoring system. A short written rationale is often enough: “Several prospects asked what the starter package includes, and clarifying it is within our control.” This makes the choice understandable later, even if you decide to change course.
Turn the theme into a statement that connects evidence to action. For example: “Prospects asked about revision limits before agreeing to the starter package, so we will make those limits clearer in the proposal and listen for remaining questions.” That is more actionable than “Improve sales.” It also avoids claiming that the change will increase bookings.
Start with a manageable change. You might revise one proposal section, add a brief onboarding checklist or change the order of questions on an inquiry form. Decide what you will watch for before making the change: fewer clarification emails about revision limits, for instance, or customers being able to explain the next step in their own words.
Close the loop and keep learning
After trying a change, compare what happens with the question that started the review. Did customers understand the revised proposal, or did they ask a different set of questions? Did the checklist help them begin, or did it add work? Combine what you observe in day-to-day interactions with follow-up conversations when appropriate. A quiet inbox alone does not prove that everything is clear.
Keep a brief record of the theme, supporting notes, decision, change and result. This gives your team a way to revisit its reasoning instead of repeatedly sorting the same notes from scratch. If the result is mixed, narrow the question: perhaps the explanation works for returning clients but not for first-time buyers. Actionable insights are not final verdicts about customers. They are grounded starting points for improving how you serve them.
