[Behavioral] Tell me about a time a project started slipping and what you did.

Example Answer

Fictional example for structure only. Replace the circumstances and results with truthful evidence from your own experience; do not present this illustration as your work history.

In a fictional customer-portal project, our six-week plan assumed the identity integration would be ready at the end of week two. The dependency owner later confirmed week four. The plan still showed the original launch because the downstream testing dates had not moved, so I treated the apparent green status as unsupported.

I checked the dependency and remaining work with the engineering and testing leads. They confirmed that a contract stub could support some development, but could not replace live integration or access-control tests. I separated work that could proceed from work that genuinely had to wait, recorded the changed forecast and presented two options: move the full launch, or keep a narrower internal demonstration without presenting it as a production-ready release.

The sponsor chose the internal demonstration at week six and a revised production decision at week eight. I updated the baseline transparently, kept the original target visible in the decision record, and assigned an owner and review date to each remaining dependency. We delivered the agreed demonstration, and the integration test results were available for the later decision.

The observed result was an explicit, achievable revised commitment and usable decision evidence. I would not describe that as delivering the original scope on time or as proof that the release was ready. The lesson was to replace unsupported schedule confidence with verified dependencies and an accountable tradeoff.

Common Poor Answer to Avoid

"I watched the timeline more closely and kept everyone motivated until we caught up."

Why it's weak

• It does not identify the cause, change the plan or explain which commitment was actually met.

Why this works

• The fictional example distinguishes a demonstration from production readiness and preserves the original-versus-revised schedule comparison.