Use customer language as evidence about how people describe a problem, alternative, outcome and proof—not as copy to paste automatically. Collect exact phrases with context, compare them across relevant customers, translate the underlying meaning into clear language and test the result. Preserve accuracy and brand voice, and obtain permission before using an identifiable quotation publicly.
Capture the situation around the words
A phrase without context is easy to misuse. Record:
- who said it, using an appropriate participant code;
- what had just happened;
- which task or decision they meant;
- whether the phrase described a problem, criterion, outcome or emotion;
- whether it was spontaneous or prompted;
- the source and permission status.
Ask about recent events. “Tell me about the last time this became a problem” produces richer language than “Which of these benefits appeals to you?” Start with customer interview questions for better positioning and keep the question neutral.
Build a language map
Group evidence into message roles:
| Role | What to capture |
|---|---|
| Trigger | what changed and created urgency |
| Problem | concrete difficulty or risk |
| Alternative | how the situation is handled now |
| Outcome | what becomes possible or easier |
| Proof | what creates confidence |
| Objection | what makes the claim doubtful |
| Category | the words used to look for an answer |
Keep meaningful differences by audience or buying stage. The same word can hide different meanings. If “visibility” means pipeline status to a sales leader and workload capacity to an operations lead, a single headline may not serve both.
Use the evidence-matrix method in how to synthesise customer interviews before selecting phrases.
Translate, do not merely transcribe
Good messaging balances three inputs:
- Customer comprehension: language the intended reader recognises.
- Strategic precision: the specific position and value the business has chosen.
- Brand expression: a consistent voice appropriate to the organisation.
Customers may use vague language, internal jargon or technically inaccurate category terms. Your task is to preserve their meaning while improving clarity. A phrase that works in a conversation may not work as a headline. A colourful quotation may be atypical.
Draft several versions, then test comprehension: who is it for, what is offered, what changes and why believe it? Place the chosen language in the hierarchy explained in what belongs in a messaging framework.
Illustrative example
Suppose several operations managers say they are “chasing updates”. The literal headline “Stop chasing updates” is recognisable but incomplete. Context shows the valued change is having a reliable view of project risk before a client meeting.
A clearer message hypothesis might connect both: “See project risks before the client meeting—without chasing every team for updates.” The example is illustrative. It would still need evidence that the product delivers the claim and testing with the intended audience.
Test meaning, not preference
Show the message in a realistic context and ask participants to explain:
- what they think the offer is;
- who it appears to be for;
- which problem it addresses;
- what outcome it promises;
- what is unclear or unconvincing;
- what they would expect next.
Do not ask only “Do you like it?” Preference can reward familiar words without proving comprehension or relevance. Compare the interpretation with your intended meaning and revise the smallest component responsible for confusion.
Limitations and trade-offs
Existing customers know the product and may use learned company language. Prospects may use broader category terms but lack experienced value. Search-query language can reveal demand but not the full buying context. Sales calls are rich sources, yet commercial pressure affects what is said.
Customer language should not overrule legal accuracy, accessibility, product truth or a deliberate brand voice. Nor should an isolated phrase become a market conclusion. Document the source, scope and confidence.
Frequently asked questions
Can we use interview quotations on the website?
Only with appropriate permission and a truthful context. Research consent does not automatically grant marketing approval. When permission is absent, use the evidence to inform original copy rather than publishing the quotation.
Should we keep customers’ jargon?
Keep terminology the intended audience recognises when it improves precision. Explain or replace language that excludes readers, varies between segments or hides the practical meaning.
What if customers use different terms for the same problem?
Map the variants to audience and context. Choose the clearest common term where possible, or use distinct messages for materially different groups rather than forcing false consistency.
Your useful next step
Review five interview notes and collect ten phrases with their full context. Label each trigger, problem, alternative, outcome, proof or objection. Draft one message using the shared meaning, not necessarily the exact words, and test whether readers interpret it as intended. Record approved language and restrictions in the customer research repository.