Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says That's Not Possible
Transcript
- Lucas: You pitch a new workflow, a process tweak, a pilot program. And before you've finished your sentence, one of your team members says it: 'That's not possible.' Not 'I have concerns,' not 'Let me think about the constraints' — just a flat 'no.' Luna: It's a conversation killer. And if you're a first-time manager, it can make you second-guess yourself before you've even started. Lucas: Right. So today I want to talk about the employee whose default answer is 'that's not possible' — not because they're trying to be difficult, but because that phrase often masks something else: fear, lack of context, or a history of failed initiatives. Luna: What's the difference between a healthy skeptic and someone who just shuts things down? Lucas: A healthy skeptic says 'I see a problem with X, Y, Z.' The 'that's not possible' person doesn't engage with the specifics. They close the door. I had a case in mind — a senior analyst at a mid-sized logistics firm. Every time the team proposed a process change, he'd say 'that won't work because the system can't handle it.' No elaboration. Luna: And the system actually could handle it? Lucas: Sometimes yes, sometimes no. But he never offered alternatives. So the team stopped bringing ideas to him. And his manager — a first-time manager, by the way — was stuck. Luna: So what did she do? Lucas: She started by scheduling a one-on-one with a very specific agenda. Not 'let's talk about your attitude' — that would have put him on the defensive. She said, 'I'd like to walk through the last three proposals you said weren't possible, and I want to understand your full reasoning.' Luna: That's a smart reframe. It's curious, not accusatory. Lucas: Exactly. And what she found was that this analyst had been burned twice before. He'd implemented changes that senior leadership then reversed, and he felt like his time was wasted. So 'that's not possible' was actually 'I'm not going to invest energy in something that'll get killed anyway.' Luna: So it's a trust issue, not a competence issue. Lucas: Exactly. The root cause was a lack of psychological safety and a history of failed change. So the fix wasn't to argue with him — it was to rebuild his sense that his effort would be respected. One technique she used was the 'pre-mortem' brainstorming session. Luna: Pre-mortem — that's where you assume the project failed and then work backward to figure out why, right? Lucas: Yes. Instead of asking 'Can we do this?' she asked 'If this project fails six months from now, what went wrong?' That flipped the script. Suddenly the analyst's objections became valuable input instead of roadblocks. He went from 'that's not possible' to 'well, if we don't fix the data pipeline first, it will fail.' Luna: And that's a much more productive conversation. He's now owning part of the solution. Lucas: It also changed his role. The manager started explicitly asking him to be the 'risk identifier' on projects. She'd say, 'I need you to tell me everything that could go wrong — not whether it's possible, but what we need to watch out for.' Luna: So she turned his negativity into a superpower. Lucas: Exactly. And after a few months, his language shifted. He'd say 'this is risky unless we address X' instead of 'this won't work.' That's a huge win for a manager. Luna: I think this is genuinely useful. I mean, a lot of us have that one person on the team who does this, and it can be exhausting. If today's episode helped you reframe a tough conversation, I'd say that's a pretty good use of a Monday morning. Lucas: Yeah, and the way these stay ad-free is listener support. If you got something out of this, you can keep it going by buying us a coffee — buy me a coffee dot com slash fexingo. It's a small way to say this kind of content matters to you. Luna: And we really appreciate it. Okay, back to the playbook — one more technique I want to get to. Lucas: So the second technique is about how you frame your own asks. If you know you have a 'that's not possible' person, don't lead with the solution. Lead with the problem. Luna: Give them ownership of the solution from the start. Lucas: Right. Instead of saying 'I think we should implement a new CRM,' say 'Our response times have slipped twelve percent this quarter. What do you think we should do?' Now they can't just say 'that's not possible' — they have to engage. Luna: That's a subtle shift, but it changes the dynamic completely. They're now problem-solving with you, not reacting to you. Lucas: And the beauty is that over time, that person starts to internalize that they're expected to contribute solutions, not just shoot down ideas. Their identity shifts from 'critic' to 'problem-solver.' Luna: So for a first-time manager listening, what's the one takeaway? If you have someone who always says 'that's not possible,' what's the first step? Lucas: First step: don't take it personally. Second step: get curious. Ask them to walk you through their reasoning in a structured way. You might uncover a past trauma or a legitimate constraint you didn't know about. And third, reframe their role so their skepticism is an asset, not a liability. Luna: That's solid advice. And I think for many managers, the hardest part is not getting defensive themselves. Lucas: Absolutely. The moment you match their negativity with your own frustration, you've lost the conversation. Stay curious, stay specific, and you can turn a blocker into a builder. Luna: Alright, thanks Lucas. And thanks to everyone listening. We'll be back next week with another Manager Monday.