PM behavioral: reducing launch scope to hit a date and handling what was deferred

Describe a project where you chose to drop or postpone part of the planned scope so the team could ship sooner. What did you cut, how did you decide, and what was the result? ```hint Show the cost of the cut Pick a story where removing scope was a real choice with a downside you had to accept, not a feature nobody wanted. Be ready to explain how you told the essential pieces apart from the rest. ``` ### Clarifying Questions - Does it need to be a launch I owned as PM, or can it be one where I recommended the cut and someone else made the final call? - Is the interest in a fixed external date (a partner commitment, an event, a regulatory deadline) or in shipping early to learn from users sooner? - Should the result cover only the launch itself, or also what happened later to the work that was deferred? ### What a Strong Answer Covers - Why shipping sooner mattered in this case: a concrete cost of slipping, not a general wish to move fast. - How the cut was decided: the user outcome and metric used to separate essential from deferrable work, and the other options considered. - How the people who lost features were brought along, and how the decision was recorded and communicated. - The measured result, and what happened afterwards to the deferred work. - What the candidate learned and would do differently in planning. ### Follow-up Questions - The stakeholder whose feature you removed escalates to your manager. How do you respond? - What would you refuse to cut even if it meant missing the date, and why? - Did the deferred work ever ship? If not, what did that teach you?