G31CONTENT

Product feedback synthesis

Pulls product feedback from everywhere it gets mentioned — support tickets, sales call transcripts, customer success notes, public reviews, social channels — and synthesizes it into structured themes the product team can act on. Different from running a survey: this pattern works on unsolicited feedback in its natural form, identifying signals across thousands of mentions that no human would catch by reading individually. Output is themed feedback with weight (how many sources, how recent), severity (how badly does it block customers), and direct links to specific source mentions. Humans interpret and decide what to do with it; the pattern surfaces what's worth interpreting.

WHERE THIS FITS

BUSINESS SHAPES

Product companyDirect-to-consumer

VOLUME THRESHOLD

Below 200 feedback mentions per month a month, the payback rarely earns the build. Patterns this shape reliably pay back at 2,000+.

REQUIREMENTS · 5 REQUIRED, 1 OPTIONAL

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

feedback_source_collection
REQUIREDREADbatch
All the places product feedback shows up. Multiple inputs, one synthesis.
DATA SHAPE
Mentions with source, date, content, author identifier (or anonymous), associated customer if known, severity hint if available.
COMMONLY FILLED BY
- support ticket archive (potentially via A1/A2 patterns)
- call transcripts from A4 if live
- review platform feeds
- social listening tools
- customer success notes archive
- in-app feedback submissions
product_taxonomy
REQUIREDREADcorpus
The structured map of product areas, features, and concerns the feedback gets classified against.
DATA SHAPE
Hierarchical product taxonomy with feature areas, components, user flows.
COMMONLY FILLED BY
- product feature catalog maintained by product team
- structured taxonomy co-authored during engagement
- feature flag system structure that doubles as taxonomy
customer_context_lookup
REQUIREDREADrequest
Who's giving the feedback: their segment, plan, tenure, spend. Weights feedback appropriately.
DATA SHAPE
Per-customer: segment, plan, ARR, tenure, strategic flag.
COMMONLY FILLED BY
- CRM with customer profiles
- billing system with plan and spend
- customer database with segment classifications
theme_destination
REQUIREDWRITEevent
Where synthesized themes land for the product team to consume.
DATA SHAPE
Per-theme: title, description, weight (mention count, customer count, weighted by spend if relevant), severity, trending direction, link to all source mentions.
COMMONLY FILLED BY
- theme dashboard for product team
- weekly digest
- structured feed into product planning workflows
individual_mention_archive
REQUIREDWRITEcorpus
All source mentions remain queryable by anyone wanting to drill from a theme to the actual quotes.
DATA SHAPE
Indexed mentions with classifications, available for filtering and direct review.
COMMONLY FILLED BY
- searchable archive available to product, customer success, support
- structured database with full-text search
- indexed feed used by other patterns
theme_calibration_loop
RECOMMENDEDREAD + WRITEevent
How product team confirms or corrects the synthesis, used for tuning.
DATA SHAPE
Per-theme: feedback on synthesis quality, theme merges/splits, classification corrections.
IF MISSING
Synthesis quality drifts. Strongly recommend even informal weekly product team review.
COMMONLY FILLED BY
- theme review interface for the product team
- structured PM workflow with theme acceptance
- weekly review session

RUNTIME FLOW · 8 STEPS

01
On regular cadence, pull new mentions from all feedback sources
feedback_source_collection
02
Classify each mention against the product taxonomy
product_taxonomy
03
Look up customer context for each mention
customer_context_lookup
04
Cluster mentions into themes; existing themes get extended, new themes get created
05
Compute theme weights factoring in mention count, customer count, customer value, recency trend
06
Archive individual mentions with classifications for drill-down
individual_mention_archive
07
Publish themes to the destination with full evidence trail
theme_destination
08
Capture product team feedback on synthesis quality
theme_calibration_loop

EMISSIONS · 3

Structured outputs this pattern produces. Other patterns and client systems can subscribe to them, which is how the catalog composes over time.

feedback_theme_corpus
Synthesized themes over time, the main signal product planning consumes.
CONSUMED BY
- product roadmap planning
- feature prioritization
- customer success workflows
- executive product reviews
emerging_signal_alert
Themes growing rapidly, surfaced as early warning before they become widespread issues.
CONSUMED BY
- product team daily standups
- customer success alerting
- engineering attention prioritization
segment_specific_signal
Themes that hit specific customer segments differently, useful for segment-aware roadmap decisions.
CONSUMED BY
- segment strategy
- product marketing
- customer success per segment