Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says That Won't Work
Transcript
- Lucas: You present an idea in a team meeting — new process, new tool, new approach — and before you've finished the sentence, one person says, 'That won't work.' Not 'I have concerns,' not 'Here's a potential issue.' Just a flat, definitive 'That won't work.' Luna: And it's not just once. It's their default response. You start to dread hearing their voice in meetings. Lucas: Right. And the tricky part is, they're often smart. They're often the person who catches real problems. But the way they deliver it shuts down the room and demoralizes the team. Luna: So how do you manage someone who's technically valuable but whose default mode is 'no'? Lucas: I want to talk about a framework I've adapted from organizational psychologist Adam Grant's work on what he calls 'disagreeable givers.' These are people who are tough-minded, critical, but ultimately want the team to succeed. The challenge is separating the constructive skepticism from the chronic negativity. Luna: And sometimes it's hard to tell which one you're dealing with. Lucas: Exactly. So let me lay out a concrete approach. There's a three-step process: test the data, challenge the framing, honor the intent. Luna: That's a good structure. Start with step one — test the data. Lucas: When your employee says 'That won't work,' your first move isn't to push back emotionally. It's to ask for evidence. 'What specifically makes you think it won't work? Have you seen a similar initiative fail before?' You're shifting them from a blanket statement to a specific claim that can be evaluated. Luna: And often, when you press for data, you discover they have a legitimate concern — or they don't have much to back it up. Lucas: Right. I worked with a product manager at a mid-sized software company — let's call her Priya. Every new feature proposal she'd say, 'That won't scale. The database can't handle it.' But when her manager asked, 'What's the query volume threshold where it breaks? Can we benchmark it?' Priya didn't have that number. She was making an assumption based on intuition. Luna: So the manager turned an opinion into a testable hypothesis. Lucas: Exactly. And that's step one. Step two is challenging the framing. 'I hear your concern, and I appreciate you surfacing it. But instead of starting with what won't work, can we start with what needs to be true for this to succeed?' You're asking them to flip the frame from 'no' to 'how.' Luna: That's a really powerful reframe. It keeps them engaged in problem-solving rather than problem-stating. Lucas: And it honors their analytical nature. You're not asking them to be a cheerleader. You're asking them to apply their critical thinking to the solution, not just the obstacle. Luna: But I want to push back a little. Isn't it possible that some managers actually create this behavior? If an employee once said 'That won't work' and was right — and the manager rewarded that by not going ahead with a bad idea — then the employee learns that skepticism is the way to get validation. Lucas: That's a really good point. You can accidentally reinforce negativity bias. If every time an employee raises a red flag you stop and say 'good catch,' they'll keep raising flags. The solution isn't to stop listening — it's to broaden what you reward. Luna: So you also reward the employee when they offer a constructive alternative, not just when they shoot something down. Lucas: Exactly. That's step three: honor the intent. After you've tested the data and reframed the conversation, you need to explicitly acknowledge their contribution. 'I appreciate you raising that — it helped us stress-test the idea. Now, what's one thing we could do to address that concern?' Luna: That's a great script. It validates their skepticism while gently pushing them toward solution mode. Lucas: And over time, you're training them to complete the circuit. They learn that 'That won't work' is only the first sentence, not the last. Luna: What about the effect on the rest of the team? If one person is always saying 'that won't work,' it can create a culture where people hesitate to offer creative ideas. Lucas: It absolutely can. And that's why you can't just manage this one-on-one. You also have to model the behavior in meetings. When someone else proposes an idea and the skeptic jumps in, you can say 'I hear that concern — let's put a pin in it and come back after we've explored the potential upside.' Luna: You're literally buying space for optimism. Lucas: Right. And you can also use a norm-setting exercise. At the start of a project, say 'For the next 30 minutes, we're only going to generate possibilities. No critiques yet.' That lets the skeptic know there's a time and place for their input — but not every moment. Luna: Let me share a quick example from a friend of mine who manages a marketing team. She had a senior designer who would shoot down every proposed campaign concept. She finally sat down with him and said, 'I value your eye, but the way you deliver feedback makes people defensive. Can we agree that before you say no, you'll offer at least one alternative?' And it worked — because she framed it as a condition of his role, not a criticism of his character. Lucas: That's a great example. It's a behavioral contract. And it's specific: 'Before you give a critique, give a constructive alternative.' Luna: So the key takeaway is: don't try to change their personality. Change the structure of the interaction. Lucas: Exactly. You're not trying to turn a skeptic into a yes-man. You're trying to channel their skepticism into a productive form. And that starts with you, the manager, being very deliberate about how you respond in the moment. Luna: You know, this topic actually reminds me of something we've been discussing behind the scenes here at Fexingo. We keep the show ad-free because we believe listeners deserve straightforward, practical advice without commercial interruptions. And that's only possible because of listeners who choose to support us. Lucas: Yeah, it's a small gesture that makes a big difference. If you've gotten value from episodes like this one — maybe a framework you've used in a 1:1 or a phrase that changed how you give feedback — consider buying us a coffee. It's at buy me a coffee dot com slash fexingo. Luna: Even a one-time contribution helps us keep the library of 300 shows free and accessible. And we genuinely appreciate every bit of support. Lucas: Alright, back to the skeptic. So we've covered the three-step process and the team-level tactics. But there's one more scenario I want to address: what if the employee's 'That won't work' is actually a sign of burnout or disengagement? Luna: Interesting. So the blanket negativity might be a symptom, not a trait. Lucas: Exactly. If someone who used to be more open suddenly becomes habitually dismissive, that's a red flag. They might be exhausted, feeling undervalued, or coping with changes outside work. In that case, your response isn't a framework — it's a check-in. 'I've noticed you're quick to shut down ideas lately. Is everything okay?' Luna: That's a much more empathetic approach. It's not about managing behavior; it's about understanding the person. Lucas: Right. And you can only do that if you have regular one-on-ones where you talk about more than just project status. If your only interaction with this person is in team meetings, you'll never know the difference between a skeptic and a struggling employee. Luna: So the broader lesson is: be curious about the 'why' behind the 'no.' Lucas: Absolutely. And once you know the why, you can choose the right tool. Data. Reframing. Behavioral contract. Or just empathy. Luna: I think the hardest part for most managers is not taking it personally. When someone shoots down your idea, it's natural to feel defensive. Lucas: It is. And that's why the first step — test the data — is so important. It depersonalizes the exchange. You're no longer defending your idea; you're evaluating a claim together. Luna: That's a good reminder. It's not about winning an argument. It's about making better decisions as a team. Lucas: And that's really the goal. The skeptic might be the person who helps you avoid a costly mistake. Or they might be the person who slows down every initiative. Your job as a manager is to figure out which one you're dealing with, and then help them become the first rather than the second. Luna: Well put. I think we've given listeners a lot to try out in their next one-on-one. Lucas: And I'd love to hear how it goes. You can always reach out to us on the Fexingo Business social channels. Until next Monday, keep those conversations productive.