What’s a Beta?

Marty Cagan argues that the word "beta" has become so ambiguous that its meaning depends on what a team is trying to accomplish. He describes four distinct uses: a QA phase handled with real users, a gentle deployment that migrates users gradually from an old system, a low-cost way to test whether a new product idea has demand, and a label for abandoned software that nobody wants to own. The first three are legitimate when actively managed with user analytics and feedback. The fourth, he says, harms users' willingness to engage with any beta, so teams should be honest and label such products as sustaining-only.

01Key takeaways

• Define what your team means by beta before launching, since the term is used for several different purposes.
• Use a beta as a QA phase only after the release has reached reasonable quality, since some bugs appear only at real-world scale.
• Use a gentle deployment beta to migrate users gradually from an old system to a new one before retiring the old.
• Treat a beta for a new idea as a validation tool only when cheaper ways of gathering feedback won't answer the question.
• Actively manage every beta with analytics and user feedback so the product improves as quickly as possible.
• Don't leave abandoned products labeled as beta; be transparent, such as with a sustaining-only label, to protect trust in real betas.

02Key sections

Beta as a QA phase

Teams sometimes release to customers to find bugs that only appear at scale or across many run-time environments. This is acceptable once the release reaches a reasonable quality level.

Beta as gentle deployment

A new release is launched as beta while the old one stays live, and users are gradually moved over until the old system can be phased out.

Beta as a feedback test for new ideas

For genuinely new products without a proven market, building and launching a beta may be the only reliable way to learn whether people want the idea.

Beta as an abandonment label

Some products carry the beta tag because no team stands behind them, which Cagan finds unhelpful because it erodes trust in legitimate betas.

Being honest with users

When a product is effectively abandoned, teams should say so openly, for example by labeling it sustaining-only, and keep using user feedback.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.