Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage Someone Who Asks Why on Everything
Transcript
- Lucas: You know that team member — the one who responds to every new initiative with a gentle, or not so gentle, 'why?' Luna: Oh, I know exactly who you mean. Sometimes it feels like they're challenging your authority. Sometimes it feels like they're just curious. And sometimes… it's just exhausting. Lucas: Right. And the instinct as a manager is often to shut it down. To say 'because I said so' or 'because leadership decided.' But I think we've all learned that doesn't work. It erodes trust. Luna: So how do you tell the difference between an engaged skeptic and someone who's just resisting change? That's the real question, isn't it? Lucas: It is. And there's actually some good research on this. Google's re:Work team — the people behind Project Aristotle — published a follow-up study in 2023 on something they called 'productive challenge behavior.' They found that teams with high psychological safety saw 27 percent more of it. The key distinction: productive challenge comes from a place of wanting to make the outcome better. Unproductive challenge comes from a place of wanting to stop the outcome entirely. Luna: So the motive matters. That's helpful, but it's also hard to read in real time. You're in a meeting, someone's asking 'why are we doing this?' — you don't have time to run a psychological evaluation. Lucas: Exactly. So I want to walk through a concrete case. A friend of mine — let's call her Priya — was a VP of engineering at a mid-size SaaS company. About 60 engineers. She had this senior engineer, James, who was brilliant. Like, genuinely the most technically sharp person on the team. But he questioned everything. Every sprint goal, every architecture decision, every process change. Luna: The classic 'Why' employee. I bet some of her other managers wanted him gone. Lucas: They did. After about three months, two of her directors came to her and said 'James is a blocker. He's slowing down the team. We need to put him on a performance plan or let him go.' And Priya's first instinct was to push back, because she knew James was talented. But she also knew the frustration was real. Luna: So what did she do? Lucas: She asked to sit in on a few of James's team meetings. She wanted to see the pattern for herself. And she noticed something: James asked 'why' most often when there wasn't a clear decision log — when the context behind a decision was missing. He wasn't asking 'why are you making me do this?' He was asking 'why is this the right technical choice?' And when no one had a good answer, he'd keep pushing. Luna: So it was a context problem. He needed the rationale to buy in. That's actually a sign of engagement, not resistance. Lucas: That's exactly what Priya concluded. She realized the team had been making decisions in leadership meetings and then just broadcasting the outcome. James — and probably others — felt like they were being dictated to, not consulted. So she worked with James's manager to develop what I now call the Three-Beat Protocol. Luna: The Three-Beat Protocol. I love a good framework. What are the beats? Lucas: Beat one: Validate the motive. Before you answer the 'why,' you say something like 'That's a great question — are you asking because you need more context, or because you see a risk we're missing?' That forces the questioner to articulate their intent. And it signals that you're open to being challenged. Luna: That's smart. It also gives you a second to think. And it sets the tone for a collaborative conversation instead of a defensive one. Lucas: Exactly. Beat two: Answer the 'why' directly, with the actual context. Don't just say 'because the client wants it.' Say 'We're doing this because the client's Q3 revenue target depends on this feature, and if we don't deliver, they've signaled they'll explore other vendors. Here's the specific clause in the contract.' Specificity kills resistance. Luna: It also shows you respect the question enough to give a real answer. Which builds trust over time. Lucas: Right. And beat three: Redirect to action. After you've answered, you say 'Given that context, do you see a better way to achieve the same outcome? Or are you comfortable proceeding with this approach?' That's the key. You're not just saying 'stop asking questions.' You're saying 'now that you have the information, help us move forward.' Luna: And if they still resist after that — if they keep asking 'why' even when they have the full context — then you know it's not about information. It's about genuine disagreement or maybe a values conflict. Lucas: Exactly. And that's a different conversation. At that point you might need to say 'I hear your concern, and I respect it. But we've made the call. I need you to execute on this, even if you disagree. Can you do that?' That's the boundary-setting moment. Luna: So the Three-Beat Protocol helps you diagnose. If they respond well to context, you've got an engaged skeptic. If they don't, you've got a deeper issue. Lucas: Exactly. And Priya's team started using this. Within a month, James's 'why' questions became shorter and more targeted. Because he knew he'd get a real answer. And the team started writing decision briefs before rolling out changes — they'd include the context up front. The number of questions actually went down, because the information was already there. Luna: It's like the old saying: you can either give people the reasons, or you can give them the reasons to resist. Lucas: That's good. I'm stealing that. So the takeaway for managers: before you label someone as difficult, ask yourself whether you're giving them enough context. The 'why' employee might be your biggest asset — if you know how to read them. Luna: And if they're not, at least you'll know sooner. Which saves everyone time. Lucas: Right. And that clarity is valuable in itself. Now, speaking of value — you know, we've been doing this show for over 30 episodes, and one thing we've never done is run ads. It's a deliberate choice. We want these conversations to be useful without any commercial interruption. Luna: Yeah, it's something we're proud of. And if you've found this episode — or any episode — helpful in your own management journey, there's a simple way to support that choice. Lucas: It's buy me a coffee dot com slash fexingo. That's it. No tiers, no perks, no gimmicks. Just a way for listeners who find value here to help us keep the show independent and ad-free. Luna: And we really appreciate it. Now, back to the 'why' employee — one more thing I want to touch on. What about the manager who is themselves a 'why' person? The one who questions everything from above? Lucas: Oh, that's a whole other episode. But the short version: the Three-Beat Protocol works in reverse too. If you're the one asking 'why,' make sure you're clear on your own motive before you speak. Are you seeking context, or are you resisting? If you're seeking context, frame it that way. Say 'Help me understand the context so I can better support the decision.' That changes the dynamic completely. Luna: It also makes you look like a leader, not a complainer. There's a fine line between being the thoughtful skeptic and being the person who always has a problem. Lucas: And that line is usually drawn by how you deliver the question. So if you're a 'why' manager, ask yourself: am I asking in a way that invites collaboration, or am I asking in a way that puts people on the defensive? Luna: That's a good mirror to hold up. I think we've all been on both sides of that. Lucas: For sure. So here's what I'd love listeners to take away: next time someone on your team asks 'why,' don't brace for a fight. Assume good intent. Use the Three-Beat Protocol. Validate, answer with context, then redirect. Nine times out of ten, you'll turn friction into alignment. Luna: And the tenth time, you'll have a much clearer picture of the real issue. That's a win either way. Lucas: Absolutely. Thanks for listening, everyone. We'll see you next week.