I fumbled this a bit because I jumped straight into 'here's what I'd do' mode instead of grounding it in a real example first.
Show that you diagnose root causes before reacting, then take a structured, data-informed approach to re-plan and communicate. Emphasize proactive stakeholder alignment and iterative delivery to regain momentum without burning out the team.
Pro tip: Frame slippage as a signal, not a failure: Google values PMs who surface risks early and propose trade-offs (scope, time, resources) rather than silently absorbing pressure.
Investigate why deadlines are slipping: unclear requirements, underestimation, dependencies, scope creep, or team capacity. Use data (burndown charts, velocity, dependency maps) to pinpoint the main drivers.
Reassess the roadmap with stakeholders, cut or defer low-impact work, and re-sequence based on value and risk. Set realistic milestones with buffer for unknowns.
Communicate the revised plan, trade-offs, and rationale clearly to all stakeholders. Secure agreement on what will be delivered and what won't, and set expectations for future updates.
Introduce short feedback loops (e.g., weekly demos, sprint reviews) to catch slippage early. Adjust scope or resources iteratively based on progress and new information.
Track leading indicators (e.g., cycle time, blocker count) and hold retrospectives to prevent recurrence. Share learnings to improve future planning.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.