Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Always Questions Your Decisions
Transcript
- Lucas: So you give a clear, reasonable direction — and your team member says, 'Why are we doing it this way?' Or 'I think we should consider the alternative.' Or even, 'Are you sure that's the right call?' Luna: And it happens in the moment, in front of other people, and you feel your confidence just drain. Lucas: Exactly. It's one of the most common — and most unnerving — scenarios for a new manager. Today we're talking about what to do when an employee constantly questions your decisions. Not the occasional thoughtful challenge — that's healthy. The pattern where you feel like every call gets second-guessed. Luna: Right. There's a difference between a good skeptic and someone who's eroding your authority. Lucas: Let's ground this in a real case. I was talking to a product director at a mid-size SaaS company — about 200 employees, growing fast. She'd just promoted a senior engineer to lead a team of four. Within two weeks, one of the engineers, a guy with deep domain expertise, started questioning every sprint priority. 'Why this feature first? Shouldn't we refactor the database?' Every stand-up, every planning session. Luna: That's a classic. And it's tricky because he's not wrong to ask — but the pattern is the problem. Lucas: Right. The new manager felt paralyzed. She didn't want to squash valid input, but the team was losing time. So she talked to her own boss, who gave her a three-step framework. I've since seen versions of it work across different industries. Step one: assess the intent. Luna: Assess intent — as in, is this about the work or about the manager? Lucas: Exactly. Some employees question because they genuinely see a better path. Others question because they don't fully trust the new manager's judgment — or they're testing boundaries. And a few do it because they wanted the promotion themselves. So step one is to figure out which one you're dealing with. The product director asked her new manager to observe for a week. Note the context: when did he question? In private or public? Was it about big strategic calls or small tactical ones? Luna: And the pattern was? Mostly public, mostly big strategic calls. Lucas: Right. That tilted toward testing authority, not just offering input. So step two: invite co-ownership. The new manager scheduled a one-on-one and said, 'I value your expertise. I want you to help shape the roadmap — but let's do that before the sprint starts, not during stand-up. I'm giving you 30 minutes every Friday to challenge any priority decision from the week ahead. If you convince me, we change course. But once that meeting ends, the sprint plan is locked.' Luna: So she created a dedicated space for his pushback. That's smart — it honors his knowledge but sets a boundary. Lucas: Exactly. The key phrase is 'once that meeting ends, the sprint plan is locked.' That's step three: set a decision boundary. The employee knows where and when his input is welcome, and the manager retains the final call. In this case, the engineer actually brought up good points in those Friday sessions. The manager adopted two of his suggestions over the next month. And the public questioning stopped. Luna: So it worked because she gave him influence without giving up authority. Lucas: Precisely. But this doesn't work for every personality. If the employee is questioning because of a deeper trust issue — maybe they saw a previous manager make bad calls — then you need a different approach. Luna: Like what? Walk us through that. Lucas: If it's trust-based, the questioning comes from fear, not ego. So step one is still assess intent — but you'll notice the tone is more anxious than combative. Then step two becomes transparency: share your reasoning more openly. Say, 'Here's the data I'm looking at. Here's the trade-off I'm making. What am I missing?' That invites collaboration without undermining you. Luna: And step three? Still a decision boundary? Lucas: Yes, but softer. 'I hear your concern. Let's try this for two weeks, then review together.' That way the employee sees you're not rigid, but you're still leading. Luna: What about the scenario where the employee is more senior than the manager? Like someone with 15 years of experience reporting to a first-time manager with four. Lucas: That's one of the hardest. The power dynamic is inverted in terms of experience. The manager has authority on paper, but the senior employee has credibility. In that case, I think the manager should lead with humility — but not weakness. Say, 'I respect your experience enormously. That's exactly why I want you to challenge me — but in the right forum.' Then set that boundary I mentioned. Luna: You're essentially saying the same framework applies, but the tone has to be more deferential. Lucas: Right. The manager has to earn the authority by showing they're not threatened by expertise. But if the employee continues to undermine decisions publicly, then it becomes a performance issue — and the manager has to address it directly. Luna: And by the way, this whole conversation reminds me why we keep this show ad-free. We don't sell your attention to sponsors. And if you find these episodes useful — maybe they've helped you handle a tough conversation — you can support the show at buy me a coffee dot com slash fexingo. Lucas: Yeah, we hear from listeners who say these frameworks save them hours of frustration. That's exactly why we keep it ad-free — listener support lets us focus on the content, not the commercials. Luna: Exactly. Okay, back to the questioning employee. There's another variant — the chronic questioner who doesn't want the stage, they just want reassurance. They ask 'Are you sure?' over and over. Lucas: Yes. That's anxiety, not defiance. The fix is different. For that person, you want to build their confidence in your decision-making by being consistent and explaining your rationale briefly each time. But after a few weeks, you can say, 'I've noticed you ask for reassurance a lot. I trust your judgment. Next time, I'd like you to sit with the decision for five minutes before asking me. If it still doesn't sit right, come talk.' Luna: That's coaching them to self-soothe. I like that. Lucas: So there's no one-size-fits-all. But the common thread is: don't take it personally. The moment you feel defensive, you lose credibility. Stay curious about their intent, give them a structured outlet, and hold the decision boundary. Luna: One more thing — what about the employee who questions in writing? Long emails with lots of cc's? Lucas: That's a different beast. Often it's a power play — they want an audience. I'd move it offline. Reply with, 'Great points. Let's discuss in our one-on-one on Thursday.' And then in that meeting, have the same conversation about appropriate forums. Luna: So the principle is: redirect the energy to a controlled space, and then address the pattern directly. Lucas: Exactly. And if they continue after that, you have a clear conversation about team norms and expectations. Because ultimately, the team needs to feel that the manager can make a call and move forward. Constant questioning — even if well-intentioned — slows everyone down. Luna: Alright, that's a solid playbook. I think the key takeaway is: don't stifle questions, but do shape where and when they happen. Lucas: That's it. And if you've got a specific situation you're dealing with, try the three-step framework this week. Assess intent. Invite co-ownership. Set a decision boundary. Let us know how it goes. Luna: We'll be back with another episode tomorrow. Until then, keep leading.