Skip to main content

SkyMirror User Feedback & Product Development Framework

Executive Summary​

This framework establishes SkyMirror's approach to collecting, analyzing, and acting on user feedback to drive product development. It covers the complete feedback loop from collection to implementation across all SkyMirror products: CheckMet (AI attendance), Traquiva (AI learning platform), Software Solutions, and SkyMirror Academy.


Part 1: Feedback Collection System​

1.1 Feedback Channels​

ChannelTypeFrequencyOwnerUse Case
In-App FeedbackQuantitative + QualitativeContinuousProductFeature feedback, bugs
NPS SurveysQuantitativeQuarterlyCSOverall satisfaction
Customer InterviewsQualitativeMonthlyProductDeep insights
Support TicketsQualitativeContinuousSupportIssues, requests
QBRsQualitativeQuarterlyCSStrategic feedback
User AnalyticsQuantitativeContinuousProductBehavior patterns
Sales FeedbackQualitativeWeeklySalesProspect objections
Churn InterviewsQualitativePer eventCSWhy customers leave

1.2 In-App Feedback System​

Feedback Widget Triggers​

TriggerWhenQuestion
Feature First UseAfter first use of new feature"How useful was this feature?" (1-5)
Task CompletionAfter completing key workflow"How easy was this?" (1-5)
Session EndAfter 10+ min session"Any feedback for us?" (open text)
Error OccurrenceAfter error message"Did this resolve your issue?" (Y/N)
Monthly Check-inMonthly for active users"How likely to recommend?" (0-10)

Feedback Widget Design​

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ How was your experience today? β”‚
β”‚ β”‚
β”‚ 😞 😐 πŸ™‚ 😊 😍 β”‚
β”‚ 1 2 3 4 5 β”‚
β”‚ β”‚
β”‚ [Optional: Tell us more...] β”‚
β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚
β”‚ β”‚ β”‚ β”‚
β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚
β”‚ β”‚
β”‚ [Submit] [Not now] β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

1.3 NPS Survey Framework​

Survey Design​

Question 1 (Required):

On a scale of 0-10, how likely are you to recommend CheckMet to a colleague?

Question 2 (Required):

What's the primary reason for your score?

Question 3 (Optional):

What could we do to improve your experience?

NPS Calculation​

NPS = % Promoters (9-10) - % Detractors (0-6)
ScoreCategoryFollow-up
9-10PromoterRequest referral, testimonial
7-8PassiveUnderstand barriers to promotion
0-6DetractorImmediate outreach, recovery plan

NPS Benchmarks​

ScoreInterpretationAction
70+World-classMaintain, leverage for growth
50-69ExcellentContinue improvements
30-49GoodIdentify improvement areas
0-29Needs workUrgent focus on experience
<0CriticalMajor intervention needed

1.4 Customer Interview Framework​

Interview Types​

TypePurposeFrequencyDurationParticipants
DiscoveryUnderstand problemsMonthly45 minProspects
UsabilityTest featuresPer release30 minActive users
SatisfactionGauge happinessQuarterly30 minAll customers
ChurnUnderstand leavingPer event20 minChurned users
Win/LossSales insightsPer deal30 minWon/lost prospects

Interview Script Template​

## Customer Interview Script

### Introduction (5 min)
- Thank you for your time
- Purpose of the interview
- Recording permission
- Confidentiality assurance

### Warm-up (5 min)
- Tell me about your role
- How long have you been using CheckMet?
- What were you using before?

### Core Questions (20-30 min)

**Problem Understanding:**
1. What challenges were you facing before CheckMet?
2. How were those challenges affecting your work?
3. What would happen if those problems weren't solved?

**Solution Feedback:**
4. How well does CheckMet solve those problems?
5. What do you like most about CheckMet?
6. What frustrates you most about CheckMet?
7. If you could change one thing, what would it be?

**Usage Patterns:**
8. How often do you use CheckMet?
9. Which features do you use most?
10. Are there features you don't use? Why?

**Value Assessment:**
11. How has CheckMet impacted your work?
12. Can you quantify any time or cost savings?
13. Would you recommend CheckMet? Why/why not?

### Wrap-up (5 min)
- Any other feedback?
- Can we follow up with additional questions?
- Thank you and next steps

Interview Notes Template​

## Interview Notes

**Date:** [Date]
**Customer:** [Company Name]
**Interviewee:** [Name, Title]
**Interviewer:** [Name]

### Key Quotes
> "[Direct quote 1]"
> "[Direct quote 2]"
> "[Direct quote 3]"

### Pain Points Mentioned
1. [Pain point 1]
2. [Pain point 2]
3. [Pain point 3]

### Feature Requests
1. [Request 1] - Priority: [H/M/L]
2. [Request 2] - Priority: [H/M/L]

### Positive Feedback
1. [Positive 1]
2. [Positive 2]

### Concerns/Complaints
1. [Concern 1]
2. [Concern 2]

### Insights
1. [Insight 1]
2. [Insight 2]

### Action Items
- [ ] [Action 1] - Owner: [Name]
- [ ] [Action 2] - Owner: [Name]

Part 2: Feedback Analysis​

2.1 Feedback Categorization​

Category Taxonomy​

CategorySubcategoryExamples
UsabilityNavigation"Can't find settings"
Workflow"Too many clicks"
Clarity"Confusing labels"
FeaturesNew Request"Need mobile app"
Enhancement"Add export to Excel"
Missing"No bulk upload"
PerformanceSpeed"Dashboard loads slowly"
Reliability"App crashes"
Accuracy"Recognition errors"
IntegrationHRIS"Need Workday integration"
Payroll"Sync with ADP"
SSO"Support Okta"
SupportResponse Time"Slow to respond"
Quality"Didn't solve issue"
Documentation"Docs outdated"

2.2 Feedback Scoring Matrix​

FactorWeightScoring Criteria
Frequency25%How often is this mentioned?
Impact25%How much does it affect users?
Revenue20%Does it affect revenue/churn?
Effort15%How hard to implement?
Strategic15%Does it align with strategy?

Scoring Scale​

ScoreFrequencyImpactRevenueEffortStrategic
550%+ usersCriticalMajor churn risk<1 weekCore to vision
425-50%HighModerate risk1-2 weeksSupports vision
310-25%MediumMinor risk2-4 weeksNeutral
25-10%LowNo risk1-2 monthsTangential
1<5%MinimalN/A3+ monthsMisaligned

2.3 Feedback Dashboard​

## Weekly Feedback Dashboard

### Volume Summary
| Source | This Week | Last Week | Trend |
|--------|-----------|-----------|-------|
| In-App | XX | XX | ↑/↓ |
| Support | XX | XX | ↑/↓ |
| Interviews | X | X | ↑/↓ |
| NPS Responses | XX | XX | ↑/↓ |

### Sentiment Analysis
| Category | Positive | Neutral | Negative |
|----------|----------|---------|----------|
| Usability | X% | X% | X% |
| Features | X% | X% | X% |
| Performance | X% | X% | X% |
| Support | X% | X% | X% |

### Top Themes This Week
1. [Theme 1] - X mentions - [Trend]
2. [Theme 2] - X mentions - [Trend]
3. [Theme 3] - X mentions - [Trend]

### NPS Trend
| Month | NPS | Promoters | Passives | Detractors |
|-------|-----|-----------|----------|------------|
| [M-2] | XX | X% | X% | X% |
| [M-1] | XX | X% | X% | X% |
| [M-0] | XX | X% | X% | X% |

### Critical Issues
1. [Issue 1] - X customers affected - [Status]
2. [Issue 2] - X customers affected - [Status]

### Action Items
- [ ] [Action 1] - Owner: [Name] - Due: [Date]
- [ ] [Action 2] - Owner: [Name] - Due: [Date]

Part 3: Feature Prioritization​

3.1 Prioritization Framework (RICE)​

FactorDefinitionScoring
ReachHow many users affected per quarterNumber of users
ImpactHow much it improves experience3=Massive, 2=High, 1=Medium, 0.5=Low, 0.25=Minimal
ConfidenceHow sure are we about estimates100%=High, 80%=Medium, 50%=Low
EffortPerson-weeks to completeNumber of person-weeks

RICE Score = (Reach Γ— Impact Γ— Confidence) / Effort

3.2 Feature Prioritization Template​

## Feature Prioritization - [Quarter]

### Scoring

| Feature | Reach | Impact | Confidence | Effort | RICE Score | Priority |
|---------|-------|--------|------------|--------|------------|----------|
| [Feature 1] | 1000 | 2 | 80% | 4 | 400 | P1 |
| [Feature 2] | 500 | 3 | 100% | 8 | 188 | P2 |
| [Feature 3] | 2000 | 1 | 50% | 2 | 500 | P1 |
| [Feature 4] | 100 | 2 | 80% | 1 | 160 | P2 |

### Priority Definitions

| Priority | Criteria | Timeline |
|----------|----------|----------|
| P0 | Critical bug, revenue impact | Immediate |
| P1 | High RICE, strategic | This quarter |
| P2 | Medium RICE | Next quarter |
| P3 | Low RICE | Backlog |

### Quarterly Roadmap

**This Quarter (P1):**
1. [Feature 1] - [Owner] - [Timeline]
2. [Feature 3] - [Owner] - [Timeline]

**Next Quarter (P2):**
1. [Feature 2] - [Owner] - [Timeline]
2. [Feature 4] - [Owner] - [Timeline]

**Backlog (P3):**
1. [Feature 5]
2. [Feature 6]

3.3 Product Roadmap Template​

## Product Roadmap - [Year]

### Vision
[One sentence product vision]

### Annual Themes
1. [Theme 1]: [Description]
2. [Theme 2]: [Description]
3. [Theme 3]: [Description]

---

### Q1: [Theme]

| Feature | Description | Status | Owner |
|---------|-------------|--------|-------|
| [Feature 1] | [Description] | 🟒 Shipped | [Name] |
| [Feature 2] | [Description] | 🟑 In Progress | [Name] |
| [Feature 3] | [Description] | βšͺ Planned | [Name] |

**Key Metrics:**
- [Metric 1]: [Target]
- [Metric 2]: [Target]

---

### Q2: [Theme]

| Feature | Description | Status | Owner |
|---------|-------------|--------|-------|
| [Feature 1] | [Description] | βšͺ Planned | [Name] |
| [Feature 2] | [Description] | βšͺ Planned | [Name] |

**Key Metrics:**
- [Metric 1]: [Target]
- [Metric 2]: [Target]

---

### Q3-Q4: [Theme]

| Feature | Description | Status | Owner |
|---------|-------------|--------|-------|
| [Feature 1] | [Description] | βšͺ Planned | [Name] |
| [Feature 2] | [Description] | βšͺ Planned | [Name] |

---

### Backlog (Future Consideration)
- [Feature 1]
- [Feature 2]
- [Feature 3]

Part 4: Feedback Loop Closure​

4.1 Closing the Loop with Customers​

Communication Templates​

Feature Shipped:

Subject: You asked, we delivered: [Feature Name]

Hi [Name],

Remember when you told us you wanted [feature description]?

We listened! [Feature Name] is now live in CheckMet.

Here's what's new:
- [Benefit 1]
- [Benefit 2]
- [Benefit 3]

Try it out: [Link]

Thanks for helping us make CheckMet better!

Best,
[Product Team]

Feature In Progress:

Subject: Update on your feedback

Hi [Name],

A few months ago, you shared feedback about [issue/request].

I wanted to let you know we're actively working on this. Here's the plan:
- [What we're building]
- [Expected timeline]
- [How it will help]

We'll let you know when it's ready to try.

Thanks for your patience and continued feedback!

Best,
[Product Team]

Feature Declined:

Subject: Following up on your suggestion

Hi [Name],

Thank you for suggesting [feature/change].

After careful consideration, we've decided not to pursue this right now because [reason]. However, we've noted it for future consideration as our product evolves.

In the meantime, here's an alternative approach that might help: [workaround].

We really appreciate you taking the time to share your ideas with us.

Best,
[Product Team]

4.2 Feedback Status Tracking​

StatusDefinitionCustomer Communication
NewJust receivedAcknowledge receipt
ReviewingUnder considerationNo communication yet
PlannedOn roadmapShare timeline
In ProgressBeing builtShare progress
ShippedReleasedAnnounce and thank
DeclinedWon't doExplain reasoning
DuplicateAlready trackedMerge with existing

Part 5: User Research Program​

5.1 Research Calendar​

MonthResearch TypeFocus AreaParticipants
JanDiscovery[Topic]8-10 prospects
FebUsability[Feature]6-8 users
MarNPS Deep DiveDetractors5-6 detractors
AprDiscovery[Topic]8-10 prospects
MayUsability[Feature]6-8 users
JunSatisfactionAll segments10-12 users
JulDiscovery[Topic]8-10 prospects
AugUsability[Feature]6-8 users
SepNPS Deep DivePassives5-6 passives
OctDiscovery[Topic]8-10 prospects
NovUsability[Feature]6-8 users
DecAnnual ReviewAll segments10-12 users

5.2 User Research Repository​

## Research Repository

### Research Index

| Date | Type | Topic | Key Findings | Link |
|------|------|-------|--------------|------|
| [Date] | Discovery | [Topic] | [Summary] | [Link] |
| [Date] | Usability | [Feature] | [Summary] | [Link] |

### Key Insights Database

| Insight | Source | Date | Confidence | Status |
|---------|--------|------|------------|--------|
| [Insight 1] | [Research] | [Date] | High/Med/Low | Validated/Testing |
| [Insight 2] | [Research] | [Date] | High/Med/Low | Validated/Testing |

### Persona Updates

| Persona | Last Updated | Key Changes |
|---------|--------------|-------------|
| HR Director | [Date] | [Changes] |
| Operations Manager | [Date] | [Changes] |

5.3 Usability Testing Protocol​

Test Setup​

Participants: 6-8 users per test Duration: 30-45 minutes per session Compensation: €50 gift card or account credit

Test Script Template​

## Usability Test Script

### Setup (5 min)
- Welcome and thank you
- Purpose explanation
- Think-aloud instructions
- Recording consent

### Warm-up (5 min)
- Current role and responsibilities
- Familiarity with CheckMet
- Typical usage patterns

### Tasks (20-30 min)

**Task 1: [Task Name]**
- Scenario: [Context]
- Goal: [What they need to accomplish]
- Success criteria: [How we measure success]

Observe:
- [ ] Completed successfully
- [ ] Time to complete: ___
- [ ] Errors made: ___
- [ ] Confusion points: ___

**Task 2: [Task Name]**
[Same structure]

**Task 3: [Task Name]**
[Same structure]

### Debrief (5 min)
- Overall impressions
- Most confusing part
- Most useful part
- Suggestions for improvement

### Wrap-up
- Thank you
- Next steps
- Compensation

Part 6: Metrics & Reporting​

6.1 Feedback Metrics​

MetricDefinitionTargetFrequency
NPSNet Promoter Score40+Quarterly
CSATCustomer Satisfaction4.5/5Per interaction
CESCustomer Effort Score<3Per task
Feedback VolumeTotal feedback itemsTrending upWeekly
Response Rate% of users giving feedback20%+Monthly
Time to CloseDays to address feedback<30 daysMonthly
Feature Adoption% using new features60%+Per release

6.2 Monthly Feedback Report Template​

## Monthly Feedback Report - [Month Year]

### Executive Summary
[3-4 sentences summarizing the month]

### Key Metrics

| Metric | This Month | Last Month | Target | Status |
|--------|------------|------------|--------|--------|
| NPS | XX | XX | 40+ | 🟒/🟑/πŸ”΄ |
| CSAT | X.X | X.X | 4.5 | 🟒/🟑/πŸ”΄ |
| Feedback Volume | XXX | XXX | ↑ | 🟒/🟑/πŸ”΄ |
| Time to Close | XX days | XX days | &lt;30 | 🟒/🟑/πŸ”΄ |

### Feedback Breakdown

| Category | Volume | Sentiment | Trend |
|----------|--------|-----------|-------|
| Usability | XX | X.X/5 | ↑/↓ |
| Features | XX | X.X/5 | ↑/↓ |
| Performance | XX | X.X/5 | ↑/↓ |
| Support | XX | X.X/5 | ↑/↓ |

### Top Requests

| Request | Mentions | Priority | Status |
|---------|----------|----------|--------|
| [Request 1] | XX | P1 | In Progress |
| [Request 2] | XX | P2 | Planned |
| [Request 3] | XX | P2 | Backlog |

### Customer Quotes

> "[Quote 1]" - [Customer, Title]

> "[Quote 2]" - [Customer, Title]

### Actions Taken

1. [Action 1] - [Outcome]
2. [Action 2] - [Outcome]

### Next Month Focus

1. [Focus 1]
2. [Focus 2]

Part 7: Tools & Systems​

PurposeToolCostPriority
In-App FeedbackHotjar / Pendo€50-200/moHigh
NPS SurveysDelighted / Wootric€50-100/moHigh
User AnalyticsMixpanel / AmplitudeFree-$100/moHigh
Interview SchedulingCalendlyFree-$15/moMedium
Research RepositoryNotion / DovetailFree-$50/moMedium
Session RecordingFullStory / Hotjar€100-300/moMedium

7.2 Integration Architecture​

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ In-App │────▢│ Feedback │────▢│ Product β”‚
β”‚ Feedback β”‚ β”‚ Database β”‚ β”‚ Backlog β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ NPS │────────────────────────▢│ Dashboard β”‚
β”‚ Surveys β”‚ β”‚ β”‚ & Reports β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Support β”‚β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Άβ”‚ Customer β”‚
β”‚ Tickets β”‚ β”‚ Profiles β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Part 8: Governance​

8.1 Roles & Responsibilities​

RoleResponsibilities
Product ManagerOwn feedback collection, analysis, prioritization
UX ResearcherConduct interviews, usability tests
Customer SuccessCollect feedback during QBRs, escalate issues
SupportTag and categorize tickets, escalate trends
EngineeringImplement features, provide effort estimates
LeadershipReview monthly reports, approve roadmap

8.2 Meeting Cadence​

MeetingFrequencyAttendeesPurpose
Feedback TriageWeeklyPM, UX, SupportReview new feedback
PrioritizationBi-weeklyPM, Eng, DesignPrioritize backlog
Roadmap ReviewMonthlyLeadership, PMReview roadmap progress
Research ReadoutMonthlyAll productShare research findings

Document Version: 1.0 Last Updated: December 2024 Owner: Product Manager Review Cycle: Quarterly