Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says That Won't Work
Transcript
- Lucas: Luna, I want to talk about the team member who kills every new idea before it's even had a chance to breathe. The person who hears a proposal and their instant reflex is 'that won't work.' Luna: Oh, I know exactly the type. It's exhausting. And it's especially tough for a first-time manager who's trying to build momentum. Lucas: Exactly. I was talking to a friend who manages a team of five at a mid-size SaaS company. They were in sprint planning, and a junior developer suggested a small refactor to reduce technical debt. Before anyone could explore it, the senior dev — very respected, very experienced — says 'that won't work because the database schema is too rigid.' End of discussion. Luna: And that junior developer probably didn't speak up again for the rest of the meeting. Lucas: Exactly. The senior dev wasn't being malicious. He genuinely believed he was saving the team time. But the effect was the same: innovation stalled, and the junior felt shut down. Luna: So what's the root cause here? Is it a personality thing, or is it something deeper? Lucas: Often it's a mix. Some people are naturally risk-averse. But a lot of it comes down to fear of failure or a lack of psychological safety. If the team culture punishes mistakes, the safest move is to preemptively shoot down anything uncertain. Luna: Right. So the manager's job isn't to change their personality — it's to change the environment. Lucas: Exactly. There are three techniques I've seen work well. The first is what I call the 'one positive before one problem' rule. Before anyone can raise an objection, they have to state one thing that could work about the idea. Luna: That forces them to engage constructively first. I've seen that used in design sprints — it works. Lucas: The second technique is to restructure the brainstorming session itself. Instead of open discussion, use a 'yes, and' protocol. For the first ten minutes, no objections allowed — only building on the idea. Then after that, you open the floor to concerns, but framed as risks to mitigate, not reasons to kill the idea. Luna: So you're separating divergent thinking from convergent thinking. That's a classic design-thinking move. Lucas: Exactly. And the third technique is the most powerful: one-on-one coaching to reframe their instinct. You sit down with the person and say, 'I notice you often point out why things won't work. That's valuable, but I want to help you turn that into a superpower.' Luna: How do you actually phrase that without sounding critical? Lucas: You say something like, 'Your experience helps us avoid costly mistakes. But I'd like you to pair each objection with a suggestion for how we could make it work. If you see a problem, also propose a workaround.' That shifts them from critic to problem-solver. Luna: I think the key is acknowledging their value first. Nobody wants to feel like their expertise is being dismissed. Lucas: And you can even use a technique from the world of project management called the 'pre-mortem.' Instead of asking 'will this work?', you ask 'assume it failed spectacularly — what went wrong?' That lets the pessimist shine in a structured way. Luna: That's brilliant because it validates their instinct to look for pitfalls, but channels it into productive foresight. Lucas: And it turns them into the team's risk radar, not the team's wet blanket. I've seen senior devs completely transform when they're given that role. Luna: But what if the person is genuinely toxic? Not just cautious, but actively undermining? Lucas: That's a different conversation. If they're consistently shutting down ideas even after coaching, and it's affecting team morale, you may need to set a clear boundary. Something like, 'In meetings, I need you to support the process. If you have a concern, bring it to me privately afterward.' Luna: So you're not punishing their insight, but you're containing the behavior. Lucas: Exactly. And if they still can't adjust, that might be a performance issue. But in my experience, most people respond well to the reframing if you do it with respect. Lucas: You know, it's funny — this podcast is all about helping managers navigate these tricky dynamics. And we deliberately keep it ad-free because we think this kind of practical advice should be free from commercial interruption. Luna: Yeah, and that's only possible because listeners who find value here sometimes choose to support us directly. Lucas: If that's you, the link is buy me a coffee dot com slash fexingo. It's a small way to keep these episodes coming without any ad breaks. Luna: Right. And speaking of keeping momentum — let's get back to that senior developer. What does the follow-up look like after your one-on-one? Lucas: You need to reinforce the change publicly. In the next meeting, if the person starts to object, you can gently say, 'Hold that thought — first, what's one thing that could work?' Then after they answer, you let them raise the concern. Over time, it becomes a habit. Luna: And you also need to model the behavior yourself. If you, as the manager, shoot down ideas, you lose all credibility. Lucas: Absolutely. I've seen managers say 'that won't work' and then wonder why their team does the same. You have to be the change. Luna: So let's summarize. Three techniques: the one-positive rule, structured brainstorming with separate phases, and coaching to reframe objections as risk analysis. Plus the pre-mortem as a bonus tool. Lucas: That's the toolkit. And one last thing: don't forget to celebrate when they do it right. If the chronic objector offers a constructive suggestion, call it out. Say 'that's exactly the kind of thinking we need.' Positive reinforcement goes a long way. Luna: Because at the end of the day, you're not trying to silence their voice — you're trying to tune it so the whole team can harmonize. Lucas: Exactly. And that's the art of managing a team member who always says 'that won't work.' Thanks for listening, and we'll see you next Monday.