Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rampstackco/user-feedback-aggregation
Collecting and synthesizing user feedback across channels (support tickets, NPS, in-app feedback, sales calls, social mentions, customer councils) into a continuous signal that informs product decisions. The triage discipline that distinguishes loudest-voice (whoever complains most wins) from averaged-noise (every signal weighted equally) from triaged-synthesis (signal weighted by source quality, frequency, and decision relevance).
Passed 18 of 22 test cases with the skill, and 16 of 22 without it.
3 fixed15 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finished conducting 15 structured discovery interviews with healthcare administrators to evaluate concepts for a new scheduling portal. I have all 15 transcript files ready. Please write a research synthesis report summarizing key findings, theme clusters, and recommendations for this specific interview batch. Provide a structured research synthesis output based on these completed interviews.
| Checked | Without skill | With skill |
|---|---|---|
| Synthesizes findings specifically from the provided batch of 15 interviews. | Missed | Passed |
| Does not apply continuous always-on multi-channel triage workflows to this discrete research batch. | Passed | Passed |
The instructions your model reads when the skill loads.
A senior product leader's playbook for collecting and synthesizing user feedback across channels into continuous decision signal. Support tickets, NPS surveys, in-app feedback, sales calls, social mentions, customer councils, all aggregated into a triaged synthesis the team can actually act on.
Most product programs accumulate feedback they do not use. Channels overflow with submissions; CSAT and NPS scores get reported in monthly updates; customer council meetings produce notes that nobody references. The loudest voices steer roadmap because they are easiest to hear; quieter signal that matters more goes unaddressed.
This skill is the triage discipline that turns continuous feedback streams into continuous decision signal. Each channel surfaces different signal at different reliability. Each signal type warrants different weight in different decisions. The team that aggregates feedback well makes better decisions; the team that drowns in feedback makes the same decisions they would have made without the feedback.
Different from discovery-research-synthesis, which covers one-off research projects (a defined batch of artifacts, a defined synthesis output). This skill covers the always-on streams: feedback that arrives every day, every week, every month, and that the team must continuously triage and synthesize.
The voice is the senior product leader who has watched feedback aggregation work and watched it fail. Concrete, opinionated about which channels matter for which decisions, willing to call out where loudest-voice or averaged-noise patterns produce bad outcomes.
When to use this skill: building a feedback aggregation system, auditing a feedback program that is producing volume without decisions, deciding which feedback channels matter for the program, or designing the synthesis cadence for ongoing feedback streams.
This skill spans continuous user-feedback aggregation. The PM-skill distinction:
discovery-research-synthesis is one-off discovery research. Defined batch, defined output.user-feedback-aggregation (this skill) is ongoing feedback streams. Always-on channels needing continuous synthesis.beta-program-management covers feedback specific to beta participants. This skill spans all users continuously.ux-research is structured research projects. This skill is unsolicited feedback.pm-spec-writing is downstream: specs use feedback aggregation as input.roadmap-planning is downstream: roadmap uses feedback patterns as input.The audience: senior PMs, product directors, customer success and support managers running feedback programs, in-house teams aggregating feedback across many channels.
What is not in scope: structured discovery research (covered by discovery-research-synthesis); beta-specific feedback (covered by beta-program-management); commissioned research projects (covered by ux-research).
The keystone framing.
Loudest-voice. Whoever complains the most gets their feature. Vocal minorities steer roadmap. Silent majority's needs go unaddressed. The squeaky-wheel anti-pattern. Cost: the program optimizes for the loudest customer, not for the broader customer base; quieter customers leave for products that addressed their needs.
Averaged-noise. Every signal weighted equally. 1 enterprise customer's feedback = 1 trial user's feedback = 1 angry social mention. Volume aggregates without weighting; noise drowns signal. Cost: the team cannot tell which feedback matters; decisions get made on aggregate sentiment that does not reflect the customers who matter most for the strategy.
test cases passed, vs 16 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.