How do you give a reliable delivery forecast to executives when there is a lot of uncertainty?

What the interviewer wants to hear

• Use ranges and confidence levels, not single dates
• Base forecasts on data: three-point estimates, velocity or throughput
• Use Monte Carlo or probabilistic forecasting
• Explain the main assumptions and risks driving the range
• Update the forecast regularly as uncertainty reduces
• Separate internal targets from external commitments

Model answer

I avoid giving a single date when uncertainty is high, because it sounds precise but is usually wrong. Instead I give a range with confidence levels, for example a 50% chance by June and 85% by July. I base that on data: three-point estimates for planned work, or historical throughput and velocity for agile teams, and I run a Monte Carlo simulation where possible. I explain the few assumptions and risks that drive the range, such as a vendor API or a regulatory approval, and what we are doing to reduce them. I also separate the team's internal target from an external commitment, which should sit at a higher confidence level. Then I update the forecast regularly, so executives see the range narrow as we learn. This builds trust because surprises become rare and every change has a reason.

More hard Project Manager questions

• You take over a project that is three months behind schedule and the team is demotivated. What do you do?
• Tell me how you would handle senior stakeholders with conflicting goals for the same project.
• How would you lead a project team spread across India, the UAE and Europe?
• Have you ever had to recommend stopping or changing a project? How would you approach it?
• A critical vendor has failed to deliver and your go-live is at risk. Walk me through your response.
• A client wants a fixed price and fixed date, but your team works in agile sprints and the requirements are still unclear. How would you set up and run this project?
• You join a program where every report is green, but you suspect it is in serious trouble. How do you find the truth and what do you do next?
• Your organisation is very traditional, with heavy governance and annual budgets, but leadership wants to become agile. How would you help a first project succeed?
• A regulator has set a deadline that cannot move, and your project is already behind. How do you make sure you comply on time?