A Project Is Slipping - Get It Back on Track (TPM)

What interviewers evaluate

• Do you diagnose the root cause before reacting?
• Do you reason through the classic levers (scope, resources, time, quality)?
• Do you protect the critical path and unblock, not just push harder?
• Do you manage stakeholders and set realistic expectations?
• Do you extract a lesson / prevention, not just firefight?

A framework to structure your answer

1. Diagnose - why is it behind? Underestimation, a blocker/dependency, scope creep, attrition, or unclear requirements? The cause dictates the fix.
2. Re-baseline - get an honest current status and a realistic estimate to done; stop trusting the old plan.
3. Pull the levers - scope (cut/defer non-essential work), resources (add help to the critical path - carefully), timeline (negotiate the date), or quality bar. Usually scope is the safest lever.
4. Unblock the critical path - remove the specific blocker; adding generic effort to non-critical work won't help.
5. Communicate early - tell stakeholders the real status and the recovery plan; don't hide a slip.
6. Prevent recurrence - capture the root cause so the next plan accounts for it.

Try structuring your own answer first, then reveal a strong worked example.

Common variants

• Your team consistently misses estimates. What do you change?
• A key engineer quits mid-project. How do you respond?
• Scope keeps growing. How do you control it?

Pitfalls to avoid

• Jumping to 'add more people' or 'work overtime' without diagnosing the cause.
• Trusting the old plan instead of re-baselining honestly.
• Pushing effort onto non-critical-path work that won't move the date.
• Hiding the slip from stakeholders until it's too late.
• Firefighting without capturing a lesson to prevent recurrence.

Likely follow-ups

• Leadership refuses to cut scope or move the date. Now what?
• How do you tell which lever to pull?
• How do you re-estimate credibly when the first estimate was wrong?