Voice Of Customer Synthesis

<!--
COMMUNITY SKILL — included under its original MIT license.
Source: https://github.com/adam-lagerhausen/b2b-marketing-skills by Adam Lagerhausen (MIT).
License text: ../LICENSE-b2b-marketing-skills.txt
Curated into Growth Marketing OS by Mahmoud Omar (mahmoudomar.com) — this file
is NOT original work by the repo author; see /skills/community/README.md.
-->

Voice of Customer Synthesis

When to use

Use this skill when you have raw customer input and need to turn it into useful product marketing judgment.

Good inputs include:

• Customer interview notes
• Sales call transcripts
• Win/loss notes
• Support tickets or community threads
• Customer advisory board notes
• Gong/Zoom summaries
• Survey verbatims
• Founder or sales-team anecdotes that need structure

Use it before positioning, messaging, launch planning, customer stories, sales narratives, website copy, or enablement. Voice of customer is the currency for PMM. Without it you have opinion. With it you can say, "I talked to 10 customers and here's what they said."

Inputs

Ask for or infer the following:

• Product or company context
• Target audience or segment
• Buyer, decision-maker, user, and influencer if known
• Raw customer notes, transcript excerpts, survey responses, sales notes, or research
• Business model, ACV, market, or GTM motion if relevant
• The desired downstream use: positioning, messaging, launch, sales enablement, customer story, or research synthesis

If the input is thin, still synthesize it, but label conclusions by confidence:

• High confidence: directly supported by multiple customer statements
• Medium confidence: supported by one clear statement or repeated pattern in weaker notes
• Low confidence: plausible inference that needs validation

Workflow

1. Separate customer truth from PMM interpretation

Do not blend quotes, facts, and strategy into one mush.

For each finding, distinguish:

• What the customer actually said
• What behavior or business reality it points to
• What PMM should infer from it
• What still needs validation

2. Identify the audience and buying roles

Clarify who is speaking and who matters in the deal.

Look for:

• End user pain
• Decision-maker pain
• Economic buyer concerns
• Admin or implementation concerns
• Champion language
• Procurement, security, IT, finance, or legal blockers

Do not assume the loudest user is the buyer. Do not assume the buyer is the daily user.

3. Extract the problem before the product

Start with fundamentals:

• Who is the target audience?
• What problem do they have?
• How do they solve it today?
• Why is the current way painful, risky, slow, expensive, or incomplete?
• What event makes the problem urgent now?
• How does the product solve it better?
• What value is created?
• How should GTM let the market know?

Do not jump straight to features.

4. Name the status quo

The real competition is often not another vendor. It is the make-do process customers already tolerate.

Look for current alternatives such as:

• Spreadsheets
• Email threads
• Manual handoffs
• Meetings
• Internal tools
• Consultants or agencies
• Doing nothing
• Waiting until the pain becomes urgent
• A partial tool used outside its intended job

Explain why the status quo persists. Common reasons: no owner, low urgency, switching cost, habit, budget timing, fear of implementation, or the pain is invisible until something breaks.

5. Capture the buyer trigger

Find the specific event that made the customer act.

Use this pattern:

• Situation: the old make-do process
• Trigger: the specific event that made them act
• Solution: how the product made the job better
• Result: the tangible outcome

Triggers can be reactive or proactive.

Reactive buyer moments:

• A failure, missed deadline, customer escalation, audit, outage, lost deal, cost spike, compliance issue, or executive complaint

Proactive buyer moments:

• New team, new market, new regulation, growth target, platform change, strategic initiative, budget cycle, or leadership mandate

6. Translate into Jobs To Be Done

Write jobs in plain buyer language.

Format:

• When [situation/trigger], I need to [job], so I can [desired outcome].

Separate:

• Functional job: the task they need done
• Emotional job: the anxiety, confidence, control, or peace of mind they seek
• Social job: how they need to be perceived by leadership, peers, customers, or their team

7. Pull exact language

Capture short, useful phrases customers actually used.

Prioritize language that is:

• Specific
• Emotional
• Repeated
• Plain-English
• A better alternative to internal jargon
• Close to how a buyer would describe the problem to a peer

Never polish a customer quote until it becomes generic marketing copy. Preserve the edge.