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?
What the interviewer wants to hear
- Gather objective evidence: milestones, burnup, earned value, defects, demos
- Talk privately to team members and stakeholders
- Look at critical path and dependencies, not just status colours
- Present findings honestly to the sponsor with options
- Build a recovery plan and new baseline
- Change the reporting culture so bad news is safe
Model answer
First I would look for objective evidence instead of status colours: milestone dates actually hit, burnup or earned value trends, open defects, test results and whether working increments have been demoed. I would check the critical path and key dependencies. In parallel, I would have private one-to-one conversations with team leads, testers and key users, because people often know the real situation but feel unsafe saying it. Once I had a clear picture, I would present it to the sponsor quickly and honestly, with facts, the likely impact and options such as reducing scope, adding capacity or moving the date. With agreement, I would create a recovery plan and new baseline through change control. Finally, I would change how status is reported, using clear criteria and evidence, and I would thank people publicly when they raise problems early, so green really means green.
Can you answer it under time pressure?
Take a timed hard round and get scored on every answer.
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?
- How do you give a reliable delivery forecast to executives when there is a lot of uncertainty?
- 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?