Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says Let Me Get Back to You
Transcript
- Lucas: There's a type of employee who is almost never the source of drama. They don't push back, they don't overcommit, they don't disappear. But they do something that drives managers quietly crazy. Luna: Let me guess — they always say 'let me get back to you.' Lucas: Exactly. And on the surface, it sounds perfectly reasonable. Professional, even. But when it becomes the default response to every question, every decision, every request for input, it grinds the team's momentum to a halt. Luna: I've definitely worked with people like that. You ask a simple question — 'which vendor do you prefer?' — and they say 'let me look into it and get back to you.' Two days later, nothing. Lucas: Right. And the manager is stuck in a weird position. You can't accuse them of being unresponsive because they technically responded. But you also can't move forward. They've created a holding pattern. Luna: So what's really going on underneath? Is it just indecisiveness? Lucas: Partly. But there's usually more to it. In my experience, it's often a blend of perfectionism and conflict avoidance. The employee wants to give the 'right' answer, so they need more time. And they don't want to risk being wrong, so they delay committing. Luna: That makes sense. There's also a fear of being seen as impulsive or not thorough. Lucas: Yes. And sometimes it's just poor time management. They genuinely intend to get back to you, but they get buried and the task falls off their radar. A 2023 study in Harvard Business Review found that ambiguous response patterns like this cost teams an average of 4.7 hours per week in follow-up overhead — emails, Slack messages, meeting recaps. Luna: 4.7 hours? That's basically half a day wasted on chasing replies. Lucas: Exactly. So as a manager, the goal isn't to eliminate thoughtfulness. It's to create a structure where the employee can be thoughtful without creating a bottleneck. Luna: What's the first step? Do you confront them about it directly? Lucas: I'd start with a gentle observation, not a confrontation. Something like: 'I've noticed that when I ask you for input, you often say you'll get back to me. I appreciate that you want to give a thorough answer, but sometimes I need a quicker signal so we can keep things moving.' Luna: That's good. It names the pattern without making them feel defensive. Lucas: Then you negotiate a specific response time. 'If I ask you something during our morning standup, can you commit to getting back to me by end of day? If you need more time, just say, I need 48 hours on this, and then I'll hold you to that.' Luna: So you're replacing the open-ended 'let me get back to you' with a concrete deadline. Lucas: Exactly. And you're giving them permission to be honest about how much time they actually need. The problem isn't the delay — it's the uncertainty. Once you have a deadline, you can manage around it. Luna: What about the perfectionism angle? Some people are afraid to give a bad answer. Lucas: That's where you create a 'good enough' culture. You can say: 'I don't need the perfect answer. I need a solid 80 percent answer by Friday. We can iterate after that.' That reduces the pressure. Luna: There's a technique I've heard called 'deadline first.' Instead of asking the question and waiting for a response, you give the deadline upfront. Lucas: That's powerful. For example, instead of 'What do you think about the Q3 budget?', you say 'I need your thoughts on the Q3 budget by Wednesday at 3 PM. If I don't hear from you, I'll assume you're good with my proposal.' Luna: That shifts the burden. Now the employee knows exactly when they need to act, and if they miss it, the decision gets made without them. Lucas: Right. And that's not punitive — it's just a way to keep the organization moving. Most people respond well to clear boundaries once they understand them. Luna: Can you share a real example where this worked? Lucas: Sure. I worked with a mid-size SaaS company last year. They had a senior product manager who was brilliant but notoriously slow to respond. Every question got a 'let me check and get back to you.' His manager was frustrated because product decisions were stalling. Luna: Classic case. Lucas: They implemented a simple 'answer threshold' system. For any request that came in, the PM had to respond within four hours with either an answer or a specific time when he would have an answer. If he said 'I need more time,' he had to provide a deadline. They tracked it in a shared doc. Within six weeks, his reply latency dropped by 60 percent. Luna: Sixty percent? That's huge. And it probably reduced the team's follow-up overhead too. Lucas: Absolutely. The key was that it wasn't about speed for speed's sake. It was about predictability. The team could plan around his responses because they knew when to expect them. Luna: I think this is a great example of how a system can solve a behavioral issue without a difficult conversation. Lucas: Exactly. And that's really the art of management — creating structures that help people do their best work without needing constant intervention. Luna: You know, this kind of practical advice is exactly why people listen to this show. And it's also why we keep it ad-free. We'd rather you get straight value without interruptions. Lucas: If this kind of content has helped you think through a management challenge, and you want to support that choice, you can find us at buy me a coffee dot com slash fexingo. It's a simple way to keep us going without any ads. Luna: Yeah, it really does make a difference. And we appreciate every bit of support. Lucas: So back to the 'let me get back to you' employee — another angle to consider is the possibility that they're using this phrase as a polite way to avoid saying no. Luna: Ah, right. They don't want to refuse a request outright, so they buy time hoping the issue goes away. Lucas: Exactly. In that case, you need to give them permission to say no. You can say: 'It's okay if the answer is no. I'd rather hear that now than wait three days for the same answer.' Luna: That's a direct way to cut through the ambiguity. Lucas: And it works. Once the employee realizes that 'no' is acceptable, the 'let me get back to you' frequency tends to drop significantly. Luna: What if the behavior persists despite all these interventions? Lucas: Then it becomes a performance issue. You escalate to a more formal conversation: 'We agreed on a 24-hour response time, but I've noticed you've been missing that. What's getting in the way?' And then you work on a plan together. If nothing changes, you have to consider whether this role is the right fit. Luna: But for most people, a clear structure and a little coaching is enough. Lucas: Exactly. The goal is to help them succeed, not to catch them failing.