Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage Someone Who Frequently Misses Deadlines
Transcript
- Lucas: You know that feeling when you send a calendar invite for a check-in and your stomach drops because you already know what the update is going to be? Luna: Oh, I know exactly that feeling. 'Hey, how's that deliverable coming?' and you're already bracing for 'it's not done yet.' Lucas: Right. And if it happens once, you chalk it up to a bad week. Twice, you start watching more closely. Three times — that's a pattern. And as a manager, your job is to intervene before it becomes the team's identity. Luna: So let's talk about the employee who chronically misses deadlines. What's the first move? Do you go straight to a performance improvement plan? Lucas: No, absolutely not. The first move is diagnosis. There are at least three distinct reasons someone misses deadlines, and you treat each one differently. The most common is overcommitment — they say yes to everything because they want to be helpful or because they're afraid to say no. Luna: I've been that person. You end up with six things due Friday and you've only got bandwidth for three. Lucas: Exactly. The second reason is poor estimation — they genuinely believe a task will take two hours when it actually takes six. And the third is a skills gap — they don't actually know how to do the work, so they avoid it until the last minute, then panic. Luna: Oof. That third one is tough because the employee might be embarrassed to admit they're struggling. Lucas: Right. So your first conversation shouldn't be about the missed deadline. It should be about the work itself. Let me give you a concrete case. I once coached a marketing manager who had a coordinator — let's call her Priya — who missed three campaign delivery dates in a row. Each time the excuse was different: the designer was late, the copy needed more revisions, the stakeholder changed the brief. Luna: Classic 'reasons, not results' pattern. So what did you advise the manager to do? Lucas: I advised him to sit down with Priya and do a time audit. Not a 'gotcha' audit — a collaborative one. For one week, Priya tracked every hour she spent on each task. And what came out was that she was spending about 60 percent of her time on low-value admin and only 20 percent on the actual campaign work. Luna: So the real problem wasn't that she was bad at her job — it was that she was buried in busywork. Lucas: Exactly. And once the manager saw that, he could help her reprioritize. He shifted some of the admin to a junior intern and gave Priya permission to say no to non-essential requests. Within two weeks, her deadline hit rate went from about 30 percent to 80 percent. Luna: That's a great outcome. But what if the time audit shows the person just has bad estimating skills? Like they think a blog post takes two hours but it actually takes five. Lucas: Then you coach them on the 'promise versus estimate' distinction. I learned this from a software engineering manager I interviewed a few years back. He said there are two numbers: how long you think something will take — the estimate — and how long you commit to — the promise. And a good professional builds buffer into the promise. Luna: So you teach them to add, say, 50 percent to their estimate before they commit? Lucas: At least. For the first few cycles, you might even ask them to give you a deadline that's double their estimate. Then as their accuracy improves, you tighten it. The key is to separate the judgment of their estimation from the judgment of their performance. Luna: That feels generous but also accountable. I like that. What about the skills gap scenario? Where the person is avoiding the work because they don't know how to do it? Lucas: That one requires a different conversation. You have to ask directly: 'Walk me through how you plan to approach this task.' If they can't describe a coherent plan, you've found the gap. Then you offer training, pair them with a senior team member, or break the task into smaller chunks they can handle. Luna: But some managers might worry that stepping in to help signals that missing deadlines is okay — that you'll just rescue them. Lucas: And that is a real tension. You don't want to create learned helplessness. So you pair the support with a clear expectation: 'I'm going to help you through this one, but by next quarter I expect you to be able to handle this independently.' Then set a 30-day checkpoint to evaluate progress. Luna: And if after 30 days nothing changes? Lucas: Then you escalate to a formal performance conversation. But honestly, in my experience, most people want to meet deadlines. They're not lazy — they're overwhelmed, miscalibrated, or under-skilled. As a manager, your job is to figure out which one it is and give them the right tool. Luna: I think one thing that's easy to forget too is that sometimes the deadline itself is the problem. Not the employee. Lucas: Say more. Luna: Well, I had a boss once who set all deadlines for Friday at 5 PM. Every single project. It didn't matter if it was a two-day task or a two-week task. Naturally, everything piled up on Fridays, and people started missing deadlines because they were just overwhelmed by the artificial crunch. Lucas: That's such a good point. The deadline itself might be arbitrary. So when you're diagnosing the pattern, also ask yourself: is this deadline real? Does it reflect an actual business need, or is it just a 'nice to have by Friday'? Luna: Right. And if it's the latter, you might want to adjust the deadline rather than coach the person. Lucas: Exactly. One more thing I want to mention: the framing of the conversation matters enormously. If you open with 'You missed another deadline,' the employee goes into defense mode. But if you open with 'I noticed the last few projects have been tight on timing — let's figure out what's going on,' you get collaboration. Luna: And before we wrap up, I want to ask: what about the manager who is also a people-pleaser? They're afraid to have the deadline conversation because they don't want to damage the relationship. Lucas: That's a real challenge, and I think it's one of the most common traps for first-time managers. You want to be liked, but being liked isn't the same as being respected. Avoiding the conversation actually damages the relationship more in the long run because the employee never gets a chance to improve. Luna: And the rest of the team starts to resent the missed deadlines too. So by having the conversation, you're actually protecting the whole team. Lucas: Exactly. And look — speaking of protecting the team and the quality of the show — we keep Manager Mondays completely ad-free. No sponsors, no ads, no interruptions. That's a choice we've made from day one because we want this to be a resource you can trust, not a vehicle for selling something. If that matters to you and you'd like to support the work, you can find us at buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to keep it independent. Luna: Yeah, I love that we do that. It means we can say exactly what we think without worrying about pleasing an advertiser. Lucas: Alright — back to the deadline conversation. The last thing I'll say is this: the goal isn't to never miss a deadline. The goal is to build a system where misses are the exception, not the norm, and where both you and your employee learn something from each one. Luna: And if you do that, the trust actually deepens, because the employee sees you as someone who helps them succeed, not someone who just tracks their failures. Lucas: Exactly. So next time you're staring at that calendar invite with the knot in your stomach, take a breath. Ask yourself: is this overcommitment, poor estimation, or a skills gap? Then have the right conversation. Luna: And maybe check if the deadline itself is even reasonable. Lucas: Always. Thanks, Luna. Luna: Thanks, Lucas.