Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says It's Too Risky
Transcript
- Lucas: I want to talk about a manager I spoke with last week — let's call her Priya. She's a VP of Engineering at a mid-size SaaS company, about seventy engineers. And she has a senior developer, Rahul, who's been with the company six years, knows the codebase cold, and is basically her most reliable person. There's just one thing. Luna: Let me guess — every new idea, he says it's too risky. Lucas: Exactly. Priya sent me a list of the actual phrases he uses. 'That's too risky for production.' 'We shouldn't experiment on the main branch.' 'If this breaks, we lose credibility with our biggest client.' And the thing is — some of his concerns are valid. But over time, it became a reflex. Priya realized that over six months, her team had shelved or delayed at least four initiatives because Rahul's risk veto carried so much weight. Luna: Six months of stalled innovation. And I bet she didn't even notice it at first because he's such a solid performer otherwise. Lucas: Right. That's the trap. When a high-credibility person becomes the de facto risk gatekeeper, you start self-censoring as a manager. You pitch ideas softer, you pre-address his objections before he even makes them. Priya caught herself doing that — she'd literally edit her own proposals before the meeting to avoid his pushback. Luna: That's a huge cost. And it's invisible. You can't put it on a balance sheet. Lucas: So we walked through a three-step framework. First step: rename the objection. Instead of letting Rahul frame it as 'this is too risky,' Priya started asking him to specify the risk in one sentence. Not 'it's risky' — 'the specific risk is X, and its probability is Y.' That forced him to move from a blanket veto to a testable claim. Luna: That's good. It shifts the conversation from emotion to analysis. And it also reveals whether he's actually thought it through or just defaulting to caution. Lucas: Exactly. Second step: create a low-stakes sandbox. Priya proposed a two-week spike — a separate branch, no production impact, just proof of concept. Rahul could still voice concerns, but they'd be tested in a contained environment. She told him, 'If it fails, we learn something. If it works, we scale. Either way, we're smarter in two weeks than we are today.' Luna: That's a nice reframe. It takes the pressure off being right and puts it on learning. Did Rahul go for it? Lucas: Hesitantly. But he agreed to one spike. And here's the interesting part — the spike actually exposed a real edge case that the team hadn't considered. Rahul's caution turned out to be useful, just not at the veto stage. Priya told me that was a turning point. She started framing his risk aversion as a superpower, but one that needed to be deployed at the right moment — during testing, not during ideation. Luna: I love that. So she flipped his role from blocker to quality assurance. That's a much more productive position for him — and for the team. Lucas: Right. And the third step was the hardest: reframing failure as insurance. Priya realized that Rahul's risk aversion was partly rooted in a project from three years ago — a major refactor that went badly, cost the company a big client, and left scars. So she had to acknowledge that history without letting it dictate the future. She told him, 'That project failed because we didn't have the right safeguards. Now we do. The cost of not trying something new is actually higher than the cost of a failed experiment.' Luna: That's a really honest conversation. And it gets at something I think a lot of managers miss — risk aversion is often a trauma response, not a personality flaw. Lucas: Absolutely. There's actually research on this — a 2022 study in the Journal of Organizational Behavior found that employees who had experienced a high-visibility failure were 40 percent more likely to exhibit risk-averse behavior in subsequent projects, even when the context was completely different. So Priya wasn't just managing Rahul's personality; she was managing his professional history. Luna: That's a powerful lens. So the solution isn't to convince him to be more optimistic — it's to build a structure where his caution is useful but not paralyzing. Lucas: Exactly. And look, I think there's a broader lesson here for any manager dealing with a chronic 'it's too risky' team member. The cost of accepting that veto without challenge is real. Priya told me that after three months of using this framework, her team had launched two of the four shelved initiatives. One of them — a new feature for their biggest client — ended up increasing retention by 12 percent. Luna: Twelve percent retention improvement from something that almost got killed by risk aversion. That's a concrete number. Lucas: It is. And it underscores something Priya said that stuck with me. She said, 'I used to think my job was to protect the team from bad ideas. Now I think it's to protect the team from not having ideas at all.' Luna: That's a great line. And it reminds me — and this is a bit of a side thought — but this kind of work takes time and energy. And honestly, a lot of the frameworks we talk about on this show come from conversations with real managers like Priya, and from research we dig into. It's something we're able to do because this show is listener-supported, not ad-driven. Lucas: Yeah, that's right. A small but meaningful group of listeners chips in monthly at buy me a coffee dot com slash fexingo, and that's what finances this whole operation — no sponsors, no commercials, just the freedom to go deep on whatever management challenge is actually showing up in people's inboxes. Luna: And we're grateful for that. It means we can spend time on stories like Priya's instead of rushing to fit a sponsor break. So if you've gotten something useful out of these episodes, that's the way to keep it going. No pressure at all — just wanted to name it. Lucas: Exactly. Anyway, back to Priya — she also told me about a second developer on her team, someone more junior, who started mimicking Rahul's caution. That was her wake-up call. Because risk aversion is contagious. If the most senior person says 'too risky' enough times, the whole team starts self-censoring. Luna: That's a really important point. The behavior spreads. And it becomes cultural. So if you're a manager and you've got one person who's the designated 'no' voice, you're not just losing their ideas — you're losing everyone else's too. Lucas: Right. Priya started doing something else after the framework took hold. She'd open brainstorming sessions with a norm: 'For the first ten minutes, no risk talk. Just ideas. We'll stress-test them later.' That simple rule changed the energy completely. The junior developers started contributing more, and Rahul's input became more targeted and useful. Luna: So she essentially created a psychological safety zone for ideation, then a separate zone for risk analysis. That's a really smart structural fix. Lucas: It is. And it's replicable. If you're a first-time manager listening, you can try this tomorrow. Pick one recurring objection from your most cautious team member. Next time you hear 'that's too risky,' ask them to name the specific risk and its probability. Then propose a contained experiment. And if they still resist, acknowledge the past failure that might be driving it, but reframe the cost of inaction. Luna: I think the reframing part is the hardest because it requires empathy. You have to understand where the fear comes from, not just argue against it. Lucas: Yeah. And that takes time. But the payoff — like Priya's twelve percent retention improvement — is real. The alternative is letting risk aversion quietly shape your roadmap, which is a decision you're making by default. Luna: So the key takeaway: don't let 'it's too risky' be the last word. Turn it into a question, create a sandbox, and honor the fear without letting it run the show. Lucas: Exactly. And if you have your own story of managing a risk-averse team member, we'd love to hear it. You can reach us on the show's page. For now, thanks for listening — and as always, keep building your team's capacity for smart experimentation.