Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says That Will Take Too Long
Transcript
- Lucas: So it's Monday morning, you're in your one-on-one, and you suggest a small process tweak. Maybe it's a new reporting template, maybe it's a slightly different way to handle client follow-ups. And your employee looks at you and says, 'That would take too long.' Luna: Oh, I've heard that one. It's like a wall just goes up. Lucas: Right. And the immediate instinct is to argue. You want to say, 'It's just an hour, come on.' But that's usually a mistake. Because 'that will take too long' is rarely about the actual time. It's a signal. It's a protective reflex. Luna: Protective against what, exactly? Lucas: Could be a few things. Fear of scope creep — they've been burned before by a 'quick task' that ballooned into a week. Or it's a hidden capacity issue — they're already stretched thin, and they don't feel safe saying 'I'm overloaded' directly. Or it's a trust issue — they don't believe the request is actually as small as you're making it sound. Luna: So you're saying the time estimate is not the real objection. Lucas: Exactly. And if you treat it as a factual dispute, you lose. You get into a debate about minutes and hours, and nobody wins. The better move is to get curious. Ask a question like, 'Help me understand — what's the longest part of that for you?' Luna: That's a good question. It shifts from defending the request to understanding their reality. Lucas: And nine times out of ten, you'll get something concrete. Like, 'Well, I'd have to pull data from three different systems, and that's a whole afternoon.' Now you have something to work with. You can say, 'What if we pull it from just one system for now? We don't need the perfect version.' Luna: So you're breaking it down. Making it smaller. Lucas: Right. There's a technique I like to call the two-hour pilot. Instead of asking for a full rollout, ask for a two-hour experiment. 'Can we try this on just one client for two hours, then check in?' That lowers the perceived cost. It also gives them permission to stop if it doesn't work — which is often what they're really afraid of. Luna: I like that. It's like a 'try before you buy' for work tasks. Lucas: Exactly. And here's the thing: if the employee still says 'that will take too long' after you've offered a two-hour pilot, then you've got a different conversation on your hands. It's not about the time anymore. It's about willingness, or maybe a deeper concern about the direction. Luna: And that's a harder conversation, but at least you know what you're dealing with. Lucas: Absolutely. I saw this play out recently at a mid-sized software company. A marketing manager wanted her team to start tagging every blog post with a new category structure. It was a pretty simple change, maybe thirty minutes of work per post. But one of her senior writers, who's usually great, immediately said, 'That'll take too long.' Luna: Oof. So what did she do? Lucas: She told me she almost pushed back. But instead, she asked, 'What's the longest part?' And the writer said, 'I have to go back and retag like forty old posts. That's a whole day.' Luna: Ah, so it wasn't the new posts. It was the backlog. Lucas: Right. So they agreed to only tag new posts going forward, and leave the old ones until a slow week. The writer was on board immediately. The change took about an hour total, and the backlog never got touched. Problem solved. Luna: That's such a simple fix. But it required her to not take the first answer at face value. Lucas: Exactly. And that's the core skill here. You have to resist the urge to either fight or cave. Fighting turns you into a micromanager. Caving teaches your employee that 'that will take too long' is a magic phrase that makes tasks disappear. Both are bad. Luna: So what's the middle path in practice? Like, if I'm a manager and I hear this tomorrow, what do I say? Lucas: Start with a version of: 'Help me understand what's driving that estimate.' Then listen. Really listen. Don't interrupt. When they're done, reflect back what you heard: 'So the data pull is the bottleneck, got it.' Then offer a smaller version: 'What if we just do it for the two most recent campaigns?' And then commit to a check-in: 'Let's try it for two weeks, and if it's not working, we'll stop.' Luna: That check-in part is key. It gives them an off-ramp. Lucas: Yes. And it also shows you respect their time. You're not asking for a blind commitment. You're saying, 'I trust your judgment, and I want to test this together.' Luna: I wonder if sometimes 'that will take too long' is also a way of saying 'I don't think this is a good use of my time.' Lucas: That's a great point. And that's a legitimate concern, right? If the task genuinely isn't worth the effort, you should want to hear that. But you can't get to that conversation if you just accept the first 'no' or blow past it. Luna: So you're saying it's not just about managing time — it's about managing trust. Lucas: Exactly. Every time you handle this well, you build trust. Your employee learns that you'll listen, that you won't dismiss their concerns, and that you'll work with them to find a reasonable path. That's the kind of manager people want to work for. Luna: And honestly, if you've been listening to this show and it's helped you think through a tricky conversation with your team, that's exactly the kind of thing we love to hear. It's also the kind of thing that keeps us going. Lucas: Yeah, we don't run ads, and we'd like to keep it that way. So if today's episode was worth the price of a coffee to you, the link is buy me a coffee dot com slash fexingo. Luna: It truly helps us keep making these conversations. And even if you can't, no worries at all — we're just glad you're here. Lucas: Now, back to that check-in. I think a common mistake is to set up a pilot but then never follow up. You say 'let's try it for two weeks,' and then it just becomes permanent. That's how scope creep actually happens. Luna: Right, because you never revisit whether it's worth it. Lucas: Exactly. So put a calendar invite for fifteen minutes in two weeks. And when you meet, ask two questions: 'What's been easier than you expected?' and 'What's been harder?' Then decide together whether to continue, adjust, or kill it. That's real partnership. Luna: I love that. It's not just about avoiding the phrase — it's about creating a culture where people feel safe to raise concerns, and where time is respected. Lucas: And that's the bigger win. When your team knows you'll actually listen to 'that will take too long,' they'll stop using it as a shield and start using it as a signal. They'll bring you problems instead of just resisting requests. Luna: So next time you hear it, take a breath and get curious. Lucas: Exactly. Ask the question, break it down, and set the check-in. You might be surprised at what you unlock.