When a Team Member Keeps Missing Deadlines
Before you manage someone for missing dates, check whether they ever agreed to the date or just heard it announced.
The situation
It's the third time this quarter. The work arrives two days late, the quality is fine, and the explanation is reasonable — something came up, a dependency slipped, the scope grew. Each individual instance is defensible. The pattern is not, and the pattern is starting to cost other people, who have begun building private buffers around this person's commitments.
You've mentioned it twice, lightly, in a way that let both of you avoid an uncomfortable moment. Nothing changed, which is what usually happens when a manager raises something lightly enough to be deniable.
Why it happens
Five causes, and only one of them is about the person's work ethic. First, the date was assigned rather than agreed — nobody who wasn't consulted feels bound. Second, hidden load: they're absorbing interrupt work, support rotations, or other people's requests that never appear on your list. Third, estimation, which is a learnable skill that almost nobody is taught. Fourth, a blocked dependency they don't feel senior enough to escalate. Fifth, and least common, a genuine standards problem — they don't believe the date is real, usually because past dates weren't.
That last one deserves attention, because it's often caused by the manager. If you have ever set an artificial deadline, moved a date without explanation, or accepted late work with no conversation, you have taught the team that dates are aspirational. People behave rationally inside the system they're actually in.
Notice also that in four of those five causes, the fix is structural. Managing the person harder makes the structural version worse, because now they're hiding the slip as well as causing it.
The protocol
- 01Gather three specific instances with dates before you talk. A pattern conversation without examples turns into a debate about whether the pattern exists.
- 02Name the pattern once, plainly, and then ask. 'Three times this quarter. I want to understand what's actually happening.' Then be genuinely open to the answer being about your system.
- 03Separate can't from didn't. Ask them to walk you through how they estimated the last one and where it went. If the estimate was wrong, that's a coaching problem. If the estimate was right and something intervened, that's a load or dependency problem.
- 04Change one structural thing that came out of the conversation — take something off their list, fix the dependency, or change how dates get set.
- 05Rebuild the commitment properly: they propose the date, not you. Ask 'what date can you commit to that you won't need to move?' and then hold them to a date they chose.
- 06Install a mid-point check on every future commitment. Half the elapsed time, not half the work: 'On the 10th, tell me either it's on track or it isn't.' Early warning is the actual deliverable.
- 07If the pattern continues after the structure is fixed, escalate the clarity, not the volume: state the standard, the consequence, and the review date in writing, once.
What to say
Naming the pattern
"I want to talk about dates. The audit was two days late, the vendor doc was a week, and the Q3 summary landed Monday instead of Thursday. Any one of those is nothing; three is a pattern and it's making other people build slack around your work. I don't think you're being careless, so tell me what's actually going on."
Rebuilding the commitment
"I don't want to give you a date. Look at what's actually on your plate and tell me the date you can commit to without needing to move it — later is fine, I'd rather have a real one. Whatever you say, I'll plan around it, and I'll expect a heads-up the moment it's at risk."
When it continues after the fix
"We changed the load and set the date yourself, and it moved again. So I need to be direct: hitting committed dates is part of the job, not a bonus. From here, every commitment gets a mid-point check, and I need to see three consecutive commitments met. Let's talk again on the 15th about how that's going."
What not to do
- —Don't hint. Two light mentions followed by a serious conversation feels like an ambush to the person on the receiving end.
- —Don't add padding to their deadlines secretly. It solves your scheduling problem and destroys the meaning of every date you give them.
- —Don't discuss it in front of the team. Public accountability for an individual is humiliation with a business justification attached.
- —Don't accept 'something came up' as a final answer three times. The third time, the something is the pattern.
- —Don't punish the early warning. If someone tells you on day five that day fifteen is at risk and you react badly, you've just bought yourself silence on every future project.
Signals you got it right
You hear about a slip at the midpoint instead of on the due date. This is the change that matters most, and it is entirely a product of how you reacted the last time someone warned you early.
Their proposed dates start moving later and then holding. A person estimating honestly will quote longer than a person trying to please you, and honest long beats optimistic short every time.
Other people stop building private buffers around this person's work. That buffer is invisible on any dashboard and it is the true cost you were paying.
The one thing that changes everything
Make the early warning the thing you praise. Most teams are optimised to reward looking on track, which means the manager finds out about the slip on the due date, when it's too late to do anything. Say it explicitly and then behave accordingly: 'Telling me late is the failure. Telling me early is the job.' Teams that believe that hit more dates, not because people work faster, but because you get two weeks to react instead of two hours.
Facing this right now?
Describe your situation and get a diagnosis, one principle, a named protocol, and the exact words to say.
Describe your situation and get a diagnosis →