Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Overpromises and Underdelivers
Transcript
- Lucas: So you have a team member who says yes to everything. They volunteer for the hardest projects, they promise the moon, they tell you they'll have it done by Friday. And then Friday comes, and they've delivered maybe sixty percent of it, and the quality is shaky. Luna: Classic overpromise and underdeliver. It's one of the most frustrating patterns for a manager because you want to reward their enthusiasm, but you also need reliable outcomes. Lucas: Exactly. And it's especially common with early-career high-potentials. They desperately want to prove themselves, so they take on more than they can realistically handle. But the pattern can also show up in seasoned employees who are people-pleasers or who fear saying no. Luna: Where do you start if you're a manager stuck in that cycle? Lucas: First, you have to understand the root cause. Is it a skill gap in estimation? Is it anxiety about disappointing stakeholders? Or is it a cultural thing — maybe the team rewards optimism over accuracy? I've seen teams where the person who says 'I can do it in two days' gets the nod, even when everyone knows it's a four-day job. Luna: Right, so the manager might be inadvertently reinforcing the behavior. Lucas: Exactly. So step one is to diagnose. Have a one-on-one where you look at three recent examples where they overpromised. Not to scold them, but to say, 'Help me understand what happened here.' Often they'll say things like, 'I underestimated the dependencies,' or 'I thought I could work faster.' That tells you whether it's an estimation problem or a saying-no problem. Luna: And if it's estimation, there's a really practical tool I've used. You ask them to give you three numbers: the optimistic case, the realistic case, and the pessimistic case. It forces them to think about risk. Lucas: That's the confidence interval approach. I call it the 'best case, likely case, worst case' question. And here's the key — you don't let them commit to the optimistic number. You ask, 'If everything goes wrong, how long would it take?' Then you work backward from there. It trains them to include buffer. Luna: But what about the people-pleaser type? The one who knows it's a four-day job but says two days because they're afraid of disappointing you? Lucas: That's a trust issue. You need to explicitly tell them, 'I would rather have an honest estimate that you can deliver on than a heroic estimate that falls short. A reliable date is more valuable than an aggressive one.' And you have to mean it. If they give you a realistic estimate and you push back, you've just trained them to overpromise again. Luna: So you're basically creating psychological safety around saying no. Lucas: Exactly. And you can reinforce it by celebrating accurate estimates. When someone says, 'This will take five days,' and they deliver in five days, you make a point of saying, 'That was a solid estimate. I appreciate that.' That shifts the incentive from speed to reliability. Luna: Let me throw out a real case. A marketing manager I worked with — let's call her Priya — was notorious for overpromising. She'd commit to a campaign launch in three weeks when the team knew it needed five. She'd work nights and weekends, burn out, and still miss the date. Her manager tried everything — deadlines, check-ins, even a performance improvement plan. Nothing worked. Lucas: So what finally turned it around? Luna: Her manager sat her down and said, 'I want you to think of your reputation. Right now, people don't trust your commitments. That's a bigger problem than any single missed deadline. If you consistently overpromise, you lose credibility. And credibility is hard to rebuild.' For Priya, that hit home. She started using the three-number method and became much more conservative. Lucas: I love that. It frames it as a reputational issue, which matters to someone who cares about what others think. And it's true — the person who always delivers a day early on a realistic estimate is more trusted than the person who promises a miracle and misses. Luna: So let's say you've had the conversation. The employee is willing to change. What's the next step? Lucas: You build a feedback loop. After every major commitment, you debrief. Did we hit the date? Was the estimate accurate? What did we learn? The goal is to turn estimation into a skill they practice, not a personality trait they're stuck with. Luna: And if they aren't willing to change? If the pattern persists even after coaching? Lucas: Then you have to escalate the consequences. Not punitively, but structurally. You say, 'I want to give you these projects, but I need a reliable timeline. If you can't provide one, I'll have to assign the work to someone else or build in a mandatory buffer that I control.' That shifts the accountability back to them. Most people will adjust rather than lose the interesting work. Luna: Right. And one more thing — sometimes the manager is part of the problem. If you're the kind of leader who rewards the first person to raise their hand, you're encouraging overpromising. You have to reward the person who says, 'I can take this, but I'll need four days, not two.' Lucas: That's a great point. Leadership sets the norms. If you consistently choose speed over accuracy, you'll get overpromisers. If you choose accuracy over speed, you'll get reliable performers. Luna: And that's really what this episode is about — moving from a culture of heroic effort to a culture of dependable execution. Lucas: Speaking of dependable execution — we're able to keep Manager Mondays ad-free because of listeners who support the show. If you've ever used one of these frameworks in a real conversation, or if this podcast has helped you think through a career decision, consider buying us a coffee. It's buy me a coffee dot com slash fexingo. All lowercase. And it genuinely helps us keep doing these episodes without corporate sponsors. Luna: Yeah, we don't do ads, and we don't want to. Listener support is what makes that possible. So if you're in a position to chip in, we appreciate it. Lucas: Alright, back to the topic. One thing I want to add about the coaching process: it's important to separate the person from the behavior. You're not saying, 'You're an overpromiser.' You're saying, 'The pattern of overpromising is hurting your credibility, and I want to help you break it.' That distinction matters. Luna: It keeps the conversation collaborative instead of confrontational. Lucas: Exactly. And one final tactic I've seen work well is to have the employee keep a 'commitment log' for two weeks. Every time they promise something, they write down what they promised, the deadline, and the actual outcome. At the end of two weeks, they look at the data. Usually, they're shocked at the gap between their intentions and reality. Luna: Self-awareness is half the battle. Once they see the pattern in black and white, they're often motivated to change without you having to push. Lucas: Right. And that's the ultimate goal — to make them their own coach. Because if they can learn to estimate accurately, they become more valuable to the team, and they build a reputation that opens doors for them down the line. Luna: So to wrap up: diagnose the root cause, create psychological safety for honest estimates, build a feedback loop, and model the behavior you want to see. Lucas: And remember, the most respected people on any team aren't the ones who promise the most. They're the ones who deliver what they promise, every time. That's the standard to aim for.