Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says That Is Not Possible
Transcript
- Lucas: Luna, I want to talk about the employee who responds to every new suggestion with the same two words: 'That's not possible.' Luna: Oh, I know that one. It's like a reflex. You propose something, and before you even finish the sentence, you're hearing why it can't be done. Lucas: Exactly. And it's a particularly draining form of resistance because it sounds rational. It sounds like they're being realistic. But after the tenth time, you start to wonder if they're actually trying to protect the team from failure — or if they're just comfortable with the status quo. Luna: I had a colleague once who would do that with every feature request. It got to the point where people would just stop bringing ideas to the team because they knew they'd get shot down. Lucas: That's the cost, right? Not just the ideas that get blocked, but the ones that never even get raised because the team knows the default response. There's a real innovation tax that comes with a chronically negative voice in the room. Luna: So where do you start? How do you have that first conversation? Lucas: The first step is to figure out whether this is a pattern or just a personality quirk. You want to look for a few things: Is it across all topics, or just certain areas? Do they only shoot down ideas from others, or their own too? And importantly — are they right sometimes? Luna: That last point is interesting. Because if they're actually protecting the team from genuinely bad ideas, then you don't want to squash that. Lucas: No, you definitely don't. The goal is to channel the skepticism into a more productive form. But if it's a blanket negative response, then you have a pattern worth addressing. Luna: One of the things I've found useful is to reframe the question. Instead of saying 'Is this possible?', ask 'What would it take to make this possible?' Lucas: That's a great technique. It shifts the conversation from a yes-no judgment to a problem-solving exercise. And it forces the person to engage with the details rather than just reacting. Lucas: I remember a manager I had who did exactly that. There was an engineer on the team who was brilliant but had this default 'can't be done' response. The manager started every such conversation by saying, 'Assume it's possible. Now tell me what would have to change for that to happen.' Luna: And did it work? Lucas: It took a few weeks, but gradually the engineer started engaging with the hypothetical. He'd say things like, 'Well, we'd need to change the database schema, and we'd need to get a new vendor, and the timeline would stretch.' And the manager would just say, 'Okay, so what would that take?' Luna: It sounds like you're training the brain to think in terms of trade-offs rather than absolutes. Lucas: Precisely. Because the honest answer is that most things are possible — they just have a cost. And the employee who says 'not possible' is often really saying 'I don't want to deal with the cost.' Luna: So how do you call that out directly without putting them on the defensive? Lucas: You can say something like, 'I hear you that this is hard. What's the biggest constraint you're seeing? Let's unpack that.' That way, you're acknowledging their concern but also demanding specificity. Luna: That's a good ground rule. It puts the burden on them to do some thinking, not just reject. Lucas: And it also changes the culture of the whole team, not just that one individual. Because once the rule is out there, other people start holding each other to it. Luna: I also think it's worth checking whether the person feels safe enough to say 'I'm not sure how' — instead of hiding behind 'that's not possible.' Lucas: That's a good point. Sometimes 'impossible' is a mask for fear of failure or lack of confidence. If they think they'll be punished for not knowing, they'll default to the safer negative. Lucas: So part of the work is building psychological safety. Making it clear that it's okay to say 'I don't know how we'd do that' or 'That sounds hard, but let's try to figure it out.' Luna: Right. And the manager has to model that too. If the leader is the one saying 'we can't' all the time, then no one else is going to step up. Lucas: Absolutely. The manager sets the tone. If they approach every idea with curiosity, the team will mirror that. If they shut things down, the team will stop bringing things up. Luna: Let's talk about the conversation itself. How do you actually deliver that feedback? Like, the first one-on-one where you bring this up. Lucas: You want to use specific examples. Don't say 'you always shoot things down.' Say 'in Tuesday's meeting, when we discussed the new client portal, you said it wasn't possible. Can we talk about that?' Lucas: Then you want to ask about the thinking behind it. Maybe they had a valid reason. But you also want to express the impact: 'When you say that, it stops the conversation. I'd like us to explore ideas more before we decide.' Luna: So it's about making the invisible visible. Lucas: Exactly. And then you agree on a new behavior. Something like, 'Next time, let's try to phrase it as a question — 'what would it take?' — instead of a verdict.' Luna: I've also seen managers use a 'pre-mortem' — asking, 'If this did fail, what would be the most likely reasons?' That can surface the same concerns without the negative framing. Lucas: That's a brilliant tool. You get all the same intelligence from the skeptic, but they're not in the position of trying to kill the idea. They're just predicting what might go wrong. Lucas: And then you can address those risks head-on, which actually makes the plan stronger. Luna: So we've got reframing questions, ground rules, pre-mortems. What else? Lucas: One more thing: sometimes you have to make the adjustment personal. If it's really hampering the team, you might say, 'Look, I appreciate your rigor, but the way you express it is causing people to disengage. I need you to bring your concerns in a way that invites collaboration.' Luna: And if they still don't change? Lucas: Then you have to escalate. Maybe it's a deeper issue — maybe they're burned out, or they feel threatened by change. Or maybe it's just a poor fit for the role. But at least you've given them a clear path to improve. Luna: It's like that saying — 'a broken clock is right twice a day.' The skeptic might have valuable insights, but if they stop the clock, the whole team misses the time. Lucas: Ha, that's a good analogy. And it ties back to the core goal: you want to keep the team moving forward while still respecting the realities. Lucas: Before we wrap up, I want to mention something that's been on my mind. We make this show five days a week, and it's completely ad-free. That's only possible because a small group of listeners chip in monthly through buy me a coffee dot com slash fexingo. Luna: Yeah, it's a real passion project. We don't have a big studio or sponsors — it's just us and our laptops, and the support of people who find the show useful. Lucas: So if you're one of those people who gets something out of these conversations, that's a way to keep us going. No pressure, just knowing it's there helps. Luna: And back to today's topic — one last thought: the next time you hear 'that's not possible,' try asking, 'What would it take?' You might be surprised at what you learn. Lucas: And if you're the one saying it, catch yourself. Ask if you're really helping the team or just protecting your comfort zone. That's the real question.