Leading a Product Team Through an Abrupt Change in Priorities

While your team is in the middle of executing its plan, its priorities change suddenly and significantly. As the product manager, explain how you would handle the shift: how you would respond at first, what you would do with the work already in progress, and how you would bring your team and stakeholders along. If you have faced this before, you may ground the answer in that experience. ```hint Understand before you react Before re-planning anything, find out what triggered the change and how long it is expected to last; both shape how much in-flight work you stop and how you explain the change to the team. ``` ### Clarifying Questions - What triggers the shift in this scenario: a leadership decision, a competitor or market event, a major customer request, a regulatory change, or a production or security incident? - Is the new priority expected to be temporary, such as a few weeks of urgent work, or a lasting change of direction? - Does the shift affect only my team, or several teams that depend on one another's commitments? ### What a Strong Answer Covers - Understanding the reason, urgency and expected duration of the change before acting, and questioning it constructively when it is unclear. - Explicit re-planning of in-flight work: what stops, what finishes, what is paused in a state that can be resumed, and which new commitments replace the old ones. - Communication with the team, dependent teams and every stakeholder whose dates move. - Care for the team's morale and focus, and avoiding repeated thrash. - A concrete example or a clear sequence of steps, and a review afterwards. ### Follow-up Questions - This is the third major shift this quarter and the team is visibly frustrated. What do you do differently? - You believe the new priority is a mistake. How do you push back, and what do you do if leadership decides to proceed anyway? - A customer was promised a feature that has now been deprioritized. How do you handle that conversation?