Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says It Can't Be Done
Transcript
- Lucas: So there's a scene from the first season of 'The Bear' that I think about a lot in management contexts — it's when Sydney pitches a new menu system and Richie immediately says 'it's never gonna work, this ain't that kind of place.' Five seconds, zero curiosity. Luna: Oh, that is so painful — and so familiar. Every team has a Richie. Lucas: Right. And the instinct as a manager is to label that person 'negative' or 'resistant' and start managing around them. But I want to argue that the reflexive 'it can't be done' person is often one of your most valuable assets — if you know how to redirect them. Luna: I love that framing. 'Asset' feels almost provocative. How do you get there? Lucas: Let me anchor this in a real case. I was talking to a director of operations at a mid-size logistics company — about 400 employees, regional trucking and warehousing. She had a senior analyst named Jenna. Jenna had been there twelve years, knew every process inside out, and was genuinely beloved for her institutional knowledge. Luna: But she was also the person who killed every new idea in under thirty seconds. Lucas: Exactly. The director told me 'every time a junior person pitches something, Jenna sighs and lists five reasons it's impossible.' And to be fair, Jenna was often right about the obstacles — but the way she delivered it shut down innovation. The director's first impulse was to tell Jenna to 'be more positive,' which predictably backfired. Luna: Because Jenna didn't see herself as negative. She saw herself as the person who prevented the team from wasting time on doomed projects. Lucas: Bingo. So the director tried something different. Instead of trying to change Jenna's personality, she gave Jenna a new role within the conversation. She called it a 'Constraint Audit.' The next time a junior analyst pitched a new routing optimization tool, the director said 'Jenna, I want you to lead the constraint audit on this. Your job is not to kill it — your job is to tell us exactly what would have to be true for this to work.' Luna: So she flipped the framing. Instead of 'here's why we can't,' it became 'here's what would need to change.' Lucas: That's the whole trick. Jenna still got to surface all the obstacles — the legacy software integration, the driver training time, the weekend disruption — but now she was doing it as a problem-solver, not a gatekeeper. And the junior analyst got to hear the real trade-offs instead of just a wall of 'no.' Luna: And what happened? Did Jenna embrace the role? Lucas: It took about three cycles. The first time, she slipped back into 'see, I told you it wouldn't work.' But the director held the frame: 'Okay, Jenna, but you said if we could solve the weekend disruption, it might be viable. So let's talk about that.' Slowly, Jenna started leading with 'the constraint here is X' instead of 'this is impossible.' The director told me within two months, Jenna was voluntarily saying 'here's a constraint I spotted, and here's one potential workaround.' Luna: That is such a subtle shift — but it changes how the whole team perceives her. She goes from the person who blocks progress to the person who makes progress possible by naming the real risks. Lucas: Right. And I think there's a deeper principle here. The 'it can't be done' person usually has a legitimate fear — that the team will waste time, that they'll be blamed when the new thing fails, or that their hard-won expertise will be ignored. The Constraint Audit honors their expertise while redirecting their energy. Luna: So what are the actual steps a manager can take on Monday? Let's make this tactical. Lucas: Step one: one-on-one conversation — but not about attitude. Say 'I notice you're really good at spotting obstacles. I want to leverage that more systematically. From now on, when someone pitches something new, I want you to lead the risk assessment. Your job is to help us see the full landscape, not just the green lights.' Luna: You're giving them a title — 'risk assessment lead' — that feels elevated. Lucas: Exactly. Step two: in the meeting itself, structure the conversation. After the pitch, you say 'Jenna, can you walk us through the constraints you see — and for each one, what would need to change to make it feasible?' That second clause is critical. Without it, you just get a laundry list of problems. Luna: So you're forcing the problem-solver frame right inside their response. Lucas: Yes. And step three: follow up publicly. After the meeting, you say 'Jenna flagged three real constraints. We're going to explore two of them — the weekend disruption is the toughest, but Jenna's going to work with the IT team on a mitigation plan.' Now she's accountable for solving part of it. Luna: And if she resists that accountability? Like, 'I don't want to work with IT, I just told you it wouldn't work.' Lucas: Then you get to have a harder conversation. 'Jenna, part of being the person who identifies risks is also helping us navigate them. If you're not willing to do that, we'll need someone else in that role.' But honestly, in most cases, people accept the new identity because it's more prestigious — they're the expert, not the cynic. Luna: I also wonder about the timing. If the person has a pattern of shooting things down in front of junior team members, the damage is already done in the moment. Do you ever pull them aside mid-meeting? Lucas: I'd avoid that if possible, because it humiliates them. Instead, I'd do what the director did — she pre-briefed Jenna before the meeting. 'Hey, the junior analyst is going to present a new routing tool. I want you to listen fully, take notes on constraints, and then we'll do the Constraint Audit.' That way Jenna knows her role beforehand and doesn't feel the need to assert it defensively. Luna: Pre-briefing. That's a really good tactic. It turns the meeting into a performance where everyone knows their part. Lucas: And it reduces the anxiety that drives the reflexive 'no.' A lot of these people have been burned before — they've seen bright ideas fail and take the team down with them. The Constraint Audit gives them a channel to voice that fear productively. Luna: So the goal isn't to make them optimistic. It's to make their skepticism useful. Lucas: Exactly. You're not trying to change who they are. You're changing how they participate. Luna: That's a really clean framework. And I think the beauty of it is that it works for any level of employee — from a senior analyst to a VP. The identity shift is the same. Lucas: Totally. And let me give you a quick language tip. When you're in that one-on-one, avoid the word 'negative.' Don't say 'you're being too negative.' Instead say 'I want to make sure your expertise lands in a way that helps the team move forward.' That's a coaching conversation, not a reprimand. Luna: And if the person is the kind who says 'I'm just being realistic'? I feel like that's the most common defense. Lucas: I'd say 'I agree — realism is valuable. And the most realistic person on the team should also be the one who helps us figure out how to work around the obstacles. That's what I'm asking you to do.' You're validating their self-image while expanding it. Luna: One more question — what if the person's negativity is actually corrosive? Like, they're not just skeptical, they're actively undermining morale? Lucas: Then the Constraint Audit won't fix it, because the issue isn't role identity — it's something deeper. Maybe they're burned out, maybe they feel overlooked, maybe they're insecure. At that point, you need to address the behavior directly: 'When you say this won't work in front of the team, it stops others from contributing. I need you to bring those concerns to me privately, or frame them constructively in meetings.' That's a performance issue, not a coaching opportunity. Luna: Fair. So the Constraint Audit is for the person who's fundamentally good but expressing their value in a destructive way. Lucas: Exactly. And honestly, that's most of them. Very few people set out to be the team cynic. They just fall into that role because it's rewarded in some way — maybe their manager has historically listened to them only when they raise alarms. Luna: Which is a fascinating point: the manager may have trained them to be that person. Lucas: A hundred percent. If every time Jenna said 'this will break the system,' the director paid attention — but when Jenna stayed quiet, she got ignored — then Jenna learned that negativity gets airtime. The Constraint Audit re-trains the reward loop: now she gets attention for identifying constraints AND for proposing paths forward. Luna: So the manager has to change their own behavior too. That's humbling. Lucas: It is. But that's the job. You can't ask your team to change if you're not willing to change the signals you send. Luna: I want to circle back to something you said earlier — about the director giving Jenna a new title within the conversation. That reminded me of something we've talked about before, which is how much of management is really just storytelling. You're giving someone a new story about who they are. Lucas: That's exactly right. And the story has to be true — Jenna really does have unmatched knowledge of constraints. The manager isn't making up a role. She's repurposing an existing strength. That's why it works. Luna: Speaking of things that work — we've been doing this show for almost fifty episodes now, and one thing we hear a lot from listeners is that the tactical advice, like the Constraint Audit, is exactly what they need. And we're able to keep delivering that because we don't run ads. We deliberately keep the show ad-free so we can focus on substance. If you find value in that approach, you can support us at buy me a coffee dot com slash fexingo. It's a simple way to keep this going without any commercials. Lucas: Yeah, and we appreciate every bit of support. It lets us spend time on cases like Jenna's instead of trying to sell you something. So thank you. Luna: Alright, back to the toolkit. One last tactical question: how long does this usually take before you see a shift? Lucas: I'd budget four to six weeks of consistent framing. The first two weeks, the person will probably revert to old patterns in the moment. You have to gently redirect each time. By week four, you should hear them self-correcting — 'okay, let me list constraints and then options.' By week six, it's a habit. The key is consistency. If you only do it in every other meeting, they'll revert. Luna: And if it doesn't work by week six? Lucas: Then you have a deeper conversation about fit. But in my experience, it works more often than not — because people want to be seen as valuable. The Constraint Audit gives them a way to be valuable without being a roadblock. Luna: I like that as a closing thought. It's generous, but it's also honest about the limits. Lucas: That's the sweet spot for management, I think. Assume good intent, give a clear path, and hold the standard. Most people will meet you there.