Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Handle the Employee Who Always Says I Need a Day
Transcript
- Lucas: So we are starting this episode with a confession. I have definitely been the employee who says, I just need a day to think about it. Luna: Really? You, Mr. Decisive? Lucas: Yeah, especially early in my career. I'd get asked something in a meeting, my brain would freeze, and I'd buy time by asking for a day. Sometimes I actually used it. Other times I just let it slip and came back with the same non-answer. Luna: So as a manager, how do you tell the difference between someone who really needs that processing time and someone who's just kicking the can down the road? Lucas: That's exactly the question for today. We're going to dig into that specific phrase, I need a day, which is a lot more common than you'd think. And I've got a concrete framework that I've seen work, plus a case from a product team that turned this pattern around. Luna: Great, because I feel like a lot of managers default to one of two extremes: they either get frustrated and push for an answer now, or they let the employee set the pace forever. Lucas: Right, and both of those break trust. So let's start with the why. When someone says I need a day, what's actually going on? In my experience, there are three main reasons. One, they're genuinely overwhelmed and need time to process information. Two, they're using it as a politeness shield because they actually disagree or want to say no but don't want to say it in the moment. Or three, they're avoiding the decision altogether because they're afraid of getting it wrong. Luna: Interesting. And the manager's job is to figure out which one it is, right? Lucas: Exactly. And you can't do that if you just say, okay, get back to me tomorrow. You have to be more intentional. That's why I love this approach from a manager I worked with. She called it the three-step check-in. Luna: Okay, let's hear it. Lucas: Step one is to acknowledge the request without judgment. Something like, sure, take a day. That's fine. But then, step two, you ask a clarifying question to surface what they actually need. Like, is it that you need more data, or is it that you want time to think through the trade-offs? Or, are you feeling uncertain about something specific? Luna: That's smart. It gives the employee a chance to articulate their real need without feeling put on the spot. Lucas: And step three is to agree on what a good answer looks like by the time they come back. You can say, when we talk tomorrow, I'd like to hear your recommendation and the top two risks you're weighing. That way you're not just getting a gut feeling, you're getting structured thinking. Luna: That's powerful. It turns a vague delay into a productive deliverable. I've seen managers just say, okay, let's circle back tomorrow, and then the employee comes back with more questions instead of an answer. Lucas: Exactly. And that's where the frustration builds. But this framework keeps the ball in the employee's court while showing you respect their process. Now, there's a bigger issue here. What if this is a pattern, not a one-off? What if every decision, no matter how small, gets the I need a day treatment? Luna: Yeah, that's when it becomes a real problem. I've seen teams where the default for any question is, let me get back to you, and nothing ever moves forward. Lucas: So let's talk about that pattern. I remember a product team where the lead designer would say I need a day for almost every creative decision. It wasn't about data; it was about perfectionism. She was so afraid of presenting something half-baked that she'd rather stall. The manager, to his credit, didn't call it out directly. Instead, he started using the three-step check-in every single time. And after a few weeks, the designer started to realize that she was just using the day to avoid the discomfort of giving a preliminary answer. Luna: Did that change her behavior? Lucas: Eventually, yes. But it took something else too. The manager introduced a pre-mortem as part of the check-in. So instead of just asking for risks, they'd say, imagine it's six months from now and this decision led to a disaster. What's the most likely cause? That's a really different conversation than, what could go wrong? Because it forces you to commit to a scenario. Luna: That's a great technique. It's like you're giving the employee a safe space to voice their fears without having to admit they're afraid. Lucas: And it worked. Within two or three months, the designer was coming to meetings with provisional recommendations instead of asking for a day. She realized that the pre-mortem helped her see that her fears were usually not about the decision itself, but about how her work would be received. Luna: So sometimes the I need a day is really a mask for something deeper. As a manager, you have to be a bit of a psychologist. Lucas: A little bit. But you don't need to be a therapist. You just need to be curious. Another thing I've found useful is to set a decision deadline. Not in a harsh way, but like, I'd like to make a call by Friday, so can we meet Thursday afternoon to discuss your thoughts? That creates a gentle sense of urgency without pressure. Luna: And what about the employee who uses I need a day to avoid saying no to your face? Lucas: That's the politeness shield. And it's tricky because they're not trying to be difficult; they're trying to be polite. But the result is the same. You don't get a decision. I think the best move there is to make it easier for them to disagree. You can say something like, I might be wrong here, but I think this is the way to go. What are the chances I'm missing something? That invites a no without confrontation. Luna: Nice. So you're basically giving them permission to push back. Lucas: Exactly. And once they see that you're open to pushback, they might not need that day at all. But here's the thing: sometimes the employee really does need a day, and that's perfectly fine. The goal isn't to eliminate the need for reflection. It's to make sure the reflection is productive and doesn't become a pattern of avoidance. Luna: So how do you know when it's crossed the line from healthy processing to problematic avoidance? Lucas: Good question. I look for two things. One, is the employee coming back with new insights or a clearer recommendation? If yes, then the time was well spent. If they come back with the same vague answer, that's a red flag. And two, is the request proportional to the decision? If it's a low-stakes question like, which font should we use? and they need a day, that's probably overkill. Luna: So you're saying a manager can use that to sort of calibrate their expectations. Lucas: Yeah. And if you notice the pattern, it's worth addressing directly, but kindly. You could say, I've noticed you often ask for a day before making a decision. I'm curious what's driving that. Is it a need for more information, or is it something else? That opens up a conversation instead of a confrontation. Luna: That's a good approach. It's about being curious, not accusatory. Lucas: Exactly. And that leads to a broader point: a lot of management is about creating a culture where people feel safe to say, I need a minute, or even, I need to disagree, without fear. When you do that, the I need a day becomes less of a stall and more of a genuine request. Luna: You know, Lucas, this episode feels like it's giving managers practical tools they can use right away. And it's interesting how much of this comes down to communication. Lucas: It does. And that's a good reminder that if today's show was useful to you, this is how we keep it ad-free, through listener support. If you've gotten something from Manager Mondays, you can back us at buy me a coffee dot com slash fexingo. It's a simple way to keep these conversations going. Luna: Yeah, it really does help us keep the lights on and the coffee flowing. Thanks to everyone who's already chipped in. Lucas: So back to that pattern of avoidance. There's one more technique I want to mention, and it's something I call the I need a day reset. If an employee is stuck in a cycle of asking for a day but never coming back with something useful, you can reset the terms. Say something like, I'm happy to give you time, but I want to make sure it's productive. When we meet tomorrow, let's aim to leave with a decision, even if it's not perfect. And I'll help you work through the trade-offs right then. Luna: That's a good way to set an expectation without being harsh. Lucas: And it also signals that you're not going to let the decision drag on indefinitely. Sometimes employees need that structure, even if they don't ask for it. Luna: So, to wrap up, we've got the three-step check-in, the pre-mortem, and the reset. Anything else you'd add for a first-time manager who's struggling with this? Lucas: I'd say don't forget to follow up. If you've agreed on a day, make sure you actually have the conversation then. If you let it slide, you're teaching the employee that deadlines don't matter. So be consistent. Luna: Consistency is key. And that's a good note to end on. Lucas: Yeah. So next time someone says I need a day, you'll know what to do. And if you've got your own stories about managing reflective employees, we'd love to hear them. Until next time, keep the conversation going.