Recovering from Falling Behind

How to tell a story about a project that slipped: spotting the drift early, raising it with options, and choosing a recovery that protects what matters most.

Overview

Most projects fall behind at some point. When an interviewer asks about one, they are not checking whether you have ever been late. They want to see three things: that you noticed the slip early and from evidence, that you told the right people quickly and brought options, and that you chose a recovery on purpose instead of just working longer hours.

A weak answer is 'I worked nights and caught up.' It suggests the plan was never checked, the risk was hidden, and the fix will not last. A strong answer says how you saw the gap, who you told and when, which options you offered, what you gave up, and what you changed so it happens less next time.

Detection — 'By week two we had closed 4 of the 7 tasks we planned.' — 'We realized near the end.'
Raising it — Told the manager and partners the same week, with options — Waited, hoping to catch up
Recovery — Cut or deferred scope, removed blockers, re-sequenced work — Longer hours only
Ownership — 'I should have checked sooner.' — Blames changing requirements
Lesson — A concrete process change — 'I'll plan better'

Every story and sample line on this page is fiction, written as an example.

What you will be able to do

Describe how you spotted a slip early, with the evidence you used.
Raise a delay with a clear cause, options and a recommendation.
Choose among recovery levers and say what each one costs.
End with a process change that makes the next slip smaller.

Interview questions

Tell me about a time your project fell behind schedule.
How do you detect schedule drift early?
How do you tell stakeholders you are going to miss a date?
What recovery options do you consider, and what does each cost?
What would you change so it does not happen again?

Recovering from Falling Behind

Overview

What you will be able to do

Interview questions

More Behavioral topics