Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / When Your Employee Keeps Saying I Need More Autonomy
Transcript
- Lucas: So Luna, I keep running into this phrase in my feed, and I'm sure you've heard it too: 'I need more autonomy.' It's become the new 'I need a raise' — every manager's inbox has one of those emails. Luna: Oh yeah, I've seen it. And the tricky part is, sometimes it's a legitimate ask, and sometimes it's a cover for something else entirely. Lucas: Right. And that's why this episode is not about whether to give autonomy or not. It's about diagnosing what's actually behind the request. And to make that concrete, I've been following the story of a product designer at a mid-sized tech company — we'll call her Maya. Maya's been at the company for about eighteen months, performance reviews are strong, and she recently told her manager, 'I need more autonomy.' Luna: And what did the manager do? Did they hand over a project and hope for the best? Lucas: Initially, yeah. The manager gave her full ownership of a new onboarding flow. But within two weeks, Maya was back in the manager's office asking for direction on every little decision. So the manager was confused — she asked for autonomy, then immediately dumped the responsibility back on me. Luna: I can relate. That's a classic sign that the autonomy request might be about something else — maybe a desire for more interesting work, or more visibility, or even a lack of confidence dressed up as a want for freedom. Lucas: Exactly. And by the way, before we dig deeper — you know, we keep this show ad-free on purpose. It's a deliberate choice so that we can spend every minute on the actual substance of managing people. If you've gotten value out of episodes like this one, and you want to support that ad-free approach, the link is buy me a coffee dot com slash fexingo. It's a small gesture that helps keep the lights on here. Luna: Yeah, and we genuinely appreciate that. It lets us focus on what matters, like figuring out what Maya's manager should do next. Lucas: Right. So back to Maya. Her manager, let's call him Dan, could have gone one of two ways: either clamp down and say, 'You asked for autonomy, so figure it out,' or retreat and start micromanaging again. Both are wrong. The better move is to treat the request as a starting point for a conversation. Luna: So what does that conversation look like? What questions do you ask? Lucas: First, ask for specifics. 'What does more autonomy look like for you? Can you give me an example of a decision you'd like to own that you don't currently?' If they can't give a concrete answer, that's a red flag — it might be a vague dissatisfaction. If they can, you've got something to work with. Luna: And in Maya's case, she actually could. She pointed to the design system — she wanted to make changes without getting approval for every tweak. That's a pretty specific request. Luna: So Dan had a tangible starting point. But then he had to figure out if Maya had the judgment to handle that kind of freedom. Lucas: Exactly. Autonomy is earned through demonstrated judgment, not just asked for. And Dan's instinct to give her a big project right away was a mistake, because he skipped the step of building up trust incrementally. There's a classic framework — it's called situational leadership, and it's about matching your delegation level to the employee's competence and commitment. For someone like Maya, who's competent but maybe not fully confident in a new area, you'd want to start with small, defined tasks with clear boundaries, then gradually expand. Luna: So instead of handing her the whole onboarding flow, he could have given her ownership of just the visual design of a single screen, with the understanding that after she delivers that, they'd review and expand the scope. Lucas: Precisely. That's the 'safe to fail' experiment. You set up a small decision that she can own completely, with a checkpoint afterward. And importantly, you define what success looks like before she starts, not after. So Dan might say, 'Here's the goal for this screen: reduce the number of drop-offs by ten percent. You decide how to get there. We'll review in two weeks.' Luna: That gives her clear criteria, and it also gives Dan a way to evaluate her judgment, not just her output. Lucas: Right. And if she hits the target, then he can expand the scope. If she doesn't, then they can talk about what she learned and adjust. That's how you build autonomy as a muscle, not as a gift. Luna: I remember once I had a boss who did this with me on a big client project. He gave me the lead on the presentation deck, but only for the first ten slides, and we had a review after each section. It felt a bit like training wheels, but it taught me how to make decisions within a framework, and eventually I was doing the whole thing on my own. Lucas: That's a great example. And it highlights something else: autonomy isn't just about the employee getting what they want. It's about you, the manager, getting comfortable with the risk. You're essentially taking a bet on your employee's judgment, and you want to make sure you're not betting the farm on the first try. Luna: So what are the signs that an employee is actually ready for more autonomy? How do you know before you even have the conversation? Lucas: A few things. First, they proactively communicate problems and solutions, not just problems. Second, they show a track record of meeting deadlines and commitments. Third, they ask good questions that show they're thinking about the bigger picture. And fourth, they take ownership of mistakes — they don't blame others or make excuses. If you see those behaviors, then the autonomy request is probably legitimate. Luna: And if they don't show those signs? What if Maya had a history of missing deadlines and always asking for help? Lucas: Then the conversation shifts. You don't just say no. You say, 'I hear you that you want more autonomy. Let's work together to build the track record that earns it.' And then you set up a development plan with specific goals. For example, 'Over the next quarter, you'll own the scheduling for the design reviews. You'll be responsible for sending invites, setting the agenda, and following up on action items. If you handle that consistently, we'll expand from there.' Luna: That's a nice way to turn a vague demand into a concrete development opportunity. And it also makes it clear that autonomy is a reward for demonstrated capability, not a right. Lucas: Exactly. And this is where a lot of managers trip up. They either cave and give too much too soon, or they get defensive and shut the request down. Both responses can hurt the relationship. The art is in finding the middle path: acknowledge the desire, break it down into small experiments, and use those experiments to build trust on both sides. Luna: So what about the flip side? What if an employee has been given autonomy and they still keep coming back for every decision? That was Maya's situation initially. Lucas: That's a common issue, and it often stems from a fear of making a wrong call. The employee thinks that asking for permission is safer than risking a mistake. As a manager, you need to make it psychologically safe to fail. You can say, 'I'm giving you the decision here. I trust your judgment. If you're unsure, there's a decision-making framework we can use, but I want you to make the final call.' And then you have to resist the urge to jump in when they come to you with a question. Luna: So you're saying you have to train them to stop coming to you, almost like breaking a habit. Lucas: Yes. And one effective technique is to set a boundary. For example, 'For the next month, I want you to make all decisions that are within the scope we agreed on. If you hit something that's truly outside that scope, then bring it to me. But otherwise, I trust you.' And then you have to follow through and not intervene, even if you see them struggling a bit. That's how they learn. Luna: But what if they make a costly mistake? Isn't that a risk? Lucas: It is, and that's why you start with safe to fail experiments. You're not giving them the keys to the whole kingdom on day one. You're giving them a small pet project where the cost of failure is low. And you also have to define what 'failure' means upfront. Is it a missed deadline? A budget overrun? Usually, you can contain the damage. And the learning that comes from a contained mistake is often worth more than the cost. Luna: So let's go back to Maya. Dan used the incremental approach. He started with the design system tweaks — maybe just the color palette and typography — with a two-week check-in. What happened next? Lucas: From what I've seen, Maya nailed it. She made a few changes that slightly clashed with the brand guidelines, but Dan had set up a checkpoint, so they caught it early and adjusted. After two more cycles, she was confidently owning the whole design system and even mentoring a junior designer. The key was that Dan didn't just give her autonomy; he coached her into it. Luna: That's a great outcome. I think the takeaway for our listeners is that 'I need more autonomy' is an opportunity to have a deeper conversation about development, not a demand to be managed. Lucas: Exactly. And that's the core message for this episode. When an employee asks for more autonomy, resist the urge to either say yes or no immediately. Instead, turn it into a conversation about specifics, set up small experiments, and use checkpoints to build trust on both sides. You'll end up with a more capable employee and a stronger team. Luna: And if you're a listener who's been on the employee side, maybe you've asked for more autonomy and been told no. What should you do? Lucas: That's a good question. As an employee, you can ask your manager, 'What would it take for me to earn more autonomy on project X?' That shows you're thinking about the process, not just the outcome. And then you can work on those specific behaviors. It's a more persuasive approach than just repeating the demand. Luna: So it's a two-way street. Managers need to give it incrementally, and employees need to show they can handle it. Lucas: Right. And I think that's a good place to leave it. The next time someone on your team says 'I need more autonomy,' you'll know it's not a problem to solve, but a journey to navigate. Luna: And maybe a journey that starts with a coffee. I know I need one. Lucas: Ha, absolutely. Thanks for joining us on Manager Mondays. We'll catch you next week.