Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Asks Why
Transcript
- Lucas: So we've covered a lot of tricky employee types on this show — the know-it-all, the micromanager, the one who says 'I already know that'. But there's another personality that can really test a manager's patience, and it's one of the most common: the employee who responds to every request with 'why'. Luna: Oh, I've had a few of those. It's not that they're refusing to do the work — they just need to understand the reasoning first. But when it's every single task, it slows things down. Lucas: Exactly. And the instinct for many managers is to treat it as pushback or insubordination. But I think that misses the real story. The 'why' asker is often your most intellectually engaged team member. The challenge is channeling that curiosity without letting it derail execution. Luna: So how do you tell the difference between someone who's genuinely trying to learn and someone who's just being difficult? Lucas: That's the key question. And the first thing I tell managers is to look at the pattern. Is the person asking 'why' before they've even started, or after they've hit a roadblock? Are they asking about the objective, or about the method? A person who asks 'why are we doing this project at all?' is different from someone who asks 'why are we using this specific tool?' Luna: Right — one is questioning purpose, the other is questioning process. And as a manager, you might need to answer both, but the response is different. Lucas: Let me give you a concrete case. I worked with a senior analyst named Sarah at a mid-size tech firm — about 300 employees. She was brilliant, one of the best data people in the company. But her manager was constantly frustrated because every time she got a new assignment, she'd ask three or four questions before starting. 'Why this dataset? Why this time period? Why this metric?' The manager felt like she was stalling. Luna: I can see why. But if she's that good, maybe the questions were actually improving the work. Lucas: That's exactly what happened. Once the manager started treating Sarah's questions as valuable input rather than resistance, he reframed the conversation. Instead of saying 'just do it', he started saying 'good question — here's the context, and if you see a better approach, let me know.' Sarah ended up catching several flawed assumptions in projects before they wasted time. Luna: So the manager shifted from seeing the 'why' as a threat to seeing it as a quality check. Lucas: Yes. But there's a nuance. You can't have every single task become a debate. So the manager also set a boundary: for routine, low-stakes tasks, Sarah agreed to trust the process and ask her questions during weekly check-ins rather than in the moment. For high-stakes projects, she was encouraged to ask upfront. That's a framework I call the 'curiosity threshold'. Luna: I like that. So you basically tier the questions: is this a 'why' that needs an immediate answer, or can it wait? Lucas: Exactly. And the manager's job is to be clear about which bucket a task falls into. If you're ambiguous, the 'why' asker will default to questioning everything because they don't know what's negotiable. The other technique I recommend is the 'two-why rule'. Luna: Two-why rule — what's that? Lucas: It's simple. When an employee asks 'why', you answer the first question directly and substantively. If they ask a second 'why', you answer that too. But if they go to a third 'why' — especially on a low-stakes item — you pause and say, 'Let me take that as a sign we need a deeper conversation later. For now, let's proceed with what we have, and we can revisit the rationale in our next one-on-one.' Luna: That's a great way to honor their curiosity without derailing the day. And it also trains them to prioritize their own questions. Lucas: Right. The goal isn't to shut down curiosity — it's to create a system where curiosity strengthens the work instead of slowing it. And honestly, some of the best innovations I've seen came from a 'why' asker who wouldn't let go of a question. There's a reason why so many breakthrough ideas start with someone saying 'why do we do it this way?' Luna: That's a good point. And I think for a lot of first-time managers, the instinct is to assert authority by demanding compliance. But that can crush the very thing that makes a 'why' asker valuable. Lucas: Absolutely. If you shut them down consistently, you get one of two outcomes: either they become passive and stop caring, or they leave. And if they're your sharpest person, that's a huge loss. So the better approach is to harness that energy. Luna: I want to go back to something you said earlier — about distinguishing productive skepticism from passive-aggressive blocking. Can you give us more specific signals? Lucas: Sure. Productive skepticism tends to be curious, not accusatory. The language is 'I'm wondering if we've considered X' or 'Help me understand why we chose Y over Z.' Passive-aggressive blocking sounds more like 'Why are we even doing this?' with a tone of resignation, or 'That's never worked before' without offering alternatives. One is opening a door, the other is closing it. Luna: And the response from the manager should be different too. For the productive skeptic, you engage. For the blocker, you might need to address the underlying resistance directly. Lucas: Exactly. And that's where the manager's emotional intelligence comes in. You need to be able to hear the tone, not just the words. I've seen managers misread a genuinely curious question as defiance and damage the relationship. On the flip side, I've seen managers who let a passive-aggressive blocker hide behind 'why' questions for months. Luna: So what's the one concrete thing a manager can do this week if they have a 'why' asker on their team? Lucas: I'd say set up a 15-minute conversation where you explicitly address the dynamic. Say something like: 'I really value your curiosity — it's one of your strengths. And I also want to make sure we're moving efficiently. Let's agree on when it's best to ask questions in the moment versus when to save them for later.' That simple framing — naming the strength and agreeing on the boundary — can transform the relationship. Luna: And it shows the employee you see their intent, not just their behavior. That goes a long way. Lucas: It does. And if you're listening and you've been that manager who gets frustrated by the 'why' questions, I'd invite you to try that conversation. You might be surprised at how much easier things get when you're both on the same page. Luna: Speaking of things that are easier when everyone's on the same page — Lucas, we talk a lot on this show about practical frameworks for tough management moments. And we're able to keep these episodes ad-free and focused on real strategy because of listeners who support the show directly. Lucas: That's right. If this kind of conversation has helped you think through a management challenge — whether it's today's topic or something we covered in a past episode — and you'd like to help keep it going, you can find us at buy me a coffee dot com slash fexingo. No pressure, just a simple way to support the work. Luna: And it genuinely makes a difference. Every bit of support helps us keep producing content that's thoughtful and practical, without any ad breaks. So thank you to anyone who's already chipped in. Lucas: Alright, back to the 'why' asker. One more layer I want to add: how do you handle it when the 'why' comes from a team member during a meeting, especially in front of others? Luna: Oh, that's a tough one. Because it can feel like a challenge to your authority, and it can also slow down the whole group. Lucas: Right. And your instinct might be to deflect or give a short answer to move on. But that can backfire — the person feels dismissed, and other team members may also have the same question. I think the best move is to acknowledge it publicly and then defer. You say, 'That's a great question. I want to give it the attention it deserves, so let's take it offline and I'll follow up with you after the meeting.' That way, you validate the question without letting it hijack the agenda. Luna: And then you actually have to follow up. If you don't, you lose credibility. Lucas: Absolutely. That follow-up is non-negotiable. And when you do, you can have the deeper conversation — which might reveal a legitimate gap in your reasoning that you can address, or it might be a misunderstanding you can clear up. Either way, you've turned a potentially awkward moment into a trust-building one. Luna: I think that's a really important point for first-time managers especially. They often feel like they have to have all the answers in the moment, but it's actually a sign of strength to say 'I need to think about that.' Lucas: Exactly. Confidence isn't about having every answer — it's about being secure enough to say you don't, and then following through. The 'why' asker will respect you more for that than for a quick, shallow answer. Luna: So to recap: don't shut down the 'why', but do set boundaries. Use the curiosity threshold and the two-why rule. And handle public questions by deferring and following up. Lucas: That's the playbook. And if you do it well, you'll likely find that your 'why' asker becomes one of your strongest contributors — because they care enough to question, and you gave them a framework to do it constructively. Luna: And maybe you'll even learn something yourself along the way. Lucas: That's the best part. Alright, that's our time for this episode. Thanks for listening, and we'll see you next Monday.