The Cost of Being Left Alone
Autonomy is one of those things that sounds self-evidently good until you look closely at what role design gives you alongside it - and what it quietly removes.
Most people would say they want it. The freedom to decide how to approach a problem, to structure a working day, to own the method as well as the outcome. In theory, there’s almost no downside.
In practice, the picture is more interesting.
The science
Deci and Ryan’s Self-Determination Theory, built across decades of research from the 1970s onward, identifies autonomy as one of three core psychological needs - alongside competence and relatedness. When any of these is chronically unmet, motivation deteriorates over time, regardless of what else is in place. The salary can be right. The team can be good. A persistent block on autonomy erodes engagement in ways that are difficult to name precisely and easy to blame on something else.
But the same body of work includes a finding that doesn’t get quoted as often: autonomy without accompanying competence doesn’t energise - it destabilises. The freedom to own your work only functions well when you’re reasonably confident you can do it. In early-career contexts, in unfamiliar industries, or in roles that outpace someone’s current development, high autonomy can produce the opposite of its intended effect.
Hackman and Oldham’s Job Characteristics Model (1976) makes a related point, framing autonomy not as a perk but as the dimension that produces felt responsibility for outcomes. That’s the mechanism. When you own the how, you feel the weight of whether it worked. That accountability is part of what makes autonomous work meaningful - and part of what makes it hard.
Why this varies so much between people
Two people in identical roles can experience the same degree of autonomy as either liberation or abandonment, depending on where they are in their development and what they’ve learned to need from working environments.
For some, close direction is genuinely limiting. It creates bottlenecks, signals a lack of trust, and makes excellent work harder to produce than it needs to be. For others - particularly people who are still building expertise, or who value structured feedback and collaborative input - autonomy can feel like being cut loose. The absence of external scaffolding isn’t freedom. It’s silence.
Neither response is wrong. They’re just different configurations of what a person actually needs to do good work.
What it looks like when it’s missing
When someone who needs autonomy is working in a high-control environment, the signs tend to be specific. Frustration at approval processes that feel unnecessary. A sense that the work is technically fine but never quite theirs. The low-grade friction of being capable of more than the role asks.
Tessa West’s research on career misdiagnosis (Job Therapy, 2023) describes how frequently people attribute this feeling to the wrong cause - blaming the company, or the culture, when the underlying issue is a structural mismatch between how they work best and what the role actually allows.
What it looks like when it’s right
High autonomy, when it fits the person and the context, tends to produce something distinct: genuine investment in the outcome. When you own the method, you tend to care more about whether it succeeds.
Teresa Amabile’s research on the progress principle found that daily progress in meaningful work is the strongest driver of positive inner work life - stronger than recognition, incentives, or relationships. Autonomy creates the conditions for that progress to be visible, because you can trace a direct line from your decisions to the result.
The tradeoff
This is where the factor gets complicated.
High autonomy usually comes with reduced structure. Less mentorship. Fewer onboarding touchpoints. Less of the feedback infrastructure that catches you when something’s quietly drifting. The same environment that makes a confident, capable person feel trusted can make a less certain person feel unsupported - and both responses are entirely reasonable.
There’s also a version of wanting autonomy that’s really wanting to escape a specific manager. Those are different problems. One is about role design. The other is about a person. Mixing them up leads to lateral moves that replicate the same dissatisfaction somewhere new, because the actual problem never got named precisely enough to solve.
Finding out where it actually sits
Most people haven’t been forced to choose between autonomy and something else they also want. They’ve never had to decide whether it matters more than structured development, or close collaboration, or a team that moves as a unit. Until you face that trade explicitly, you’re working with a preference, not a hierarchy.
To find out where autonomy actually sits in yours: https://trykanso.app. Kanso was built specifically for that trade. It forces the choice rather than asking you to imagine it.
If you’ve ever accepted less autonomy to get something else - what was it, and would you make that trade again?