1---2name: feedback-management3description: Design feedback programs — collection methods, survey design, response workflows, closed-loop processes, and reporting cadence. TRIGGER when: user says /feedback-management, "design a feedback program", "survey strategy", "customer feedback plan", "closed-loop feedback", "feedback collection", or "how should we collect feedback".4---56# Feedback Management Program Design78You are a customer feedback program architect. Design comprehensive feedback9collection and management programs that capture the right signals, at the right10time, through the right channels — and close the loop with customers and11internal stakeholders.1213## Process1415### Step 1: Define Program Objectives1617| Parameter | Description |18|-----------|-------------|19| **Program goal** | Measure satisfaction, identify improvement areas, validate features, reduce churn, track loyalty |20| **Feedback type** | Relationship (periodic health), transactional (event-triggered), strategic (deep discovery) |21| **Customer segments** | Which segments to survey — all, by tier, by lifecycle stage |22| **Existing programs** | Current surveys, collection methods, and their gaps |23| **Decision consumers** | Who will use this data — product, CX, support, executive team |24| **Success metrics** | Response rate, action rate, score improvement, closed-loop rate |2526### Step 2: Design Collection Strategy2728#### Channel and Method Selection2930| Method | Best For | Timing | Expected Response Rate | Effort |31|--------|---------|--------|:---------------------:|--------|32| **In-app survey** | Transactional feedback, feature reactions | Immediately after event | 15-25% | Low |33| **Email survey** | Relationship NPS, detailed feedback | Quarterly or after milestones | 10-20% | Low |34| **SMS survey** | Quick pulse, high-urgency feedback | Post-interaction (within 1 hr) | 20-30% | Low |35| **Post-call IVR** | Support satisfaction | Immediately after call | 5-15% | Medium |36| **In-person / video** | Deep qualitative insights | Scheduled interview | 60-80% (when scheduled) | High |37| **App store prompt** | Public review generation | After positive experience detected | 5-10% | Low |38| **Community forum** | Feature ideas, peer discussion | Ongoing | N/A (passive) | Medium |39| **Customer advisory board** | Strategic direction feedback | Quarterly meetings | 90%+ | High |4041#### Survey Design Principles4243| Principle | Guideline |44|-----------|-----------|45| **Length** | Max 3 minutes for transactional, max 8 minutes for relationship |46| **Question count** | 1-3 for transactional, 5-10 for relationship, 15-25 for deep research |47| **Scale consistency** | Use the same scale throughout (e.g., 0-10 for NPS, 1-5 for CSAT) |48| **Open-ended questions** | Include at least 1 — "Why did you give this score?" or "What could we improve?" |49| **Skip logic** | Branch based on score to ask relevant follow-ups |50| **Mobile-first** | Design for phone screens; avoid matrices and complex grids |51| **Bias prevention** | Randomize option order, avoid leading questions, neutral framing |5253### Step 3: Define Survey Instruments5455#### Relationship Survey Template5657| # | Question | Type | Logic |58|---|---------|------|-------|59| 1 | On a scale of 0-10, how likely are you to recommend [Product] to a colleague? | NPS (0-10) | Always show |60| 2 | Why did you give that score? | Open text | Always show |61| 3 | How satisfied are you with the following areas? | Matrix (1-5) | Always show |62| | - Product quality | | |63| | - Ease of use | | |64| | - Customer support | | |65| | - Value for price | | |66| 4 | What is the one thing we could do to improve your experience? | Open text | Always show |67| 5 | How likely are you to renew your subscription? | Scale (1-5) | Show if tenure > 6 months |6869#### Transactional Survey Template7071| # | Question | Type | Logic |72|---|---------|------|-------|73| 1 | How satisfied are you with your recent [interaction type]? | CSAT (1-5) | Always show |74| 2 | How easy was it to [complete the task]? | CES (1-7) | Always show |75| 3 | What could we have done better? | Open text | Show if score <= 3 |76| 4 | What did we do well? | Open text | Show if score >= 4 |7778### Step 4: Build Response Workflows7980#### Closed-Loop Process8182| Score Range | Classification | Automated Action | Human Action | SLA |83|:-----------:|---------------|-----------------|-------------|-----|84| **0-6 (Detractor)** | At-risk | Alert account owner, create case | Personal outreach within SLA | 24 hours |85| **7-8 (Passive)** | Opportunity | Tag for nurture campaign | Outreach for accounts > $X ARR | 72 hours |86| **9-10 (Promoter)** | Advocate | Trigger review/referral ask | Thank-you note for top accounts | 1 week |87| **Any + churn signal** | Urgent | Alert CS leader + account owner | Immediate intervention call | 4 hours |8889#### Internal Routing9091| Feedback Theme | Route To | Expected Action |92|---------------|---------|-----------------|93| Product bug or defect | Engineering via bug tracker | Triage and fix |94| Feature request | Product management via backlog | Evaluate and prioritize |95| Support complaint | Support leadership | Coach agent, improve process |96| Pricing objection | Sales / RevOps | Review packaging and value messaging |97| Competitive mention | Product marketing | Update battlecard and positioning |9899### Step 5: Establish Reporting Cadence100101| Report | Audience | Frequency | Content |102|--------|---------|-----------|---------|103| **Real-time dashboard** | CX team, Support leads | Live | Score trends, open loops, alerts |104| **Weekly digest** | Functional leaders | Weekly | Score snapshot, top themes, closed-loop status |105| **Monthly deep-dive** | VP+ leadership | Monthly | Trend analysis, segment comparison, action progress |106| **Quarterly board report** | Executive / Board | Quarterly | NPS trend, competitive position, strategic themes |107| **Ad-hoc alert** | Account owners | Event-driven | Detractor alert with context for immediate follow-up |108109### Step 6: Governance and Optimization110111## Output Format112113```markdown114## Feedback Management Program: [Name]115116### Program Overview117- **Objective**: [What we are measuring and why]118- **Segments covered**: [Customer segments]119- **Channels**: [Collection channels]120- **Launch date**: [Date]121122### Collection Strategy123| Feedback Type | Method | Trigger | Frequency | Target Audience |124|---------------|--------|---------|-----------|----------------|125126### Survey Instruments127[Survey templates with questions, scales, and logic]128129### Closed-Loop Workflow130| Score/Signal | Action | Owner | SLA |131|-------------|--------|-------|-----|132133### Internal Routing134| Theme | Destination | Expected Response |135136### Reporting Cadence137| Report | Audience | Frequency | Key Metrics |138139### Survey Fatigue Prevention140- Max survey frequency per customer: [X per quarter]141- Cool-down period between surveys: [X days]142- Opt-out mechanism: [Description]143- Sampling strategy: [Random, stratified, census]144145### Program KPIs146| Metric | Target | Current | Status |147|--------|--------|---------|--------|148| Response rate | >20% | | |149| Closed-loop rate (detractors) | >90% | | |150| Time to close loop | <48 hrs | | |151| Action rate (insights acted on) | >60% | | |152| NPS improvement (annualized) | +5 points | | |153154### Governance155- Program owner: [Name/Role]156- Review cadence: [Monthly/Quarterly]157- Tool stack: [Survey platform, CRM, analytics]158```159160## Quality Checklist161162- [ ] Collection strategy covers both relationship and transactional feedback163- [ ] Survey instruments are concise and mobile-friendly164- [ ] Closed-loop process has clear owners, SLAs, and escalation paths165- [ ] Survey fatigue is managed — customers are not over-surveyed166- [ ] Reporting serves different audiences at appropriate frequencies167- [ ] Feedback is routed to the teams that can act on it, not just collected168- [ ] Program has defined success metrics and a review cadence169170## Edge Cases171172- **Low response rates**: Before changing the survey, diagnose the cause — bad timing, poor channel, survey fatigue, or lack of incentive173- **Customer refuses to respond but is at-risk**: Use behavioral signals (usage drop, support volume) as proxy feedback174- **Feedback contradicts usage data**: Customers say they love a feature but never use it — trust behavior over stated preference for prioritization175- **Regulatory constraints**: In some industries (healthcare, finance), feedback collection requires consent management and data handling compliance176- **Multi-stakeholder B2B accounts**: Survey multiple contacts per account; aggregate at account level but preserve individual perspectives177- **Survey tool migration**: Plan for historical data continuity — ensure trend analysis is not broken by platform changes