Product Feedback System

FEEDBACK COLLECTION

SE Feedback Submission Template

SE PRODUCT FEEDBACK FORM

FEEDBACK TYPE:
☐ Feature request
☐ Enhancement request
☐ Bug/issue
☐ Competitive gap
☐ Integration need
☐ UX improvement

FEEDBACK DETAILS:
Title: _______________
Description: _______________
Use case: _______________
Customer impact: _______________

CUSTOMER CONTEXT:
Customer name: _______________
Deal value: _______________
Deal stage: _______________
Lost/at-risk without: ☐ Yes ☐ No

FREQUENCY:
☐ First time heard
☐ 2-5 customers
☐ 6-10 customers
☐ 10+ customers

COMPETITIVE CONTEXT:
Competitor with feature: _______________
Competitive impact: ☐ High ☐ Medium ☐ Low

PRIORITY RECOMMENDATION:
☐ Critical (deal blocker)
☐ High (significant impact)
☐ Medium (nice to have)
☐ Low (minor improvement)

Feedback Categories

Category	Definition	Escalation Path
Deal blocker	Must have to close	PM + Director
Competitive gap	Losing deals	PM weekly
Enhancement	Improves existing	PM monthly
Nice to have	Low urgency	Backlog

---

FEEDBACK AGGREGATION

Feedback Analysis Process

FEEDBACK AGGREGATION PROCESS

WEEKLY AGGREGATION:
☐ Collect all submissions
☐ Categorize by type
☐ Group similar requests
☐ Count frequency
☐ Calculate deal impact

MONTHLY ANALYSIS:
☐ Top 10 requests by volume
☐ Top 10 by revenue impact
☐ Competitive gap analysis
☐ Trend identification
☐ Regional variations

QUARTERLY REPORT:
☐ Executive summary
☐ Prioritized recommendations
☐ Revenue opportunity analysis
☐ Win/loss correlation
☐ Product team response

FEEDBACK METRICS:
Total submissions: _____
Unique requests: _____
Deal value impacted: $_____
Requests addressed: _____

Prioritization Matrix

Request	Frequency	Revenue	Competitive	Score

---

PRODUCT COMMUNICATION

SE-Product Interface

SE-PRODUCT COMMUNICATION CADENCE

WEEKLY:
☐ Feedback submission deadline: Friday
☐ PM acknowledgment: Monday
☐ Urgent escalation: Real-time

BI-WEEKLY:
☐ SE-Product sync meeting
☐ Attendees: SE lead + PM
☐ Agenda: Top requests, status updates
☐ Duration: 30 minutes

MONTHLY:
☐ Feedback review meeting
☐ Full SE team + Product
☐ Roadmap visibility
☐ Prioritization discussion

QUARTERLY:
☐ Roadmap planning input
☐ SE leadership + Product leadership
☐ Strategic alignment
☐ Resource allocation

Communication Standards

Communication	Owner	Audience	Timing
Submission ack	PM	SE	48 hrs
Status update	PM	SE team	Weekly
Decision	PM	Submitter	30 days
Release note	PM	All SEs	Pre-launch

---

CLOSED LOOP PROCESS

Feedback Resolution Workflow

CLOSED LOOP PROCESS

SUBMISSION → ACKNOWLEDGMENT:
☐ Auto-ack on submission
☐ PM review within 48 hours
☐ Category assignment
☐ Initial response to SE

EVALUATION:
☐ Product team review
☐ Technical feasibility
☐ Business impact analysis
☐ Roadmap consideration

DECISION COMMUNICATION:
☐ Accepted → Roadmap slot
☐ Declined → Rationale provided
☐ Deferred → Timeline given
☐ Needs research → Follow-up date

FEATURE RELEASE:
☐ SE early access
☐ Training/enablement
☐ Customer communication guide
☐ Win-back opportunity identification

SE FOLLOW-UP:
☐ Notify requesting customers
☐ Update opportunity status
☐ Document wins
☐ Share success stories

---

Quick Reference: Which Resource for Which Challenge

Challenge	Recommended Resources
"Building SE team"	#353, #362
"Demos not closing deals"	#354, #360
"POCs extending cycles"	#355
"RFP response overwhelm"	#357, #361
"Technical objections"	#358
"SE-AE friction"	#359
"Product not hearing us"	#366

---

Every resource built to the Human Standard. Every resource designed to make technical selling your advantage.