Customer signal arrives in four kinds. Each one tells you something different about the same product, and none of them is sufficient on its own.
01. Explicit voice
Customers writing or speaking, directly to you, on purpose. Support tickets. Survey responses — NPS, CSAT, CES. Feature requests in a public board. Discovery-call transcripts. Sales-call notes. Reviews on G2, Capterra and Trustpilot. Social posts that mention the product. In-app feedback widgets at the moment of friction. Churn-exit surveys at the moment of leaving.
Explicit voice tells you what customers think they want. It is the loudest layer, the easiest to collect, and the most structurally biased. Research consistently finds that 90% or more of dissatisfied customers leave without saying anything. For every customer who complains, something like 26 stay silent. Most VoC programmes hear from 4 to 7 percent of their customer base. The vocal minority is rarely the representative one — they are the delighted, the angry, the power user, and the customer whose support workflow leaves a paper trail.
Examples a software team will recognise:
- A support ticket from a designer at a Series B SaaS: "the Slack listener works fine for #product but silently drops everything from #product-emea — we noticed because the European team stopped getting follow-ups."
- A G2 review from a Cursor-using team: "spec generation is fast, file paths are right, but the link to the original customer quote breaks for any spec longer than three sections."
- A discovery-call moment, captured in a Fireflies transcript: "...so we just use a shared Google Doc instead because we can't link it to a customer record."
- A thumbs-down on an in-app survey, followed by free text: "I just want to export this to Linear without reformatting it."
02. Implicit behaviour
What customers do, regardless of what they say. Product usage analytics. Feature-adoption curves. Drop-off in critical funnels. Time on task. Support-ticket volume per surface. Repeated workaround patterns visible in session replay. Rage clicks, dead clicks, error clicks — the frustration signals product analytics tools surface automatically. NPS detractor verbatims correlated with declining usage.
Behaviour tells you what customers really need. It catches the customers who never report. It also catches the gap between what was asked for and what works. When voice and behaviour agree, the priority is clear. When they disagree, the disagreement is the priority.
Examples:
- A customer's session replay shows three failed attempts to invite a teammate, each blocked by a "workspace not found" error. They never opened a ticket. They didn't come back.
- Adoption of a new spec-sharing feature is 8% after two weeks. The customers who churned in the same window all had the feature available. The feature works fine; the onboarding hint that surfaces it doesn't.
- Rage clicks on the "Generate Spec" button — flagged automatically by your product-analytics tool — cluster around customers whose repos are above 50,000 files. The generation works but the loading state never updates.
03. Ambient and external
What is happening around the customer, in the wider market. Community forum activity — Reddit, Discord, Hacker News, niche Slack groups. Competitor mentions surfacing in your own feedback. Comparison reviews on third-party sites. Twitter and LinkedIn conversation. Conference and industry-event chatter. Market-research reports.
Ambient signal is what tells you when the conversation has moved. Voice and behaviour are about the customer's relationship with your product. Ambient is about the customer's relationship with the category — and the category is what determines whether the next thing you build will land.
Examples:
- A Reddit thread in r/ProductManagement compares four AI-spec tools. Your product is not in it. The top three comments name your two largest competitors.
- A Hacker News thread on "what's broken about AI coding tools" surfaces a class of complaint your team has been hearing in support tickets — now framed as the field's problem, not your product's.
- Two competitors ship MCP servers in the same fortnight. Your sales team mentions it in five out of seven calls.
04. Observability and system signal
What customers feel but never directly report. Error rates. Performance regressions. Core Web Vitals. Latency in the long tail — the 95th and 99th percentile that most dashboards hide. Integration failure rates. Webhook delivery rates. Cache misses at peak.
Most product organisations treat observability as an engineering signal. It is also a customer feedback signal — the most honest one, because customers don't have to remember to file it. The performance regression that pushes a workflow from one second to four seconds will surface in retention long before it surfaces in feedback. A customer-obsessed system reads it.
Examples:
- Webhook delivery failures above five megabytes silently drop for the three customers who built the biggest integrations. They feel the lag; they never report it. They mention "the product feels unreliable" in their next NPS — and the team has no way to connect the two.
- Spec-generation p95 latency drifts from 2s to 9s after a model swap. Volume of generated specs drops 18%. Nobody opens a ticket. Engagement quietly fades.
- The Slack integration's token refresh fails for workspaces that haven't reconnected in six months. Feedback collection drops to zero for those accounts. They appear in the dashboard as "no signal" rather than "signal broken".
Voice says what customers think they want. Behaviour says what they really do. Ambient says what they will want next. Observability says what is quietly costing them.
None of these layers is sufficient. A roadmap built only on voice is built for the loudest customers. A roadmap built only on behaviour is built for the workflows that already exist, not the ones that should. A roadmap built only on ambient is built for the market, not the customer. A roadmap built only on observability is built for the engineer, not the user. Customer feedback management as a discipline reads all four at once, and surfaces the priority where they converge — or where they diverge in a way that demands attention.