Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Says Yes to Everything
Transcript
- Lucas: So you've got a team member who says yes to everything. Every new request, every cross-functional ask, every extra assignment — they nod, they smile, they say 'sounds great.' And then three weeks later, the deadlines start slipping, the quality dips, and you realise they're in way over their head. Luna: That is such a specific, frustrating pattern. And it's different from someone who just overestimates their capacity — this feels more like they're afraid to say no. Lucas: Exactly. And the tricky part is, on the surface, it looks like enthusiasm. You want to reward that energy. But if you don't address it, you end up with a burned-out employee and a team that can't rely on commitments. I've seen this play out in a product team at a mid-size SaaS company — a junior designer named Priya. Luna: What was her manager doing wrong, or what was the dynamic? Lucas: Good question. Her manager, let's call him Dan, initially thought Priya was just a rockstar — she'd take on UX tasks, content requests, even some front-end tweaks. But after about two months, he noticed she was missing internal deadlines and her design reviews were full of basic errors. He sat her down and said, 'Are you stretched too thin?' And she said — you guessed it — 'No, I'm fine.' Luna: Classic. The 'I'm fine' trap. So what did Dan actually do? Lucas: He tried a different approach. Instead of asking about her workload, he asked her to walk him through her week — hour by hour — on a whiteboard. They did what I call a 'yes audit.' They listed every project she'd agreed to, ranked them by priority, and then looked at the actual time each one needed. Priya realised she'd taken on six things that week that realistically required four full-time people. Luna: Wow. So the visual really hit home. Did she admit she had a problem? Lucas: She did. She said she was worried if she pushed back, people would think she wasn't a team player. That's the core fear — especially for junior folks or anyone early in their career. So Dan introduced a simple rule: before saying yes to any new request, Priya had to take 24 hours to review her existing commitments and then respond. He called it the '24-hour pause rule.' Luna: I love that. It buys time to actually think, and it gives the manager a chance to coach on prioritisation. Did they have a script for saying no gracefully? Lucas: They did. Dan helped Priya craft three go-to responses. One: 'I'd love to help, but I want to make sure I can give this the attention it deserves — let me check my priorities and get back to you by tomorrow.' Two: 'Right now my focus is on X and Y — can we revisit this next sprint?' And three, the hardest one: 'I'm not the best person for this — here's who I'd recommend.' Luna: That third one is crucial — it redirects rather than just shuts down the request. It shows leadership. Lucas: Right. And here's the thing: Dan also had to change his own behaviour. He realised he was part of the problem — he'd been dumping last-minute requests on Priya because she was so responsive. So he started sending her a weekly capacity overview: every Monday, she'd share a list of her top three priorities and how many hours she had free. That way, when a new ask came in, she could immediately see if she had room. Luna: That's a great systematic fix. But what about the manager who doesn't have that kind of structure? Say you're a new manager in a startup where everything is urgent. Lucas: Then you need the 'capacity conversation.' It's a regular one-on-one where you explicitly talk about the employee's total workload — not just their tasks, but their emotional bandwidth. I'd frame it like: 'I notice you're saying yes to a lot of things. I want to make sure you're not burning out. Let's look at what's on your plate and see what we can defer, delegate, or kill.' Luna: And that's different from a typical status update because it's about permission to offload. Lucas: Exactly. You're giving them explicit permission to say no — because many chronic yes-people never feel like they have that permission. They think their job is to absorb everything. Your job as a manager is to redefine their job as delivering on a focused set of outcomes. Luna: Speaking of redefining outcomes — if we've helped you think through a management challenge like this, or given you a framework you've actually used in a one-on-one, we'd love to hear about it. And honestly, the reason we can keep doing these deep dives without any ads or sponsors is because of listeners who chip in a couple of dollars a month at buy me a coffee dot com slash fexingo. It genuinely keeps the show going. Lucas: Yeah, it's a small thing that makes a big difference for us. And we don't interrupt the show with ads, so that's the trade-off. Anyway — back to the yes-person. Luna: Right. So you've done the audit, you've set the pause rule, you've had the capacity conversation. What happens if they still keep saying yes? Lucas: Then you need to look at the root cause more deeply. Sometimes it's a confidence issue — they feel they have to prove themselves constantly. Other times it's a lack of strategic thinking — they don't know how to triage priorities. And occasionally, it's a values mismatch: the company culture rewards 'always on' behaviour. Luna: How do you diagnose which one it is? Lucas: Ask them a simple question in a one-on-one: 'If you could only do three things this quarter, what would they be?' If they can't answer, that's a strategic thinking gap. If they can answer but still take on everything, that's likely a confidence or fear issue. And if they say 'everything is a priority,' that usually reflects a culture problem. Luna: And if it's culture, the manager has to shield the employee from some of that noise, right? Like, you have to be the buffer. Lucas: Exactly. As a manager, you're the umbrella. If the organisation is chaotic, you absorb some of that rain. You can say to your employee: 'Look, I know the CEO keeps asking for last-minute reports. I'm going to filter those through me first. If I think it's genuinely urgent, I'll pass it to you. Otherwise, I'll handle it or push back.' Luna: That builds so much trust. The employee stops feeling like they have to defend themselves constantly. Lucas: It does. And within a few weeks, Priya started feeling more in control. She still said yes to things, but she'd add a qualifier: 'I can do this, but it will push X deliverable to next week — is that okay?' That's a mature way to commit. She went from being a yes-machine to being a reliable partner. Luna: I want to talk about one more nuance: what if the yes-person is actually a high-performer who can deliver on most of what they take on? Isn't that just a great employee? Lucas: It is, until it isn't. Even high-performers have a ceiling. I've seen star employees burn out because they kept saying yes for years and then suddenly crashed. The key is to catch it early — when they're at 80 percent capacity, not 120 percent. Have the capacity conversation before the crisis, not after. Luna: So the framework works for both the struggling employee and the star. It's about sustainable performance. Lucas: Exactly. And the biggest takeaway for any manager listening: don't assume that 'yes' means 'yes, and I can handle this.' Sometimes it means 'yes, because I'm afraid to say no.' Your job is to create a safe space for them to tell you the truth. Luna: Alright, so to recap: do the yes audit, introduce the 24-hour pause rule, have regular capacity conversations, and act as a buffer if the culture is chaotic. That's a solid action plan. Lucas: That's it. And if you try any of these, let us know how it goes. We love hearing real stories from the trenches. Luna: Definitely. And a reminder — if you want to support the show, you can do that at buy me a coffee dot com slash fexingo. Every bit helps, and we're grateful for the community. Lucas: On that note, we'll see you next time. Keep leading well.