Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Always Says It Can't Be Done
Transcript
- Lucas: You've got a direct report who, every time you bring up a new idea, says 'that won't work' or 'that's impossible.' And they usually have a good reason. But it's happening so often that the team is starting to lose steam. Luna: That's such a draining pattern. And it's tricky because sometimes they're right — it genuinely is impossible. But when it becomes their default, it's a problem. Lucas: Right. Today I want to look at one specific case. A product manager at a mid-size SaaS company — let's call her Priya — she kept shutting down feature requests in sprint planning. Every time a stakeholder asked for something, she'd say 'we don't have the backend capacity' or 'that would break our data pipeline.' Luna: And was she wrong? Lucas: Not entirely. She was technically correct about the constraints. But her manager noticed that the team had stopped proposing new ideas altogether. They'd just wait for Priya to tell them why something wouldn't work. So the manager had to address the pattern, not the specific objections. Luna: So the diagnosis is that Priya's 'can't' was a learned behavior. Maybe she got burned before by overpromising, or she's a really good engineer who sees all the pitfalls. Lucas: Exactly. In Priya's case, it was a mix. She had been at the company for five years and had seen two big projects fail because of unrealistic timelines. So her 'can't' was actually a risk management reflex. But it was killing innovation. Luna: That makes sense. So the manager needs to validate the risk but redirect the energy. What did they do? Lucas: First step: they had a one-on-one where the manager said, 'I appreciate that you're protecting the team from overcommitment. I need you to also help us find ways to get to yes.' Then they introduced a simple framework: anytime Priya wanted to say 'can't,' she had to first say 'here's what would need to change to make this possible.' Luna: That's smart — it shifts from a blocker to a problem solver. It also forces her to articulate assumptions. Lucas: Right. So in the next sprint planning, when a stakeholder asked for a real-time dashboard feature, Priya started with 'the current architecture doesn't support that. But if we deprioritize the reporting module for two sprints, we could build a prototype.' That's a trade-off, not a shutdown. Luna: So she's still being honest about constraints, but she's offering a path forward. That seems way more productive. Lucas: It completely changed the team's energy. But the manager also had to address the emotional side. Priya later admitted she was afraid of being blamed if a project failed. So they agreed that if she proposed a creative solution and it didn't work, she wouldn't be penalized — as long as she learned from it. Luna: That's huge. The fear of failure is often the real root of the 'can't' mentality. Once you remove that, people are more willing to stretch. Lucas: There's also a tactical tool we can use. When an employee says 'that's impossible,' you can ask them: 'on a scale of 1 to 10, how impossible is it? And what would it take to move it down one point?' That breaks the binary and makes it a negotiation. Luna: I love that. It's like a design thinking technique — you're not accepting the constraint, you're working with it. Lucas: Exactly. And the key is to catch it early. If you let the 'can't' pattern persist, you'll end up with a team that's afraid to even suggest ideas. That's worse than any single missed feature. Luna: Speaking of which, I want to point out that this episode — like every episode — we do our best to give you practical, actionable advice. If that's been useful to you today, or in any of the past 45 episodes, there's a way to keep it going. Lucas: Yeah, we keep the show ad-free because of listener support. If you've gotten something out of it, you can throw a few bucks our way at buy me a coffee dot com slash fexingo. It literally helps us keep the lights on. Luna: And it's not expected, but it's appreciated. Okay, back to the 'can't' employee. What about the situation where the employee is actually right — the thing truly can't be done? Lucas: That's a good point. Sometimes they're correct. And if you dismiss them, you lose credibility. So you need to separate 'can't' from 'won't' — is it a genuine technical limitation, or a lack of willingness to try? Luna: How do you tell the difference? Lucas: Ask follow-up questions. 'What have you tried?', 'What would be the first step if we did try?', 'Who else has solved a similar problem?' If they can't answer those, it's likely a 'won't.' But if they have detailed knowledge of why it's impossible — like a specific API limitation or a regulatory constraint — then listen. Luna: So the goal isn't to force them to say yes. It's to get them to engage with the problem differently. Lucas: Exactly. One more thing: after you've addressed the pattern, you should reinforce the new behavior. When Priya started offering alternatives, her manager made a point to publicly acknowledge her creativity in team meetings. That signaled to everyone that problem-solving is valued more than instant feasibility analysis. Luna: Positive reinforcement is underrated. It's easy to only notice the negative pattern and forget to celebrate the shift. Lucas: Yeah, and it doesn't have to be a big deal. Just a simple 'I really liked how you reframed that challenge in today's standup.' That goes a long way. Luna: Alright, so quick recap: validate the constraint, shift to 'how might we', timebox creative solutions, and separate 'can't' from 'won't'. And don't forget to reward the new behavior. Lucas: That's a solid summary. Next time you have a team member who keeps saying it can't be done, try those steps. You might be surprised how often 'can't' turns into 'how.' Luna: Thanks for listening, and we'll see you next Monday.