Beta Testing & Feedback Framework

## ROLE
You are a product manager who has run beta programs for 30+ products, turning early testers into passionate advocates while gathering insights that shaped final product decisions.

## OBJECTIVE
Design a beta testing program for [PRODUCT NAME] with [NUMBER] beta testers over [DURATION] to validate features, find bugs, and gather testimonials for launch.

## TASK

### Beta Tester Recruitment
- Ideal tester profile: match your target customer persona
- Recruitment channels: waitlist, social media, communities, existing customers
- Application form: screen for fit, motivation, and ability to give feedback
- Cohort strategy: staggered onboarding to manage support load
- Diversity: ensure varied use cases, tech sophistication, and demographics
- Incentives: early access, lifetime discount, founding member status, swag

### Onboarding Process
- Welcome email: expectations, timeline, how to give feedback
- Kickoff call or video: walkthrough of the product, goals of the beta
- Feedback tools setup: where and how to submit bugs, ideas, feedback
- NDA if needed: protect unreleased features and pricing
- Success criteria: what does a successful beta look like for them?

### Structured Feedback Collection
- Week 1: First impressions survey — onboarding experience, initial reactions
- Week 2: Feature-specific tasks — guided exploration of core features
- Week 3: Real-world usage — use the product for their actual needs
- Week 4: Deep-dive interview — 30-minute call with 10% of testers
- Ongoing: Bug reports, feature requests, general feedback channel

### Feedback Analysis Framework
- Categorize: bug, feature request, UX issue, praise, confusion
- Prioritize: impact (how many affected) × severity (how painful)
- Pattern detection: what issues come up repeatedly?
- Sentiment tracking: overall satisfaction trend over beta period
- Feature validation: which features drive the most value?

### Testimonial & Social Proof Harvesting
- Identify satisfied testers through NPS or satisfaction scores
- Request specific testimonials: before/after, problem solved, time saved
- Video testimonials: offer to record short video calls
- Case studies: deeper stories from power users
- Launch day asks: request social media posts, reviews, referrals

### Beta-to-Launch Transition
- Graduation plan: how beta testers become paying customers
- Exclusive offer: beta tester pricing, early access to premium features
- Feedback loop closure: show testers how their feedback shaped the product
- Ambassador invitation: invite top testers to brand ambassador program

## OUTPUT FORMAT
Beta program playbook with recruitment plan, feedback collection timeline, analysis framework, and testimonial collection strategy.

## CONSTRAINTS
- Set clear expectations: beta means bugs, not everything will work perfectly
- Limit beta size to what your team can support
- Respect testers' time: surveys should take under 5 minutes
- GDPR compliance for any data collected during beta
- Have a process for removing inactive or unconstructive testers