Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Keeps Asking for Permission
Transcript
- Lucas: Luna, I want to start today with a number. A 2019 Google study on high-performing teams found that in the most effective squads, members spent roughly seventy percent less time seeking approval from their manager than in lower-performing teams. Luna: Seventy percent less. That is a staggering gap. It suggests who you have on your team is less important than how they interact with you. Lucas: Exactly. And it gets at a pain point I hear from first-time managers all the time: 'My employee keeps asking for permission on things they should just own.' They feel like a bottleneck, and the employee feels untrusted. It is a lose-lose. Luna: I have been on the receiving end of that as a team member. It is demoralizing when you know you could make the call, but you are trained to check first. Lucas: Right. So today, let us talk about a specific playbook for shifting from 'ask permission' to 'test and report' in about two weeks. And if you are listening and this episode helps you think through a tricky management situation, just know that the show stays ad-free because of listener support – people who grab a coffee at buy me a coffee dot com slash fexingo. It is a small gesture that keeps these conversations going. Luna: Yeah, we really appreciate that. It lets us keep the focus purely on the content. Lucas: Alright. So the framework I have used – and that I taught to a thirty-person engineering team at a mid-sized SaaS company – has four steps. First, you define the boundaries. Second, you set a default forward rule. Third, you coach the employee on what to report after they act. Fourth, you reinforce with a short feedback loop. Luna: Walk me through step one. What do the boundaries look like? Lucas: You sit down with the employee and explicitly list the decisions they are already qualified to make. I would say something like: 'You have final say on anything under five thousand dollars in client spend, on the tech stack for your sub-projects, and on scheduling your team's stand-ups. For anything outside those, come to me.' That clarity removes the ambiguity that drives permission-seeking. Luna: So you are creating a decision rights map. That makes sense, but what if the employee still asks about something inside the boundary? Like they know they can decide, but they check anyway? Lucas: That is where the 'default forward' rule comes in. You tell them: 'If this falls inside your boundary, assume you have my support unless you hear otherwise within two hours. Send me a one-line email with your intended decision, and if I do not object, proceed.' That shifts the burden of proof from 'wait for approval' to 'act and inform.' Luna: That is clever because it leverages inertia. People are more likely to move forward if they are not waiting for a reply. Lucas: Exactly. And the two-hour window gives them a clear trigger: if you do not hear back, you go. Now step three: after they act, they need to report what happened. Not for approval – for learning. So they send a brief note: 'I decided X, the result was Y, here is what I would do differently next time.' That builds their confidence and your trust. Luna: And step four, the feedback loop – that is where you confirm they are on track, right? Lucas: Right. In your weekly one-on-one, you spend five minutes reviewing their decisions from the past week. You reinforce the ones that worked, and you quietly course-correct the ones that did not. Over two weeks, that repetition rewires the dynamic. Luna: I can see this working for mid-level contributors. But what about junior hires? If they do not have the context to know when a decision is safe, the boundaries need to be drawn much tighter. Luna: And if you set the boundaries too wide, you risk them making a costly mistake. So is there a triage system for who gets the full framework? Lucas: Good question. My rule of thumb is: if the employee has been in role at least three months and has demonstrated solid judgment in at least ten low-stakes decisions, they are ready for the test and report model. If they are newer or less proven, you start with a narrower boundary and expand it weekly. Luna: So you basically give them a ladder – small wins first, then bigger autonomy. That feels sustainable. Lucas: Exactly. And the key is that you are transparent about the ladder. You say: 'This month, you own decisions up to this level. Next month, we will add these two categories.' That way, the permission-seeking is replaced by a growth plan. Luna: What about the manager who is the bottleneck? I mean, what if the manager is the one who cannot let go? I have seen leaders who say they want empowerment but then micromanage anyway. Lucas: That is a real problem. And it often stems from the manager's own anxiety about being blamed for mistakes. In that case, the manager needs to do their own work – creating a 'mistake budget' for the team. You say: 'We have capacity for up to three decision errors per quarter without escalation. Use them to learn.' That gives the manager permission to let go. Luna: A mistake budget. I love that. It takes the fear out of delegating. Have you seen teams that successfully implemented this? Lucas: Yes. At that SaaS company I mentioned, the engineering lead set a mistake budget of five decisions per quarter. In the first quarter, they used all five – mostly small overspending on cloud services. But by the second quarter, the team was making better calls, and the manager's involvement dropped by sixty percent. Luna: So the framework works, but it requires intentionality from both sides. One last thing: how do you handle the employee who keeps asking because they are afraid of being wrong? Lucas: That is often a confidence issue, not a competence issue. You can pair the test and report rule with a simple reframe: 'I care more about you making a decision and learning from it than you making the perfect call. A wrong decision that we catch fast is better than a delayed decision.' Luna: That is a nice mantra. And it gives the employee psychological safety to act. Lucas: Exactly. And that psychological safety is what the Google study was really measuring. When people feel safe to decide, they decide faster, and the whole team accelerates. Luna: So for our listeners who are managers: if you have a team member who constantly asks for permission, the first step is to look in the mirror – have you created an environment where they feel safe to act? Then use the four-step framework to shift the balance. Lucas: And remember, the goal is not to eliminate all questions. Some decisions genuinely need a quick approval loop – especially if they involve significant risk or cross-functional alignment. The goal is to shrink the grey area. Luna: Right. And to help your team grow into their own authority. That is the real win. Lucas: Exactly. On that note, I think we have a solid playbook for the week. If you try the default forward rule, drop us a note – we would love to hear how it goes. Luna: And if you found this episode useful, you know where to find us. Thanks for listening, and see you next time.