Behavioral: Responding When Colleagues Reject an Idea You Proposed

In a product manager interview at Google, you are asked a behavioral question: describe a time when you proposed an idea and it was not agreed to. Explain what the idea was and why you proposed it, who disagreed and why, how you responded, how things turned out, and what you took away from the experience. ```hint Show the disagreement had substance Choose a story where the other side had real reasons. Interviewers listen for how you worked out those reasons before deciding whether to push further, change the idea or let it go. ``` ### Clarifying Questions - Does the idea need to be a product idea, or can it be a change to a process, a plan or how the team worked? - Does the story need to end with the idea adopted, or is one where it was rejected for good, or where the objection proved right, acceptable? - Does it matter who disagreed: a manager or executive, peer product managers, or the engineering or design team? ### What a Strong Answer Covers - A concrete idea, the problem it addressed and the evidence behind it. - A fair account of who disagreed and their actual reasons. - What you did in response and why you chose that path over the alternatives. - The outcome, its effect on the working relationships, and a specific lesson you applied later. ### Follow-up Questions - Looking back, who was right, and how do you know? - How did you decide whether to keep pushing, escalate or drop the idea? - How did you work with the people who opposed it afterward?