Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Pushes Back on Deadlines
Transcript
- Lucas: Luna, I want to talk about a manager who came to me last week. She runs a small product team at a marketing analytics firm, and she has this one developer — brilliant guy, fantastic code, but every single deadline he pushes back. Two-day task? He says he needs four. Sprint commitment? He asks for a buffer. She's starting to feel like she's negotiating a used car every time she assigns something. Luna: Oh, I know this person. I've managed that guy. It's exhausting because on paper, he's right — he always delivers good work. But the constant pushback wears you down. Lucas: Exactly. And here's the tricky part. If you just clamp down and say 'No, this is the deadline,' you risk losing a good employee or creating resentment. But if you always give in, you're essentially letting him set the team's pace. Luna: So what's the root cause? Is he just trying to protect his time, or is there something else? Lucas: That's the first question any manager has to answer. In my experience, pushback on deadlines usually falls into one of three buckets. First: fear of failure — the employee wants a buffer so they never miss. Second: overcommitment — they're on too many things and they're trying to protect their sanity. Third: and this one's subtle — they genuinely believe your deadline is wrong. Luna: And each of those needs a different response. You can't treat a fear of failure person the same as someone who's overloaded. Lucas: Right. With the fear of failure type, the answer is to build trust through smaller commitments. Instead of a two-week sprint, start with two-day tasks. Show them that they can hit a tight deadline without breaking. With the overcommitted person, you need to help them reprioritize — maybe they need to drop something else. Luna: What about the third bucket? The employee who thinks the deadline is unrealistic. Lucas: That's the most interesting one, because often the employee has a point. But here's the trap: if they always push back, you stop listening. You start assuming they're being difficult, even when they're right. The manager I talked to realized that her developer had flagged a genuine dependency issue three sprints in a row, and she wasn't hearing it. Luna: So the real skill is distinguishing between chronic pushback and legitimate concern. How do you do that in practice? Lucas: You need a structured conversation. I recommend a one-on-one where you say something like: 'I've noticed that every task I give you, you ask for more time. I want to understand what's driving that. Is it the scope? Is it competing priorities? Or is it that you don't feel comfortable committing to something you're not sure you can deliver?' Luna: That's direct but not confrontational. I like that. Lucas: And then you need to listen. But you also need to set a boundary. Because if the employee says 'I just need more time' every single time, that's not a sustainable pattern. One technique that works well is to ask them to propose an alternative. Not just 'I need three days,' but 'I can deliver the core functionality in two days, and the polish will take another day — here's the trade-off.' Luna: So you're shifting from a yes/no negotiation to a partnership about scope and quality. That feels much more productive. Lucas: Exactly. And here's a concrete example. I had a team once where a data engineer would always push back on quarterly milestones. Everything was 'I can't commit to that.' We switched to weekly milestones — every Friday he had to show something working. Within a month, the pushback disappeared. Because a week is too short to be scared of, and he could always adjust the scope for the next week. Luna: Interesting. So you shrunk the time horizon to reduce his anxiety. That's a great technique for the fear of failure bucket. Lucas: Right. And for the overcommitment bucket, I've found that managers often don't have a good handle on their employee's total workload. This developer might be on three projects, but the manager only sees one. So a simple fix is to ask them to list everything they're working on, and then help them decide what to deprioritize. Luna: One thing I've seen work is giving the employee ownership of the deadline. Instead of saying 'I need this by Friday,' say 'This needs to be done by Friday. How do you propose we make that work? What help do you need?' Lucas: That's powerful because it reframes the conversation. Now the employee is on the hook for the solution, not just the problem. And if they push back, you can say 'Okay, but if Friday is impossible, what's your plan B? Should we reduce scope? Should we get someone else to help?' Luna: Let me push back on you a little. What if the employee's pushback is actually a sign of a bigger issue? Like they don't trust management's priorities? Lucas: That's a real possibility. And if that's the case, no amount of deadline negotiation will fix it. The employee might be signaling that they think the project is a waste of time. That's harder to address because it's not about the deadline — it's about the mission. Luna: How do you handle that as a manager? You can't just say 'trust me.' Lucas: No, you can't. You have to be willing to explain the why. Show them the business context — why this deadline matters. If there's a client demo, or a regulatory requirement, or a revenue milestone, share that. Sometimes employees push back because they don't see the bigger picture. Luna: And if the employee still disagrees? If they genuinely think the priority is wrong? Lucas: Then you have to make a judgment call. Is this a one-time disagreement, or is this a pattern of not aligning with the team's direction? If it's a pattern, it might be a cultural fit issue. But more often than not, giving the employee context turns a pushback into a buy-in. Luna: I want to bring up one more scenario. What about the employee who pushes back on deadlines but then delivers early? That's a different kind of challenge. Lucas: That's the classic 'lowballer.' They overestimate everything so they always look good. The problem is, it creates a false safety margin across the whole team. If everyone does it, your planning becomes meaningless. Luna: So how do you call that out without punishing their good performance? Lucas: You use data. Track their actual completion times compared to their estimates. In a one-on-one, you can say 'You estimated this task at five days, but you finished it in three. That's a 40 percent buffer. I appreciate that you always deliver, but this gap makes it hard for me to plan. Can we work on tightening your estimates?' Luna: That's fair. You're not criticizing their work — you're asking for better planning. Lucas: And you can incentivize accuracy. Some teams use a 'confidence interval' approach — the employee gives a range: 'I'm 90 percent confident I can do this in three to five days.' Over time, you calibrate together. Luna: All right, let's talk about the manager's own role in this. I've seen managers who create pushback because they're disorganized. They give unclear deadlines, or they change them last minute, and then they wonder why the employee resists. Lucas: That's a huge one. If your deadlines are arbitrary or constantly shifting, you're training your employees to push back. They learn that your deadline isn't real. So the first step for any manager dealing with deadline pushback is to look in the mirror. Are you giving clear, consistent, realistic deadlines? Luna: And are you actually listening when they flag a problem? Because if you ignore their concerns three times, they'll stop raising them — or they'll push back harder. Lucas: Exactly. So the takeaway for a first-time manager is this: don't take deadline pushback personally. It's not defiance — it's data. It's telling you something about the employee's workload, their confidence, or the clarity of your assignment. Your job is to diagnose the root cause and then choose the right intervention. Luna: I think that's a good note to end on. But before we wrap, Lucas, I want to mention something. If this episode gave you a new tool or a different way to think about managing a deadline-pushback employee, honestly, that's worth the price of a coffee. If it was helpful, you can support the show at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. It helps us keep the podcast ad-free and focused on practical advice. Lucas: Yeah, and we really appreciate it. Every bit of support goes right back into making these episodes better for you. So, thank you if you choose to do that. Luna: Alright, let's bring it back. Lucas, you mentioned the manager with the developer. Did she try the weekly milestone approach? Lucas: She did. And the first week, the developer still pushed back on the Friday deadline. But she held firm — 'Let's just try it for one sprint.' By the third week, he was hitting the Friday deadlines consistently. He even said it felt less stressful because he wasn't carrying a two-week burden in his head. Luna: That's a great outcome. So sometimes the solution is structural, not personal. Lucas: Right. And that's the key insight for managers: if you have a pattern of pushback, don't just blame the employee. Look at your system. Look at your communication. And if you can build trust through small wins, you might find that the pushback melts away on its own. Luna: Good advice. Thanks, Lucas.