Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Am Too Busy for That
Transcript
- Lucas: So you ask an employee to take on something new, and before you finish the sentence they say, 'I'm too busy for that.' Maybe they don't even say 'for that' — just 'I'm too busy.' Luna: That phrase has become almost a reflex in some teams. It can shut down a conversation before it starts. Lucas: Right. And as a manager, your first instinct might be to push back — 'everyone's busy, just fit it in.' But that rarely works and it damages trust. Today I want to look at why employees say 'I'm too busy' and what you can do about it that actually helps both of you. Luna: Give me a concrete example. Who are we talking about? Lucas: Let's use a marketing manager at a mid-sized B2B SaaS company. Let's call her Priya. She's responsible for content, social media, some event support. She's good — produces solid work. But whenever her boss, the VP of marketing, asks her to join a new cross-functional project or review a partner's collateral, she says, 'I'd love to, but I'm really swamped right now.' Luna: I've seen that exact dynamic. The VP starts to see her as not a team player. But maybe there's more to it. Lucas: There almost always is. So let's unpack what's behind 'I'm too busy.' I think there are three main drivers. First, genuine overload — she truly has more work than hours. Second, unclear priorities — she doesn't know which of her current tasks are actually important, so everything feels urgent. And third, and this is the one managers often miss — avoidance. The new task might be something she's unsure how to do, or she's afraid of failing at it. Luna: Avoidance disguised as busyness. That's subtle. How do you tell the difference? Lucas: You have to dig a little. Start by validating the workload. Say something like, 'I hear you're stretched. Let's look at your plate together.' Then ask them to walk you through their current priorities and deadlines. If they can rattle off a clear list with reasonable timelines, they're probably genuinely overloaded. If they're vague or everything is 'urgent,' you might have a prioritization problem. And if they get defensive or change the subject, avoidance might be at play. Luna: So the first move is not to assign the task. It's to understand their current state. Lucas: Exactly. And that's a shift from how many managers operate. We're trained to delegate, not to negotiate. But if you just pile on, you burn people out or they start cutting corners. In Priya's case, her VP sat down with her and asked her to list everything she was working on. It turned out she was spending fifteen hours a week on social media posts that were getting very low engagement, because she felt she had to maintain a certain posting cadence. Luna: Fifteen hours a week on low-impact work. That's a classic capacity trap. Lucas: Right. So the VP helped her create a 'stop doing' list. They agreed to cut the social posting frequency in half and automate some of the scheduling. That freed up about eight hours a week. Then they reprioritized: the new cross-functional project became a top-three priority, and she moved lower-impact tasks to a 'when time allows' list. Luna: That's a concrete outcome. But what if the employee is using 'busy' to avoid something specific? Like they don't want to do the new task because it's outside their comfort zone? Lucas: That's harder. In that case, you need to ask about the task itself — not just the workload. 'What's your take on this project? Do you feel equipped to contribute?' Sometimes they'll admit they're worried they don't have the skills. Other times they'll say it's not a good use of their time, which is actually a valid point if they're senior enough. The key is to make it safe for them to say 'I'm not comfortable with this' instead of hiding behind busyness. Luna: So you're essentially giving them permission to be honest about the real reason. Lucas: Yes. And you have to model that honesty yourself. If you suspect avoidance, you can say, 'I want to make sure this is a good fit for you. If there's a part of it that feels daunting, I'd rather know now so we can figure it out together.' That approach preserves their dignity and keeps the conversation productive. Luna: What about the manager who hears 'I'm too busy' from multiple team members? At that point, it might be a systemic issue, not individual. Lucas: Absolutely. If half your team is saying they're too busy, you likely have a capacity or prioritization problem at the team level. Maybe you're taking on too many projects, or your planning process is broken. In that case, the fix isn't coaching individuals — it's rethinking how work gets assigned. I've seen teams do a 'work stoplight' exercise where every project gets rated green, yellow, or red based on strategic importance. Anything red gets dropped or postponed. That immediately clarifies what's truly essential. Luna: That reminds me of a story from a friend at a fintech startup. The CTO said yes to every feature request, and the engineering team was constantly in 'we're too busy' mode. They finally did a prioritization workshop and killed three major projects. Within a month, morale went up and they actually shipped faster. Lucas: Classic example. The 'too busy' response is often a symptom of a leadership failure to set clear priorities. But let's go back to the one-on-one dynamic. Say you've validated, reprioritized, and the employee still says 'I'm too busy' when you approach them. What then? Luna: That's when you might need to set a boundary, right? Lucas: Yes. At some point, it becomes a performance issue. If you've given them the tools to manage their workload and they consistently resist taking on anything new, you need to name the pattern. 'I've noticed that every time I bring up a new initiative, you say you're too busy. I want to help you succeed, but part of your role is being available for emerging priorities. Let's figure out what's blocking that.' That frames it as a joint problem, not an accusation. Luna: And if they still don't budge? Lucas: Then you have a conversation about role fit. But that's a last resort. Most of the time, the three-step approach — validate, reprioritize, address avoidance — resolves it. Priya's story ended well. She took on the cross-functional project, delivered strong work, and eventually got promoted. The VP learned to check in on capacity before assigning new work. It changed how they operated. Luna: So the takeaway for managers: don't take 'too busy' at face value. Treat it as the start of a conversation, not the end. Lucas: Exactly. And if today's episode gave you a new way to think about that conversation, that's exactly what we're here for. These shows stay ad-free because listeners support them — you can find us at buy me a coffee dot com slash fexingo. Just a simple way to keep the content going. Luna: Yeah, and it really does make a difference. We hear from listeners who say they use these frameworks in their teams every week. That's the whole point. Lucas: So next time someone tells you they're too busy, pause. Ask to look at their list. Help them decide what not to do. That might be the most valuable thing you do as a manager this week. Luna: And if you've got a phrase you hear all the time from your team that we haven't covered, let us know. We might do an episode on it. Lucas: For now, I'm Lucas. Luna: And I'm Luna. Lucas: See you next Monday.