Plan a beta or early-access program for a new feature
A beta plan covering who to invite, what to learn, how to collect feedback, and the criteria for general release.
The prompt
Plan a beta program for a new feature.
Feature: [DESCRIPTION AND CURRENT MATURITY]
What we need to learn: [e.g. does it solve the problem, does it scale, will people pay]
Ideal beta users: [SEGMENTS, USE CASES]
Candidate pool: [CUSTOMER LIST, WAITLIST, COMMUNITY]
Duration and capacity: [WEEKS, HOW MANY USERS WE CAN SUPPORT]
Known limitations: [WHAT IS NOT DONE YET]
Include:
1. Learning goals: 3-5 specific questions the beta must answer, each linked to a measure.
2. Participant selection: criteria, mix of segments, and red flags (e.g. users who will only report bugs, accounts that cannot tolerate instability). Suggested number of participants.
3. Invitation message and a short expectations note: what is unfinished, how to give feedback, support level, whether data carries over, and whether it will be paid later.
4. Feedback system: in-product prompt, survey at key moments, interview schedule, bug-report channel, usage events to watch.
5. Weekly cadence for reviewing feedback and deciding fixes.
6. Exit criteria for general availability: quality bar, adoption or satisfaction thresholds, open bugs allowed.
7. How to close the beta: thank-you, what happens to their access and data.
Keep the plan to a page. Have legal review any beta terms or data-use language.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- DESCRIPTION AND CURRENT MATURITY
- SEGMENTS, USE CASES
- CUSTOMER LIST, WAITLIST, COMMUNITY
- WEEKS, HOW MANY USERS WE CAN SUPPORT
- WHAT IS NOT DONE YET
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Audit a website or app for accessibility (WCAG)Checks against WCAG and gives prioritized, specific fixes.
- Respond to a secret leaked in a code repositoryWalks you through containing a leaked API key, password, or token: revoke, rotate, check for misuse, and clean up history.
- Plan a feature sunset and customer migrationA deprecation plan with usage analysis, timeline, migration path, and communications for every affected group.
- Implement a feature from a spec, with testsPlans and writes production-quality code for a feature, including tests and edge cases.