Owning a fix for a team or process problem you saw in your organization

In a product manager interview, you are asked to describe a time when something going on in your organization bothered you: a process, a recurring decision pattern, a team dynamic or a way of working that you thought was wrong. Explain the situation and what you did about it. ```hint Show action, not just dissatisfaction Choose a case where you went beyond complaining: you found out why the problem existed, proposed a change, and got others to act, even if the problem sat outside your direct ownership. ``` ### Clarifying Questions - Should the issue be one within my own team, or is a cross-team or company-level problem in scope? - Does it need to be fully resolved, or is a story where I only partly improved things acceptable? - Is a people issue such as attrition or morale appropriate, or would you prefer a process or product-quality issue? ### What a Strong Answer Covers - A problem with a clear cost to customers, delivery or the team, described with evidence rather than frustration - A root-cause diagnosis: why the problem existed and who owned it - Ownership beyond the job description: how the candidate acted, influenced people without formal authority, and handled resistance - A measurable result and an honest account of what did not change - A lesson about raising and fixing problems that the candidate still applies ### Follow-up Questions - Who disagreed with your proposed change, and how did you bring them along? - If leadership had refused to act, what would you have done next? - How did you make sure the fix lasted after you moved on to other work?