Can you challenge authority constructively and commit once a decision is made?
At Google, my manager wanted to launch a new AI feature broadly to beat a competitor's announcement. I believed our model's accuracy wasn't high enough, risking user trust. I didn't just say 'no'; I prepared a brief analysis showing projected churn if error rates exceeded 5%, contrasting with the competitor's known issues. I requested a 30-minute meeting to present this 'Disagree and Commit' style. I proposed a middle ground: a limited beta to gather accuracy data before a full launch. My manager initially pushed back on the timeline but appreciated the data-driven risk assessment. We agreed on a 1% rollout with strict monitoring. The beta revealed significant hallucination issues in edge cases, validating my concern. We paused the broad launch, fixed the model, and launched three months later with high confidence. This preserved our reputation for quality. It taught me that disagreement is healthy when backed by data and focused on the customer outcome, not ego.
Explicitly mention 'Have Backbone; Disagree and Commit'.
Focus on the data used to persuade and the collaborative resolution.
📚 Recommended Resource
The 0-1 PM Interview Playbook (2026 Edition)
Master every round of the PM interview with frameworks, sample answers, and company-specific strategies used by candidates who landed offers at FAANG+.
Get it on Amazon →