Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Always Says I'm Fine
Transcript
- Lucas: So you've got a team member who keeps saying 'I'm fine' but their work is slipping. Maybe they're quieter in meetings, missing small deadlines, or just seem checked out. You ask how they're doing and they give you that flat smile and say 'yeah, fine, just busy.' Luna: Oh, the fine trap. I think every manager has been there. And it's especially hard when it's a high-performer who used to be super engaged. Lucas: Exactly. That's the profile that makes this so tricky. If it's someone who's always underperformed, you have a different playbook. But when someone who used to bring energy and ideas suddenly goes quiet, you worry you're about to lose them — or worse, that they're quietly burning out and you missed it. Luna: Right. And the standard 'are you okay?' question often backfires. It puts them on the defensive. Lucas: Yeah, because 'I'm fine' is a script. It's automatic. And if you push past it too directly, they just reinforce the wall. So the question is: what do you say instead? I want to walk through a real case. I was talking to a marketing director at a mid-size SaaS company — let's call her Jenna. She had a direct report named Sarah, a senior marketing manager who had been on fire for two years. Then over about six months, Sarah's output dropped maybe 30 percent. She was still producing good work, but less of it. She stopped volunteering ideas. She missed two campaign deadlines. And every time Jenna checked in, Sarah said she was fine. Luna: That's the hardest kind of person to manage, because they're not failing enough to trigger a performance plan, but they're clearly not thriving. Lucas: Exactly. And Jenna's instinct was to ask directly: 'You seem off, is everything okay?' But Sarah just doubled down on fine. So Jenna tried a different approach. Instead of asking about feelings, she named the specific behavior she was seeing. She said: 'Sarah, I noticed you passed on two speaking opportunities this quarter, and you used to jump at those. I'm not assuming anything is wrong, but I want to understand your thinking.' Luna: That's smart. It's concrete. It doesn't ask Sarah to label her own emotional state, which is hard for a lot of people. Lucas: Right. And Sarah actually opened up a little. She said she'd been feeling like her ideas weren't landing with the new VP, so she'd pulled back to avoid embarrassment. She wasn't 'fine' — she was strategically retreating. And that's a conversation you can actually work with. Luna: So the framework is: name the discrepancy you're seeing, not the emotion. Then give them a low-stakes entry point to talk about what's underneath. Lucas: Exactly. And then — and this is the part a lot of managers skip — you set a follow-up. Not 'let me know if you want to talk,' but 'I'm going to check in with you in two weeks, same time, just to see how things are going.' That takes the pressure off the employee to initiate. Because if they're in retreat mode, they're not going to come to you. Luna: It also signals that you're not going to forget about it. You're not just doing a drive-by concern check. Lucas: Exactly. And here's the thing — this approach works because it treats the employee like a professional, not a patient. You're not diagnosing them. You're saying: I see a change in your behavior, I'm curious about it, and I want to support you. That's respectful. Luna: It also avoids the trap of making it about you. I've seen managers who get defensive — like 'I thought we had a good relationship, why won't you tell me?' That just adds guilt. Lucas: Yeah, that's a fast way to make someone shut down even more. So let's talk about what happens if they still say 'I'm fine' after you name the specific behavior. Jenna had that happen once with a different employee. She said 'I noticed you've been leaving right at 5 every day when you used to stay until 6 or 7,' and the employee said 'Yeah, I'm just trying to have better boundaries.' Luna: Which sounds reasonable. But if performance is dropping, 'better boundaries' might be a cover for disengagement. Lucas: Yes. So Jenna said: 'That's great, I support healthy boundaries. But I also noticed your project timelines have slipped. Let's talk about whether your workload is realistic or if something else is going on.' She didn't challenge the boundaries story — she acknowledged it and then tied it to the work outcome. That's key. You're not interrogating their personal life. You're discussing performance. Luna: So the script is: acknowledge their explanation, then redirect to the observable business impact. Lucas: Exactly. And that keeps the conversation professional. You're not a therapist. You're a manager. Your job is to help them do their best work. If something personal is interfering, they can choose to share it. But you don't need to know the personal details to address the work problem. Luna: I think a lot of first-time managers especially struggle with this. They feel like they need to be a friend or a counselor. But the most helpful thing you can do is stay in your lane — performance and development. Lucas: Yeah. And by staying in that lane, you actually create more safety. Because the employee knows what to expect. They know you're not going to pry. You're going to focus on what's measurable and actionable. That's actually more trustworthy than someone who tries to be your best friend. Luna: Speaking of trust and staying in our lane — you know, we deliberately keep this show ad-free. No sponsors, no affiliate links. The reason is simple: we want every episode to be exactly what you need, not what an advertiser wants. If that approach has helped you — whether you're a new manager or a seasoned one — the best way to keep it going is to throw a few dollars in the tip jar. It's buy me a coffee dot com slash fexingo. No pressure, just a way to say 'keep going.' Lucas: Yeah, it's a small thing that makes a big difference for us. And we appreciate everyone who's chipped in. Now back to the 'I'm fine' conversation — let's talk about the follow-up. So you've had the first conversation, you've set a check-in in two weeks. What do you actually say in that follow-up? Luna: Right, because if you just say 'how are things?' you're back at square one. Lucas: Exactly. So Jenna's approach was to reference the previous conversation briefly. She'd say: 'Last time we talked, you mentioned you were pulling back because your ideas weren't landing. I've been thinking about that. Have you noticed any changes since we spoke?' That does two things: it shows you remembered, and it asks about change over time, not just current state. Luna: It also puts the employee in a reflective mode rather than a defensive mode. Lucas: Yes. And if the employee says 'I'm still fine, nothing's changed,' that's actually useful information. It tells you that the first conversation didn't fully land, and you may need to escalate. You can say: 'Okay, I respect that. But I'm still seeing the same pattern in your output. So I need to set some expectations around these deadlines going forward. Let's agree on a plan.' Luna: So at that point it shifts from coaching to performance management. And that's okay. You can't force someone to open up. Lucas: Right. And sometimes the 'I'm fine' is actually true — they're not in crisis, they've just become disengaged because they're bored or they don't see a future. That's still a problem, but it's a different kind of conversation. You might say: 'I hear you that nothing's wrong, but your engagement level has clearly changed. Let's talk about your career trajectory and what would excite you.' Luna: So 'I'm fine' can mask boredom as much as burnout. Lucas: Exactly. And that's actually easier to solve. You can give them a stretch project, a new skill to learn, a mentorship opportunity. The point is, you have to resist the urge to take 'I'm fine' at face value. As a manager, your job is to be professionally curious. Not nosy — curious. Luna: I think the biggest mistake managers make in this situation is accepting the 'I'm fine' too quickly because it's comfortable. They don't want to rock the boat. Lucas: Yeah, and that's understandable. But the cost of avoiding that discomfort is huge. You could lose a great employee who just needed someone to notice and care enough to ask a better question. Or you could let a performance problem fester until it becomes a real issue for the team. Luna: So the takeaway for this episode: next time an employee says 'I'm fine,' don't just nod. Name what you're seeing. Acknowledge their response. Then connect it to the work. And follow up. Lucas: Yeah. It's a three-step loop: observe, connect, revisit. And it works whether the employee is struggling with something personal, or just going through a rough patch professionally. The key is that you're being a manager — not a mind reader. And sometimes that's exactly what they need.