PM roundtable: How do you prioritize experiments?

Product managers from Statsig and Amplitude discuss how they prioritize experimentation, beginning with a naming test that temporarily freed the term “Journeys” for a journey-orchestration product before that initiative was deprioritized. They argue that most meaningful feature changes should be tested or placed behind feature gates, particularly when revenue, user behavior, or operational safety could be affected, while acknowledging that time, engineering capacity, and limited B2B traffic can constrain statistically significant A/B tests. Feature gates can still support safer releases, regression detection, observability, and directional learning even when experiments are underpowered. The group recommends prioritizing tests based on expected customer and business impact, implementation effort, measurable outcomes, available traffic, and the urgency of the information needed, including qualitative feedback for customer-specific features. They also contend that AI is reducing the cost of building variants and accelerating development, making experimentation culture increasingly important for keeping rapid product changes reversible, measurable, and low risk.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.