Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Have a Better Idea
Transcript
- Lucas: So you've laid out a plan in a team meeting, you feel good about it, and then from the corner of the room, you hear it: 'Actually, I have a better idea.' Luna: Oh, that phrase. It can land so differently depending on who says it and how. Lucas: Exactly. Today we're talking about the employee who always says 'I have a better idea.' Not the occasional brainstormer — the person for whom it's almost a reflex. The one who can't let a single proposal pass without offering an alternative. Luna: Is this always a problem? I mean, sometimes they do have a better idea. Lucas: Sure, sometimes they do. And that's what makes it tricky. If you shut them down, you might kill a genuinely good suggestion. But if you always let them run with it, you lose momentum, and other team members start to feel like their input doesn't matter. Luna: There's a power dynamic too. If the person is junior, it can feel refreshing. If it's a senior person, it might feel like they're trying to run the show. Lucas: Right. I want to anchor this in a specific case. I was talking to a VP of Engineering at a mid-sized software company — about 200 people. She had a senior engineer, very talented, who would do this constantly. In every sprint planning meeting, he'd challenge the product manager's priorities. In every architecture review, he'd propose a completely different approach. And on one level, some of his ideas were good. But the cost was that the team never committed to a direction. They'd spin for weeks. Luna: So the VP's instinct might be to say, 'Look, I appreciate the input, but we're going with my plan.' But that doesn't solve the underlying pattern. Lucas: Exactly. She tried that. And what happened? The engineer started going around her — talking to other teams, escalating to her boss, sending long emails after meetings. He wasn't malicious; he genuinely believed his ideas were better. But he was eroding her authority and creating confusion. Luna: So what did she do? Lucas: She shifted her approach. Instead of treating his suggestions as interruptions, she created a structured channel for them. She told him: 'I value your ideas. In our one-on-ones, I want you to bring me your top three alternatives to whatever we're working on. We'll evaluate them together. But in team meetings, when we've already made a decision, I need you to support it publicly.' Luna: That's interesting — she's not saying 'don't have ideas,' she's saying 'here's when and where to share them.' Lucas: Exactly. It's about time and place. The engineer agreed, and within a few weeks, the dynamic shifted. He felt heard, and the team meetings stopped being derailed. But it wasn't a perfect fix. The engineer still struggled with decisions he disagreed with. Luna: So what's the deeper skill for a manager here? How do you distinguish between someone who's genuinely innovating and someone who's just resistant? Lucas: There's a framework from organizational psychologist Chris Argyris called the Ladder of Inference. It's about how we move from data to action. People who always have a 'better idea' are often jumping from a single piece of data to a conclusion without sharing their reasoning. As a manager, you can ask them to walk you up their ladder: 'What data are you seeing that I'm missing? What assumption are you making?' Luna: So you're not just accepting the idea or rejecting it — you're forcing them to articulate their reasoning. Lucas: Right. And often, when they do, you find that they're operating on a different set of assumptions. Maybe they're prioritizing speed over quality, or they're worried about a risk you hadn't considered. That's productive friction. Luna: But what about the manager who feels threatened? If you're a first-time manager, having a senior team member constantly challenge you can be really destabilizing. Lucas: Absolutely. And the temptation is to clamp down hard — 'I'm the manager, we do it my way.' That usually backfires. It creates resentment and can drive the employee to leave or become passive-aggressive. Instead, you want to establish what I call 'decision rights.' Clearly communicate: 'On this type of decision, you have input but I have the final say. On that type, you have authority.' Luna: So you're not fighting about every single idea — you're defining the arena upfront. Lucas: Exactly. For example, in the engineering team, the VP defined that architectural decisions within the sprint were the tech lead's call, but the overall roadmap was hers. That gave the engineer autonomy in his domain, while preserving her authority in the broader strategy. Luna: What about the employee who always says 'I have a better idea' but never actually wants to implement it? The ideas just keep coming, but they don't follow through. Lucas: That's a different pattern. That's often someone who enjoys the intellectual exercise but doesn't want the responsibility of execution. In that case, you can say: 'Great idea. I'd love for you to lead a pilot. Can you put together a proposal with timelines and resources by Friday?' That usually filters out the talkers from the doers. Luna: So you're putting the onus on them to prove the idea has legs. That also respects their intelligence — you're not dismissing them, you're taking them seriously. Lucas: Right. And if they come back with a solid proposal, then maybe it is a better idea. You've just turned a potential disruption into a real contribution. And if they don't follow through, you've got a data point that their ideas might not be as actionable as they think. Luna: I think the hardest part for managers is managing their own ego. When someone says 'I have a better idea,' it can feel like a personal attack. Especially if you put a lot of thought into your plan. Lucas: That's so true. And the research backs it up — we have a cognitive bias called the 'not invented here' syndrome. We naturally favor our own ideas. So when someone challenges us, our first instinct is to defend. But as a manager, your job is to find the best idea, not protect your own. That doesn't mean you cave every time — it means you evaluate the idea on its merits, not its source. Luna: So how do you do that in the moment? Like, someone says 'I have a better idea' in a meeting. What's the script? Lucas: I like a simple three-step response. First, acknowledge: 'I hear you, and I appreciate you thinking about this.' Second, inquire: 'Help me understand what you're seeing that I might be missing.' Third, defer: 'Let's note this and evaluate it offline so we can keep the meeting on track.' Luna: That third step is crucial. Because if you get into a debate in the meeting, everyone else checks out. You've got to protect the group's time. Lucas: Exactly. And then you follow up in the one-on-one. That's where you can really dig into the idea. And if it's good, you implement it — and you give them credit. That builds trust. Luna: But what if the idea is bad? Or impractical? How do you say no without demotivating them? Lucas: You explain your reasoning clearly. 'Here's why I'm not going with that — the timeline is too tight, or the cost is too high, or it conflicts with another priority.' And you tie it back to a shared goal. 'I know we both want to ship this feature on time, and this approach would push us past our deadline.' Luna: So you're not saying 'your idea is bad,' you're saying 'it doesn't fit our constraints.' That's a big difference. Lucas: Exactly. And if the employee keeps pushing, you can say, 'I've made my decision. I need you to support it even if you disagree. Can you do that?' That's a direct ask for commitment. Most people, if they respect you, will say yes. Luna: I want to go back to the VP of Engineering story. Did the engineer eventually stop? Lucas: He didn't stop entirely, but it became manageable. He still brought ideas, but in the right forum. And over time, some of his ideas actually improved the product. The VP learned to see him as a strategic asset, not a disruption. And he learned to trust that his voice mattered, so he didn't need to fight every battle. Luna: That's the ideal outcome. But it takes work on both sides. Lucas: It does. And I think that's the takeaway for managers today: don't try to eliminate the 'I have a better idea' impulse. Channel it. Create structures for it. And protect your team's time and focus. Luna: You know, it reminds me of something you said in a previous episode — that managing is not about having all the answers, it's about creating the conditions for the best answers to emerge. Lucas: Yeah, that's exactly it. And speaking of creating conditions — if you've found value in these conversations, we want to keep them coming. A couple of dollars a month genuinely helps us stay ad-free and focused on what matters. You can support the show at buy me a coffee dot com slash fexingo. Luna: It's a small thing that makes a real difference. We appreciate everyone who chips in. Lucas: Anyway, back to the topic. One more thing I want to mention: the 'better idea' employee often has a lot of energy and creativity. If you can redirect that energy, you've got a powerful contributor. But if you shut them down completely, you might lose them — or worse, they'll take their ideas to a competitor. Luna: So the manager's job is to be a conduit, not a dam. Lucas: I love that. A conduit, not a dam. That's going on my whiteboard. Thanks, Luna. Luna: Thanks, Lucas. See you next week.