en un clic
beta-program
Closed beta program playbook covering recruitment, success criteria, communication cadence, and beta-to-GA exit gates.
Menu
Closed beta program playbook covering recruitment, success criteria, communication cadence, and beta-to-GA exit gates.
Basé sur la classification professionnelle SOC
Expert agile coaching: framework selection, maturity assessment, retrospective facilitation, transformation roadmaps. Use when selecting an agile framework, coaching teams, facilitating retrospectives, or designing a transformation.
Administer the Atlassian suite (Jira/Confluence): user provisioning, groups, SSO/SAML, permissions, security policies, marketplace apps, backups, and org-wide governance. Use for admin config, access management, and system optimization.
Structured PM 1:1 templates by partner type — manager, engineering-manager partner, designer, IC reports, cross-functional — grounded in Radical Candor, the GROW coaching model, and the Manager Tools 1:1 framework.
PM career ladder rubrics from APM through VP/CPO across product sense, execution, leadership, strategy, and communication. Includes gap analysis, growth planning, and promotion packet templates.
Structured PM interview preparation across product sense, execution, strategy, behavioral, and technical rounds, using CIRCLES, AARM, STAR, and the estimation framework. Calibrated to APM, PM, Senior PM, and Group PM rubrics.
30-60-90 day plan for a new PM joining a company or team, grounded in Michael Watkins' First 90 Days framework and the STARS situational diagnosis. Includes week-by-week plan, stakeholder map, 1:1 question bank, and first-PRD template.
| name | beta-program |
| description | Closed beta program playbook covering recruitment, success criteria, communication cadence, and beta-to-GA exit gates. |
| license | MIT + Commons Clause |
| metadata | {"version":"1.0.1","author":"borghei","category":"project-management","domain":"pm-execution","updated":"2026-06-15T00:00:00.000Z","tech-stack":"beta-program, kano-model, cohort-design, beta-to-ga-gates"} |
A structured playbook for running a closed beta that produces clear learning, retained design partners, and an unambiguous decision on whether to proceed to general availability. Most betas fail not because the product is wrong, but because the program is run informally: recruitment is opportunistic, success criteria are implicit, communication is sporadic, and exit gates are never defined. This skill replaces all of that with concrete templates and decision rules.
A good closed beta runs 4-8 weeks, recruits 10-30 participants from three concentric cohorts ("friends, family, fanatics"), publishes a weekly cadence the team commits to, and exits on pre-agreed criteria rather than the calendar. The outputs are a beta program plan, a recruitment script, a weekly cadence template, and an exit memo that either greenlights GA, extends the beta, or kills the feature.
launch-playbook/ and a progressive rollout instead).create-prd/).assets/beta-program-plan.md and get PM + Eng + sponsor sign-off before recruiting.assets/recruitment-script.md (over-recruit 2x), then stand up the comms channel and publish the cadence on day 1.assets/weekly-cadence-template.md); review the exit memo (assets/exit-memo.md) at week N for a Greenlight / Extend / Pivot / Kill decision.See references/beta-framework.md for the full framework tables, step-by-step workflow, troubleshooting, and success criteria.
references/beta-framework.md -- Full framework (cohort, Kano, success gates, cadence, exit gates), the 8-step workflow, troubleshooting matrix, and success criteria. Read this when building the plan, setting gates, running the cadence, or diagnosing problems.references/beta-program-guide.md -- Practical reference guide: why betas fail, cohort sequencing, Kano deep dive, exit-gate worked examples, common failure modes. Read this for narrative depth and worked examples.references/red-flags.md -- Bad-vs-good examples for the beta plan, recruitment script, cadence, and exit memo. Read this to review beta artifacts before opening recruitment.assets/beta-program-plan.md -- Beta program plan template with gates, cohort sizing, timeline.assets/recruitment-script.md -- Email/DM templates for the three cohorts plus screening questions.assets/weekly-cadence-template.md -- Monday digest, Tuesday office hours, Wednesday review, Friday snapshot templates.assets/exit-memo.md -- Exit-gate decision memo template (Greenlight / Extend / Pivot / Kill).In Scope:
launch-playbook/Out of Scope:
launch-playbook/)discovery/brainstorm-experiments/)launch-playbook/)Important Caveats:
delivery-manager/).| Integration | Direction | What Flows |
|---|---|---|
create-prd/ | Receives from | PRD defines the hypothesis and headline outcome that beta gates measure |
discovery/identify-assumptions/ | Receives from | Riskiest assumptions become the beta's primary learning goals |
discovery/brainstorm-experiments/ | Complementary | Beta is one experiment type; brainstorm-experiments covers smaller/faster alternatives |
daci-framework/ | Uses | DACI driver owns the exit-gate decision |
launch-playbook/ | Feeds into | Greenlit beta hands testimonials, case studies, and known issues to launch |
release-notes/ | Feeds into | Beta release notes preview the GA changelog |
summarize-meeting/ | Complementary | Office hours and 1:1 notes become structured weekly summaries |
senior-pm/ | Reports to | Exec sponsor receives the exit memo and signs the GA decision |