Many leaders have told their team to use their judgment. What they’ve actually done is left the decision sitting on the floor between them.
“Use your judgment” isn’t permission. It’s ambiguity with good intentions. The team hears it and wonders... how much judgment? On what? Up to what point? Who gets blamed if they judge wrong?
Autonomy isn’t an attitude. It’s a scope. The team doesn’t need to feel empowered. They need to know exactly what they’re authorized to decide.
That’s a different conversation.
Autonomy isn’t a mindset you give someone. It’s a boundary you draw and then stand behind when they use it.
What most people think Autonomy means
Many leaders think they’ve given the team permission to act when they’ve said the right things. “You’re empowered.” “I trust your judgment.” “Don’t come to me with every little thing.”
The team hears all of that. And then they still escalate, because the scope isn’t clear.
Autonomy isn’t about attitude or trust signals. It’s about decision rights. Who can decide what, and up to what consequence, without escalating?
When that’s unclear, the team defaults to asking. Not because they lack confidence. The risk of deciding wrong without authorization is higher than the cost of asking.
What Autonomy actually looks like in leadership
Autonomy shows up in three places.
-
Defining which decisions belong to the team member, not just which tasks
-
Drawing the line clearly: decide alone up to here, flag me above here
-
Backing the decision publicly even when you’d have decided differently
When Autonomy is real, the escalation rate drops. The team stops routing every judgment call upward. They make the call, note it, and move. That’s what an authorized team looks like in operation.
A pattern I have lived through
In one of my businesses, we had a team that was experienced and capable. But decisions above a certain size kept routing back to me, not because I wanted them there. It was that the team wasn’t clear what they were authorized to decide.
I’d say “use your judgment.” They’d hear “if this goes wrong, it’s on you without cover.”
What changed wasn’t a speech. It was a specific conversation: here are the decisions that are yours. Here’s the line. Below it, decide. Above it, flag me before you move. I’ll back you on everything below the line, even if I’d have done it differently.
That conversation changed the operating tempo more than anything else I’d tried.
You see this in basketball. A point guard who has to look to the bench before every call isn’t running the offense. They’re relaying it. The teams that operate fastest have point guards who know exactly what they’re authorized to decide in real time and who trust the coach will back those calls.
The discipline leaders must practice
Autonomy requires leaders to define scope, not just signal trust. Three disciplines make the permission real.
-
Name the decision, not just the task. “Handle the vendor relationship” is a task. “You own vendor pricing decisions up to $X without my sign-off” is Autonomy. The difference is specificity.
-
Draw the line explicitly. Define the threshold, consequence, cost, or scope, above which the team flags you. Below it, they decide. The line has to be visible, not implied.
-
Back the decision publicly even when you’d have decided differently. If the team makes a call within scope and you relitigate it, you’ve retracted the permission. They’ll stop deciding.
Actionable application
Pick one role on your team and ask three questions.
-
Can I name three decisions they’re authorized to make without involving me?
-
Is there a clear threshold that defines when they should flag me?
-
In the last 30 days, have I backed their within-scope decisions or relitigated them?
If you can’t name the three decisions, the permission isn’t real yet. Write them down and have the conversation. That specificity is what activates the team.
What usually gets in the way
Leaders resist specificity because specificity creates accountability for them.
When you clearly name what the team is authorized to decide, you give up the ability to step back in without cost. You’ve ceded the right to override without consequence.
So leaders stay vague. “Use your judgment” keeps the options open.
The team pays the price. They stay in an escalation pattern that slows everything down and keeps the leader in the middle of decisions that shouldn’t need them.
Closing challenge
Think about a decision that came to you in the last week that you wish hadn’t. Was the person who brought it clear they were authorized to make it without you?
If they weren’t, that’s not on them. The scope was never drawn.
Autonomy isn’t a mindset. It’s a scope. Until the scope is clear, the team is waiting for you to decide.
Draw the line. Back it. Then get out of the way.
One Word Leadership is our way of teaching leaders the disciplines that make growth less chaotic and more sustainable.
Pat Alacqua is a business growth strategist and Amazon best-selling author of Obstacles to Opportunity. He helps leadership teams think, plan, and execute differently so they can fix or prevent what growth breaks.