Discuss a Missed Deadline After a Dependency Changed

A missed deadline still needs a conversation when another team changed a dependency. The manager can acknowledge the changed condition while examining what the employee knew, when they knew it, and how they raised the risk. That approach improves future coordination without treating a dependency as a complete explanation.

Bring a simple timeline to the discussion: original due date, dependency date, update received, and communication sent. Ask the employee where the plan stopped matching reality. The answer may point to a decision that needed escalation, an unclear owner, or a request that should have been renegotiated earlier.

Manager Nina said, “The client summary was due Friday. The data file arrived Thursday afternoon with new fields, and we delivered Monday. Walk me through the point when you saw Friday was no longer realistic.” Omar said, “I knew on Thursday, but I thought I could finish over the weekend.” Nina replied, “I understand why you tried. Next time, tell me as soon as the estimate changes so we can choose between a reduced scope, help from another person, or a revised date. What message could you have sent Thursday?” Omar said, “I could have said the file change added review time and asked whether the client needed every section by Friday.”

The manager should take responsibility for decisions that belong above the employee, such as approving scope or speaking to the client. The employee owns timely visibility and the agreed work plan. Write those ownership points down before the next project starts.

In the next project check, ask the employee to identify dependencies before committing to a date. Review one early warning they send, including the options they proposed. This practice makes escalation a normal part of delivery instead of a sign that someone has failed.