The tension between a high performer’s need for autonomy and a manager’s responsibility to maintain structure is one of the most common friction points I’ve observed across organizations. It rarely announces itself as a crisis. Instead, it emerges gradually – through a capable person taking on more decision-making without explicit permission, or through subtle resistance when asked to follow established processes. By the time a manager recognizes what’s happening, the situation has often calcified into something harder to address.
What makes this dynamic tricky is that both sides are usually right. The high performer genuinely has developed competence that exceeds the constraints of their role. They can see inefficiencies in existing workflows. They have ideas about how to do things better. And they’re often correct. At the same time, the manager is responsible for consistency, risk management, and ensuring that organizational knowledge doesn’t live solely in one person’s head. The impulse to protect structure isn’t always about control – it’s often about sustainability.
I’ve found that the real problem emerges when managers treat autonomy as a binary choice. Either the person stays in their defined role with defined responsibilities, or they get promoted into a new position with a new title and new constraints. There’s rarely a middle ground explored, even though that’s where most solutions actually live.
The Autonomy Conversation Usually Comes Too Late
Most managers don’t initiate a direct conversation about autonomy until the high performer has already started operating independently without permission. By then, the conversation becomes defensive. The manager feels their authority has been challenged. The performer feels they’ve been doing the right thing and now they’re being criticized for initiative. Both parties are slightly entrenched.
The better approach – and I’ve seen this work consistently – is to name the pattern early, before resentment builds. When you notice a strong performer consistently pushing boundaries or asking for exceptions to process, that’s the moment to have a structured conversation about what they actually need. Not in a punitive way, but as an acknowledgment that their capabilities are evolving and the current arrangement may not be serving them or the organization well.
What I’ve noticed is that high performers often don’t explicitly ask for autonomy. They demonstrate it first, then wait to see if they’ll be shut down. If they are, they either disengage or leave. If they aren’t, they keep expanding their sphere of influence until someone finally objects. A manager who gets ahead of this by asking directly – “What decisions do you want to be making that you’re not making now?” – often learns that the person’s actual needs are more specific and negotiable than they expected.
Autonomy Isn’t One Thing
This is where many managers get stuck. They think autonomy is a single dimension they can turn up or down. In reality, it’s multifaceted. A person might want complete autonomy over how they execute their work but still want input on what projects they take on. Or they might want to choose their own priorities but need clear guardrails around budget or risk. Or they might want to make hiring decisions independently but need oversight on strategic direction.
I’ve found it useful to break autonomy into specific domains: execution (how they do the work), prioritization (what they work on), resource allocation (what they spend), hiring and team composition (who works with them), and strategic direction (where their function is headed). A high performer might need significant autonomy in three of these areas while still needing structure in the other two. Most managers never have this conversation in these terms, so they end up either granting too much autonomy across the board or refusing it entirely.
The conversation becomes much more productive when you can say something like: “You clearly don’t need oversight on execution – you’re consistently producing excellent work. Where I think we need to stay aligned is on prioritization, because your work intersects with three other teams’ roadmaps.” That’s specific. It’s respectful. And it often resolves the tension because the person feels heard on what they actually care about.
When Autonomy Becomes a Retention Problem
There’s a point at which refusing reasonable autonomy becomes expensive. A strong performer who feels micromanaged will eventually look elsewhere. This isn’t dramatic – they don’t usually announce it. They just gradually become less engaged, and then one day they have an offer from another company. The exit interview reveals that autonomy was the core issue all along.
What I’ve observed is that organizations often underestimate how much autonomy costs them in retention. They see it as a risk (what if the person makes a bad decision?) and fail to calculate the cost of replacing them (recruitment, onboarding, lost productivity, team disruption). For a truly high performer, the math almost always favors granting reasonable autonomy.
That said, there are legitimate cases where a person’s desire for autonomy exceeds what the organization can actually provide. Sometimes the role itself has inherent constraints. Sometimes the person’s judgment isn’t as sound as they believe it is. In those situations, the honest conversation is often: “This role may not be the right fit for you long-term, and that’s okay. Let’s think about what would be.” That’s better than slowly strangling the relationship through continued conflict.
The Hidden Risk: Autonomy Without Accountability
One thing I’ve learned the hard way is that autonomy without accountability creates problems that are harder to fix than the original tension. When a manager grants autonomy to a high performer but doesn’t establish clear metrics or checkpoints, the person can drift into territory that’s damaging to the broader organization. They might optimize for their own goals at the expense of other teams. They might take risks that the organization isn’t comfortable with. They might build processes that only they understand.
The autonomy that works is paired with transparency. The high performer makes decisions independently, but they’re visible decisions. There are regular conversations about what they’re doing and why. There are agreed-upon metrics that define success. There’s a clear escalation path if something goes sideways. This isn’t micromanagement – it’s accountability. And most strong performers actually respect this because they understand that autonomy without accountability is just chaos.
I’ve also noticed that when autonomy is granted without this structure, it often leads to a different problem: the high performer becomes indispensable. All the knowledge and decision-making lives with them. The organization becomes fragile because it depends on one person. That’s not sustainable, and it’s not actually good for the performer either, because they can never truly leave or move on to something else.
The Structural Solution
The managers I’ve seen handle this most effectively tend to use one of a few structural approaches. Some create expanded roles that give the high performer more autonomy while keeping them in the same reporting structure. Some establish clear domains where the person has full decision-making authority and other domains where they need approval. Some shift to outcome-based management, where the person is measured on results rather than process compliance.
What these approaches have in common is that they’re deliberate. They’re not ad hoc exceptions made to keep someone happy. They’re structured in a way that could theoretically be applied to other people in similar situations. This matters because it prevents the perception of favoritism and it creates precedent that makes future conversations easier.
The worst approach I’ve seen is when a manager grants autonomy informally and inconsistently. The high performer gets away with things that would be unacceptable from someone else. Other team members notice. Resentment builds. The manager ends up having to clamp down, which feels like a betrayal to the high performer. Everyone loses.
The reality is that high performers who want more autonomy are usually signaling something important about their development. They’re outgrowing their current constraints. The question isn’t whether to accommodate that – the question is how to do it in a way that works for both the person and the organization. That requires specificity, clarity, and a willingness to redesign the role rather than simply defend the existing structure.
