Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Complains
Transcript
- Lucas: You have a team member who finds something wrong with everything. The project timeline is too tight, the software update is clunky, the coffee in the break room is lukewarm. Every one-on-one turns into a laundry list of grievances. And the rest of the team starts absorbing the negativity. Luna: The chronic complainer. It's one of the hardest dynamics for a new manager because you want to be empathetic, but you also feel the energy drain. Lucas: Exactly. And the instinct is to either try to fix every complaint or just nod along until the meeting ends. Neither works. So today I want to give you a specific three-step framework. I'll call it validate, redirect, set boundaries. Luna: I like that. And I'm guessing the validation part is the one most managers skip, because they're afraid of encouraging the complaining. Lucas: Right. But if you skip validation, the employee feels unheard and doubles down. So step one, you acknowledge the frustration without agreeing with the conclusion. You say something like, 'I hear you on the timeline concern. It's frustrating when deadlines feel tight.' You're not saying the timeline is wrong. You're saying the feeling is valid. Luna: That's different from 'you're right, the timeline is impossible.' And it keeps you from being pulled into their frame. Lucas: Exactly. Then step two is the redirect. This is where you pivot from the complaint to a question about what they can control. For example, 'Given the current deadline, what's one thing you think we could adjust to make it more manageable?' You're inviting them to be part of the solution. Luna: So you're essentially training them to shift from problem-finding to problem-solving. But what if they just keep circling back to the complaint? Lucas: That's when you need step three, which is setting a boundary. And this is the part most managers avoid because it feels confrontational. But it's actually kind. You can say, 'I notice we've talked about this a few times without a proposed solution. Going forward, I'd like us to come to these one-on-ones with at least one idea for how we might address the issue.' Luna: That's a clear expectation. And it puts the ball in their court. I've seen managers who just say 'stop complaining' and that backfires because the employee feels attacked. Lucas: Exactly. The boundary isn't punitive. It's a new operating standard. And you have to be consistent. If they come in with another complaint without an idea, you gently remind them of the new norm. 'Remember, I'm looking for us to problem-solve together. What's one thought you have?' Luna: Let me push back a little. What about the employee who genuinely has valid complaints? Maybe the timeline really is unreasonable or the software is broken. How do you distinguish chronic complaining from legitimate concern? Lucas: That's a great question. The key is pattern. Chronic complainers tend to have complaints across multiple unrelated domains. If someone only ever complains about one thing — say, the broken software — that's a legitimate issue you should escalate. But if the same person complains about the software, the coffee, the parking, the meeting schedule, and the lighting, that's a pattern of negativity. Luna: So you're looking for breadth, not depth. One deep complaint is a signal. A wide range of shallow complaints is a habit. Lucas: Exactly. And the habit usually stems from a sense of powerlessness. The employee feels they have no control, so complaining is their way of regaining a sense of agency. The redirect gives them agency back, but in a constructive way. Luna: That's a good insight. I've also seen that chronic complainers often get a secondary gain — like attention or sympathy from the manager. So by redirecting to problem-solving, you remove that payoff. Lucas: Right. You're not giving them the dopamine hit of you agreeing. You're giving them the satisfaction of actually influencing something. And that's more durable. Luna: Before we move on, I want to acknowledge something. If today's episode helps you handle a tough one-on-one this week — and I hope it does — just know that this show stays ad-free because of listeners who support it at buy me a coffee dot com slash fexingo. It's how we keep bringing you real, practical management content without sponsored segments. Lucas: And we really appreciate that. It's a small gesture that makes a big difference in keeping this going. So if you find value here, that's the way to keep it ad-free. Luna: Okay, back to the framework. Lucas, you mentioned consistency. How do you hold the boundary when the employee tests it? Lucas: They will test it. The first time they come in with a complaint and no idea, you gently remind them. If it happens again, you might say, 'I really want to help with this, but I need you to bring a proposed solution so we can move forward. Let's reschedule for tomorrow and you can come with one idea.' Luna: You actually end the meeting? That's strong. Lucas: It is strong, but it's also clear. It communicates that your time is valuable and that the new standard is non-negotiable. And it's not punitive — you're offering to meet again. But you're not going to spend the hour listening to complaints without progress. Luna: I can see that working for some people. But I wonder about the employee who feels genuinely unheard and then gets cut off. Could that damage trust? Lucas: It could, if you skip the validation step. That's why you always start with 'I hear you.' The boundary comes after they've been heard. If you go straight to boundary without validation, it feels like dismissal. Luna: So the sequence matters. Validate, then redirect, then boundary only if needed. Lucas: Exactly. And most employees respond to the redirect. They actually want to be part of the solution. The chronic complainers are often just stuck in a habit. Once you show them a different path, they take it. Luna: Let's talk about the team impact. How do you handle it when the complaining spreads? Lucas: That's a critical point. If one person's negativity is affecting others, you may need to address it team-wide without singling anyone out. In a team meeting, you can set a norm: 'In our one-on-ones, I'm going to focus on solutions. I'd love for all of us to bring at least one idea for any challenge we discuss.' That way, the norm applies to everyone. Luna: It normalizes the problem-solving culture. And if the chronic complainer still doesn't shift, then you have a private conversation about the pattern. Lucas: Right. And you can use data. 'In our last three one-on-ones, we've spent about twenty minutes per meeting on concerns without proposed solutions. I'd like to shift that so we can make progress. How can I support you in bringing ideas?' Luna: That's objective. It's not 'you complain too much,' it's 'here's how we're spending our time.' That's harder to argue with. Lucas: Exactly. And it opens a conversation about what's underneath the complaining. Sometimes the employee is overwhelmed, or feels unsupported, or has a personal issue. The complaining is a symptom. Once you address the root cause, the symptom often disappears. Luna: Do you have a story from your own experience where this worked? Lucas: I do. Early in my management career, I had a team member who complained about everything. I tried the fix-everything approach and it exhausted me. Then I tried the nod and ignore approach and it got worse. Finally, I used this framework. I validated her frustration about a specific process issue, then asked what she'd change. She came up with a good idea. We implemented it. And over time, she started bringing more ideas and fewer complaints. It wasn't overnight, but within a few months, her tone shifted completely. Luna: So the key was giving her ownership over the solution. She felt empowered instead of powerless. Lucas: Exactly. And that's the core of this approach. The chronic complainer is often someone who feels they have no control. By giving them a structured way to influence outcomes, you turn a drain on the team into a contributor. Luna: That's a great note to end on. Just to recap: validate the feeling, redirect to a solution, and set a boundary if needed. And watch for the pattern, not the one-off complaint. Lucas: And if you try this, let us know how it goes. We'd love to hear a success story or a challenge. That's it for this episode of Manager Mondays.