How would you communicate a feature delay to stakeholders?
Model answer
Model answerDelays need to be communicated early, with context, and with a plan. The worst thing is to say nothing until the deadline passes. I'd communicate: what changed, why it changed, what the new timeline is, and what we're doing to prevent it from slipping again. I'd avoid being defensive — delays happen, and the team's credibility comes from honesty and recovery, not from never being late.
Framework · Communication Framework
- EEarly
Communicate as soon as you know — never wait until the deadline - CContext
Explain why, not just what — stakeholders can handle truth, not ambiguity - PPlan
Always pair bad news with a recovery plan and revised timeline - DDownstream impact
Check what the delay affects and address it proactively before being asked
Related questions
- What is product-market fit and how would you know if you have it?
- You have 3 features requested by customers and only 1 sprint. How do you decide?
- How do you handle a situation where engineering says a feature is impossible?
- How do you say no to a stakeholder's feature request?
- How would you explain your product roadmap to an engineer who thinks all roadmaps are a waste of time?