Beta testing programme plan with testers and feedback loop
Plans a closed beta for a new product or feature: who to invite, how many, how long, what testers are asked to do each week, how feedback is collected and triaged, and the exit criteria for a full launch. Use it before releasing something risky to all users.
The output this prompt produced, unedited.
The prompt
What to give
Product or feature in beta: [e.g. a new invoicing module in an accounting app]
What we need to learn: [e.g. does it handle GST invoices correctly, is setup under 10 minutes]
Who the real users will be: [segment, size, devices]
Length of beta available: [e.g. three weeks]
Ways we can reach testers: [e.g. email list, in-app banner, community group]
Team time for support during the beta: [e.g. one PM and one engineer, two hours a day]
Plan checklist
Tester profile that matches real users, with two or three screening questions.
Number of testers with the reason: enough to see repeated problems, small enough to reply to every report.
A welcome message that sets expectations: it may break, how to report, what testers get.
Weekly tasks: one main job to try each week, tied to what we need to learn.
Feedback channels: an in-app report button, a short weekly survey of up to five questions, two or three follow-up calls.
Triage: every report tagged as bug, usability, missing feature or question, with a severity.
Exit criteria: numbers that must be met before launch, such as no open critical bugs and a task success rate.
Close: thank-you note, what testers keep, and what changed because of them.
Output format
Tester profile and screener questions.
| Week | Testers do | We measure | We send |
Triage table: | Severity | Example | Response time | Who fixes |
Exit criteria as a checklist with a target for each.
Welcome message under 150 words with [placeholders].
Guardrails
Do not promise launch dates or rewards that are not in the inputs.
Testers must know their data may be reset at the end; say so in the welcome message.
Never ask testers for passwords or payment details in feedback forms.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.