rampstackco/claude-skills / skills/user-feedback-aggregation
user-feedback-aggregation
VerifiedCollecting 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). Triggers on user feedback, customer feedback aggregation, NPS, support ticket analysis, customer councils, feedback synthesis, voice of customer, feedback triage, in-app feedback. Also triggers when feedback channels overflow with volume that does not produce decisions, when the loudest-voice problem is steering roadmap, or when continuous feedback streams need synthesis discipline.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 366 B |
| SKILL.md | skill md | 20.4 KB |
| references/categorization-and-tagging-at-scale.md | markdown | 9.7 KB |
| references/channel-source-weighting.md | markdown | 10.9 KB |
| references/channel-types-and-what-each-surfaces.md | markdown | 11.2 KB |
| references/closing-the-loop-with-users.md | markdown | 9.5 KB |
| references/common-feedback-aggregation-failures.md | markdown | 10.3 KB |
| references/detecting-drift-in-feedback.md | markdown | 9.5 KB |
| references/frequency-vs-intensity.md | markdown | 9.6 KB |
| references/from-feedback-to-product-decision.md | markdown | 9.8 KB |
| references/tooling-considerations.md | markdown | 8.9 KB |
references/detecting-drift-in-feedback.md
View on GitHub# Detecting drift in feedback
Drift patterns. Investigation discipline. Drift as early signal of change.
Feedback signal changes over time. Volume in a category increases or decreases; new patterns emerge; old patterns disappear; sentiment shifts. The team that detects drift early often catches issues before they compound; the team that does not detect drift often discovers problems after they are large.
---
## The drift patterns
Common ways feedback signal changes over time.
### Increasing volume in a category
**Signal.** Feedback volume in a specific area is rising over weeks or months.
**Possible causes.**
- The issue is worsening.
- The user base is growing (more total volume across all categories).
- Awareness of the channel is increasing (more users finding the feedback channel).
- Recent product changes introduced or amplified an issue.
**The investigation.** Look at the cause:
- Is the percentage of total feedback in this category increasing? (If yes, this category is growing relative to others; the issue is real, not just user-base growth.)
- Did recent product changes affect this area? (Often the cause when volume increases sharply.)
- Are users describing similar issues in different ways? (Could be one underlying issue surfacing through multiple feedback styles.)
### Decreasing volume in a category
**Signal.** Feedback volume in a specific area is declining over weeks or months.
**Possible causes.**
- The issue was resolved.
- Users gave up reporting (resignation rather than satisfaction).
- The user base shifted (fewer users in the affected segment).
- Channel access changed (users stopped using the feedback channel for this category).
**The investigation.** Decreasing volume can be good or bad:
- If a fix shipped and volume dropped: fix worked.
- If no fix shipped but volume dropped: investigate. Are users churning? Are they working around the issue silently?
### New patterns emerging
**Signal.** Feedback that was rare or non-existent starts appearing more frequently.
**Possible causes.**
- Recent product changes introduced new patterns.
- Market conditions changed (new competitors, new user expectations).
- User base expansion brought new use cases.
- Existing users developed new workflows.
**The investigation.** Investigate the cause; new patterns often inform roadmap decisions.
### Patterns disappearing
**Signal.** Feedback patterns that used to be common stop appearing.
**Possible causes.**
- Product changes addressed the issue.
- Users migrated away from the affected workflows.
- The user base shifted.
**The investigation.** Validate that the disappearance reflects resolution, not silent abandonment.
### Sentiment shifts
**Signal.** Aggregate sentiment (NPS, CSAT, in-app rating) trends differently than before.
**Possible causes.**
- Specific changes affected sentiment.
- External factors (market conditions, competitor actions, news cycles).
- User base composition changed.
- Cumulative experience changes that the team did not flag individually.
**The investigation.** Sentiment shifts warrant root-cause analysis; both improvements and degradations are informative.
---
## The drift detection cadence
When the team checks for drift.
**Weekly:** quick scans for sharp drift in critical categories. Sharp increases in support volume on specific issues, sudden NPS drops, viral social mentions.
**Monthly:** systematic review of category-level trends. Compare the past month to prior months. Identify categories with significant increases or decreases.
**Quarterly:** strategic drift review. Long-term trends, sentiment shifts, emerging patterns. Pairs with quarterly strategic synthesis.
**Annually:** taxonomy and aggregate drift. Are tag categories still appropriate? Has the user base composition changed? Long-term sentiment trends.
---
## Tooling for drift detection
What infrastructure helps catch drift.
**Trend dashboards.** Time-series views of feedback volume per category. Visual surfacing of changes.
**Threshold alerts.** Automated alerts when a category's volume changes significantly (e.g., 50%+ increase week-over-week).
**Sentiment tracking.** NPS or CSAT trends over time, segmented by user segment and product area.
**Cross-channel views.** Aggregate trends across channels surface patterns that single-channel views miss.
**Period comparisons.** Compare current period to prior periods (this month vs last month, this quarter vs same quarter last year).
The tooling supports detection; humans interpret.
---
## Investigation discipline
When drift is detected, what to investigate.
**The questions.**
- What changed in the product or in the user base that could explain the drift?
- Is the drift persistent or a temporary spike?
- Is the drift segment-specific or universal?
- Is the drift correlated with other signals (churn, engagement, support volume)?
- What is the underlying cause vs the surface signal?
**The investigation methodology.**
- Pull a sample of feedback from the drifting category.
- Compare it to feedback in the same category from before the drift started.
- Identify what changed: language, contexts, severity, user segments.
- Map to product changes or external events that could explain.
- Form a hypothesis; test it through additional investigation.
---
## Drift as early signal
Drift often signals issues before they become large.
**The leading-indicator pattern.**
- A category's volume starts increasing.
- The team investigates and identifies the cause.
- The cause is addressed before it affects more users.
Without drift detection, the same issue might compound for months before the team notices.
**Worked example.**
- Support tickets in the "configuration step 3" category increase 30% in two weeks.
- Investigation reveals: a recent change to the configuration form introduced a confusing default.
- The change is reverted or fixed within a week.
- Without drift detection, the issue might have continued for months, affecting many more users.
---
## Drift in segments
Drift can be segment-specific.
**The pattern.** Aggregate metrics look stable; segment-specific metrics show drift.
**Worked example.** Aggregate NPS is stable. Enterprise NPS is dropping; small-team NPS is improving. The aggregate hides the segment-specific drift.
**The investigation.** Segment-level views surface patterns the aggregate hides. Enterprise drift may indicate a specific issue with enterprise features or experience that aggregate metrics miss.
The discipline. Drift detection should include segment views, not just aggregate views.
---
## Drift in cross-channel patterns
Sometimes drift appears across channels even when individual channels look stable.
**The pattern.** Each channel shows mild changes; the cross-channel aggregate shows a stronger pattern.
**Worked example.** Support tickets in onboarding category up 15%. NPS comments mentioning onboarding up 10%. In-app feedback in onboarding up 20%. No single channel signals an emergency; the cross-channel aggregate suggests a real issue.
**The investigation.** Cross-channel drift detection requires unified views or manual cross-channel review.
---
## False-positive drift
Not every change is real drift.
**Common false positives.**
- Seasonal patterns: support volume drops over holidays; NPS dips during certain campaigns.
- One-off events: a viral social mention spikes social signal but does not represent persistent change.
- Product launches: short-term volume spikes around new features, then normalize.
- Channel changes: a new feedback channel launches; volume in that channel grows from zero, not because the underlying issue grew.
**The investigation discipline.** Before declaring drift, validate that the change is persistent and not explained by known factors.
---
## Drift acknowledgment in synthesis
Drift signals get surfaced in monthly and quarterly synthesis.
**The pattern.** Synthesis documents include a drift section: what is changing, what may explain it, what action (if any) is recommended.
**The honest framing.** Some drift gets acknowledged but not actioned (low-priority categories, edge cases). Some drift drives investigation. Some drift drives roadmap decisions. The synthesis names the disposition for each drift signal.
---
## Common drift detection failures
**No detection.** Aggregate volume is the only metric tracked; trends invisible.
**Aggregate only.** Segment-specific drift hidden by aggregate stability.
**Single-channel only.** Cross-channel patterns missed.
**Late detection.** Drift caught after it has compounded for months.
**False positives treated as real drift.** Seasonal patterns or one-off events trigger investigation that wastes time.
**Real drift treated as false positive.** The team dismisses signals as noise; underlying issues compound.
**Investigation without follow-through.** Drift detected; team investigates; finds cause; does not act. The detection was performative.
---
## Methodology-level choices that stay in the public skill
The drift patterns (increasing/decreasing volume, new/disappearing patterns, sentiment shifts). The drift detection cadence. Tooling for drift detection. Investigation discipline. Drift as early signal. Drift in segments. Drift in cross-channel patterns. False-positive drift. Drift acknowledgment in synthesis. Common failures.
## Implementation choices that stay internal
Specific dashboards for drift detection. Specific threshold settings for alerts. Specific seasonality models. Specific segment-view configurations. The team's own conventions for drift acknowledgment in synthesis. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |