Describing a Product Strategy You Defined, From Diagnosis to Results

Walk me through a time when you were the one who defined the strategy for a product. How did you arrive at it, and what happened? ```hint Show the choice, not the roadmap Pick an example where you decided what the product would and would not pursue, rather than one where you carried out a plan someone else set. ``` ### Clarifying Questions - Does a strategy for one area of a product, such as a new customer segment or a single feature line, count, or should it cover the whole product? - Should the example be one whose results are already known, or is a strategy that is still playing out acceptable? - Is the interviewer more interested in how the strategy was formed or in how it was rolled out across teams? ### What a Strong Answer Covers - The situation that called for a strategy: what was unclear, contested or not working, and why it mattered at that moment. - The evidence gathered, the real alternatives considered, and the explicit choices made, including what the product stopped doing or said no to. - How the strategy became goals, a sequenced roadmap and alignment with engineering, design, go-to-market and leadership. - Measurable results, and how the strategy was adjusted when new evidence arrived. - A clear line between the candidate's own decisions and those of the team or leadership. ### Follow-up Questions - Who disagreed with the strategy, and how did you resolve it? - What signal would have made you change direction, and did you ever act on one? - Looking back, what would you do differently if you set this strategy again?