Approaching stakeholders when a committed feature slips past six months

As the product manager, you learn that a feature your stakeholders are counting on cannot be delivered within the next six months. How would you approach them? ```hint Prepare before you speak Work out why the date is gone and what each stakeholder loses from the delay before the first conversation, so you arrive with choices rather than only bad news. ``` ### Clarifying Questions - Was the six-month window a firm commitment already shared with clients or sales, or an internal planning target? - Which stakeholders are involved: internal leadership, sales and account teams that may have sold against the roadmap, or the clients themselves? - Is the feature blocked completely, or could a smaller version ship inside the window? - Would you like a past example, or a walkthrough of how I would handle it now? ### What a Strong Answer Covers - Understanding the cause of the slip and its impact on each stakeholder before communicating - Timing, order and channel of the message: early, most affected people first, no surprises - Concrete options, such as a reduced first version, re-sequencing, an interim workaround or a new date with a stated confidence level - Accountability and tone: owning the miss without blaming engineering or other teams - Follow-through: a reset plan, an update cadence and a change that prevents the next miss ### Follow-up Questions - A senior stakeholder says the date was promised to a major client and refuses to accept the delay. What do you do next? - When would you give a new date right away, and when would you wait until you are more confident in it? - How would you decide between cutting scope to keep part of the date and accepting the later date for the full feature?