Strategy question

Your team has implemented a change in the "Share" feature and released it for A/B testing. You realized that there is 20% of usage of the feature. Would you still decide to release it?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Judgment on shipping decisions under ambiguous experiment results, weighing usage level against the actual success criteria.

Clarify what success was originally defined as, since 20% usage alone is meaningless without a target or baseline.
Compare the 20% figure against the pre-test hypothesis or benchmark for a Share feature change.
Check the metric's effect on north star outcomes, like overall shares completed or downstream engagement, not just feature usage.
Look for guardrail regressions, such as increased friction, errors, or drop off in the sharing flow.
Decide based on whether the change is net positive versus the control, not on the usage number in isolation.

Refuses to answer yes or no without the missing context: what was the control's usage and what was the target.
Reasons that 20% usage could be strong if it lifted total shares by, say, 10%, or weak if it cannibalized an existing higher performing flow.
Recommends a clear next step, such as extending the test or checking segment level results, instead of a blind release.

Treating the 20% number as inherently good or bad without a baseline to compare it to.
Ignoring guardrail metrics like errors or retention that matter more than raw usage.

Chapters of the AI PM course that teach what this question tests.