Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Asks for Permission
Transcript
- Lucas: So you've got a senior analyst named Priya on your team. She's smart, diligent, has been with the company for eighteen months. But every time she needs to do something even slightly outside her routine — like email a client about a new scheduling slot — she sends you a note saying, 'Can I go ahead and do this?' Luna: Right. And at first you think, 'Oh, she's being thorough.' But after a while it becomes exhausting. You're answering questions she already knows the answer to. Lucas: Exactly. This is what I call the Permission Seeker pattern. It's different from the person who genuinely doesn't know what to do. Permission seekers are capable — they just habitually defer the decision to you. And if you're a new manager especially, it's easy to fall into the trap of just answering them because it feels faster than coaching them through it. Luna: So how do you break the cycle without making them feel like you're annoyed or that you don't want to help? Lucas: Great question. I think the first step is to recognize that this is a coaching problem, not a competence problem. Priya doesn't lack skill. She lacks a framework for when she can act without approval. So you need to give her that framework. Luna: And how do you do that concretely? Are we talking about a one-time conversation, or an ongoing process? Lucas: It's a three-session coaching arc. I call it the permission to use judgment Reset. Session one, you sit down with Priya and you explicitly tell her: 'I trust your judgment. The reason I hired you is because you have good instincts. From now on, I want you to assume you have the green light for anything that fits within these clear boundaries.' And then you define the boundaries. Luna: What boundaries are we talking about? Lucas: I suggest a simple traffic-light system. Red light — decisions that affect budget over a certain threshold, or that could create legal or reputational risk. Those still come to you. Yellow light — decisions that are new but low risk, like a new scheduling slot. Priya should go ahead but copy you on the email. Green light — routine decisions she can own entirely. Luna: I like that. It gives her a concrete way to categorize things. But what about the second session? Lucas: Session two is about the 70-Percent Rule. This comes from a concept in military decision-making and also from author Liz Wiseman's work on multipliers. The idea is: if you have 70 percent of the information and 70 percent confidence in your decision, you should go ahead. Waiting for 100 percent clarity is a recipe for paralysis. So you coach Priya to ask herself, 'Do I have at least 70 percent of what I need?' If yes, she acts. If no, she comes to you with a specific question about the missing piece. Luna: That reframes the dynamic. Instead of 'Can I do this?' it becomes 'Here's what I'm planning to do based on the 70 percent I have.' That's more empowering. Lucas: Exactly. And session three is a post-decision debrief. After Priya has made a few calls on her own, you check in. You ask, 'How did that decision feel? What did you learn? Is there anything you'd do differently next time?' That reinforces the behavior and builds her confidence. Luna: I think one concern managers have is: what if they mess up? What if Priya makes a call that costs the company time or money? Lucas: That's the risk. But the cost of never letting them try is actually higher. If you keep answering every question, you become the bottleneck. Your team never develops judgment, and you never get to focus on higher-level work. Plus, if you've defined the red-light boundaries clearly, the mistakes will be small and recoverable. Luna: Let me push back a little. Does this work the same way in a remote or hybrid environment? Because when you're not in the same room, it's easier for a manager to default to approving things in Slack just to keep things moving. Lucas: It's actually even more important in remote settings. Because the friction of asking permission is lower — you just type a quick message — it can become a crutch. I'd recommend the same framework, but with a twist: create a shared decision-log document. Each time Priya makes a yellow-light decision, she adds a one-line entry: date, decision, outcome. You can scan it weekly instead of having to approve each one. Luna: That's smart. It builds accountability without micromanagement. And it gives you data to coach from. Lucas: Right. And one more thing: be explicit about the permission shift. Say, 'I'm changing my expectation. In the past, you asked permission for X, Y, Z. Going forward, I want you to assume approval unless it's on the red list.' That clarity prevents confusion. Luna: I want to tie this back to something you mentioned earlier — Liz Wiseman's multipliers. Can you briefly explain the multiplier concept for listeners who don't know it? Lucas: Sure. Liz Wiseman wrote a book called 'Multipliers: How the Best Leaders Make Everyone Smarter.' In her research, she found that some leaders are 'diminishers' — they drain intelligence and capability from their teams by always having to be the smartest person in the room or by micromanaging. And others are 'multipliers' — they amplify the intelligence and capability of their people. The Permission Seeker pattern is often a direct result of a diminisher manager. But even if you're not a diminisher, you can accidentally create that culture by being too available to answer every question. Luna: So the coaching arc we just described is really a way to shift from being a diminisher to being a multiplier, even if you didn't realize you were falling into that trap. Lucas: Exactly. And the best part is, once you do this with one person, word spreads. Other team members see Priya making decisions, and they start to ask themselves, 'Why am I still asking for permission on this?' It creates a culture shift. Luna: That reminds me of something I read in a Harvard Business Review article about decision rights. They found that clarifying decision rights — who decides what — can boost team speed by up to 30 percent. Because you eliminate the back and forth of asking and waiting. Lucas: Yeah, and that's the same principle. When you formalize it, you cut out the latency. And that 30 percent speed increase is huge, especially in fast-moving teams. Lucas: You know, this topic is exactly why we do Manager Mondays — to help you navigate these real, everyday challenges that don't get covered in leadership training. If you've found these episodes useful, there's a simple way to keep them going: buy me a coffee dot com slash fexingo. A few dollars a month genuinely makes a difference in keeping the show ad-free and focused on what matters. Luna: Absolutely. We hear from listeners all the time who say a single episode helped them handle a tough conversation. That feedback is what keeps us going, and listener support ensures we can keep doing it. Lucas: So, back to the coaching arc. One more practical tip I want to share: after you've done the three sessions, give Priya a one-page decision matrix. It has three columns: decision type, decision category, and examples. She can pin it to her desk or save it in her notes. That way, she has a reference point whenever she's unsure. Luna: That's concrete and helpful. I also think it's worth mentioning that this approach works for new employees too, not just existing ones who've developed the permission-seeking habit. You can set this expectation from day one. Lucas: Great point. Onboarding is the perfect time to say, 'Here's how we think about decisions on this team. Here's what you own from the start.' It prevents the permission-seeking pattern before it starts. Luna: So to wrap this episode: if you have a Priya on your team, don't get frustrated. Instead, see it as an opportunity to be a multiplier. Give her a framework, coach her through it, and watch her autonomy grow. Lucas: And if you're the Priya — if you find yourself always asking your manager before you act — try using the 70-Percent Rule yourself. Chances are, you already know the answer. Trust that.