The conversation usually starts the same way. A leader tells me their team is empowered. Then they sigh and admit their team will not make a decision without checking first. Somewhere between those two sentences sits the real problem, and it is not the team!
On the latest KatAnu Connect Podcast, Anu Smalley, Ryan Smith and I sat down to unpack exactly this gap. We were recording from Atlanta, Los Angeles and the Scottish Highlands, and the topic was supposed to be ownership and accountability. It turned into something bigger. It turned into a working conversation about why so many “empowered” teams are quietly waiting to be told what to do, and what it takes to design autonomy into the system rather than just declare it.
The Accountability Trap
Most organizations do not have an accountability problem. They have an ownership problem. Without ownership, the word “accountability” becomes a polite way of saying blame. Someone gets pointed at when the work goes sideways, and the harder question goes unasked: who designed the conditions under which the work was supposed to succeed in the first place?
Anu put it sharply on the episode. The system has to enable accountability. A leader can give a passionate speech about empowerment, but if the system around the team still requires approval for every decision, nothing changes. The team learns to wait. They learn that “empowered” is a word that gets said in town halls and ignored in practice.
Ryan added the other half of the picture. Organizations have spent decades training people to be order takers rather than artisans. “Tell me exactly what you want and I will go and do it.” That training produces teams who genuinely do not believe their input is wanted. When the door finally opens, they stand in the hallway and wait for permission to walk through.
| “There can be no accountability without ownership. And until people really feel like they own a product, you will not get either.” Ryan Smith, KatAnu Connect Podcast Ep. 177 |
Trust Stands on Three Legs
When you feel the urge to micromanage, that urge is almost always a signal. Something underneath is not where it needs to be. I find it helpful to think of trust as a three-legged stool. If one leg is wobbly, the whole thing tips.
- Clarity. Does the team know the goal and the priorities? Have they been read in on the vision, or are they working from a list of tasks with no context?
- Capability. Do they have the skills and the information to do the work? Without those, no amount of trust will produce the outcome you are hoping for.
- Visibility. Can you see the status and the progress without interrupting? If you do not have a window into the work, you will create one by walking over and asking, and that erodes the very trust you said you were building.
Notice that none of those three legs is “check in more often.” Trust is not built by checking. It is built by clarity, capability and visibility working together. The next time you feel anxious about a team’s work, ask which leg is wobbly. Fix that one. Then step back.
| “Trust doesn’t happen because you demanded it. Trust happens because you worked on it. You created it. You showed up.” Anu Smalley, KatAnu Connect Podcast Ep. 177 |
Why Leaders Struggle to Let Go
We spent real time on this in the episode. Leaders struggle to let go because they have been judged, for years, on whether the work got delivered. That is how they got promoted. That is what their bonus has historically depended on. The moment you say “stop managing the work,” you are asking them to walk away from the thing they have been told defines their value.
The honest question underneath that resistance is this: what do I add if I am not managing the work?
A lot, but it requires a shift. The leader’s job becomes clarity of purpose and competence of the team. You hire well, you set context, you create the conditions, and then you step out of the way. Your value is not in having the answer. Your value is in helping the team find the answer faster than they would have alone.
That is the shift from “I know the answer” to “how can I help you find the answer?” One sentence. A completely different relationship.
Make Trust Visible
Trust that is invisible is fragile. The fastest way to make it visible is through working agreements: short, written, agreed-upon norms about how the team will operate. They look small. They are not. They might look something like this:
- Blockers are surfaced within 24 hours. No one sits on a problem for a week and then announces it at Sprint Review.
- No surprises at Sprint Review. If the work is not going to land, that conversation happens days earlier, not at the demo.
- The Product Owner does not assign tasks. The team pulls work as they have the capacity to take it on.
- Done means the Definition of Done. Not “done-ish.” Not “almost.” Done.
- No scope-switching mid-sprint. Flexibility is fine. Whiplash is not.
Each one of these removes a place where ownership quietly leaks out of the team and back to the leader. Each sprint that holds these agreements buys credibility, and credibility is the currency that funds the next round of autonomy.
Guardrails, Not Gates
A lot of well-meaning organizations confuse guardrails with gates. Gates are approval points. Guardrails are decision boundaries.
One of the cleanest examples we discussed on the show: a team empowered to spend up to $200 against the company’s core values, with no approval required. The boundary is clear. The values are clear. The team can move. The leader does not become the bottleneck for every receipt.
The point is not the $200. The point is replacing the approval queue with a published boundary. Inside the boundary, the team owns the call. Outside it, they bring you in. Speed comes from clarity, not from permission.
End Hero Culture, One Pomodoro at a Time
One pattern quietly destroys teams: the hero who stays up until 4am solving the problem alone. It feels noble. It is the opposite of noble. It robs the team of the chance to learn the problem, hides the real cost of the work, and burns out the one person who will do it again next time.
Anu walked through a discipline she coaches on the episode, built on top of the Pomodoro Technique:
- First 25 minutes. Work on the problem alone.
- Second Pomodoro. If you are still stuck, pair with someone.
- Third Pomodoro. If the pair is still stuck, bring the team together.
- Fourth Pomodoro. If the team cannot solve it either, stop. The skill or the information you need is not on the team, and grinding for another four hours will not change that.
Leaders check in at each boundary with coaching questions, not answers. The point is to teach the team a problem-solving rhythm, not to step in as the rescuer. Heroes are a sign that the system is broken. Coaches are a sign that the system is working.
The Real Job
The thread running through all of this is simple. Hope is not a strategy for empowerment. You do not get to declare autonomy and walk away. You design for it.
You provide clarity of purpose. You build capability. You make the work visible. You write down the agreements. You replace approval queues with guardrails. You coach instead of rescue. And every successful sprint, every problem solved without you, every decision made at the right level, deposits credibility into the team’s account.
| “The goal isn’t less leadership. It’s leadership that creates more leaders.” Kate Megaw, KatAnu Connect Podcast Ep. 177 |
Real accountability requires real ownership, and ownership only grows in conditions where it is safe to actually take it. That is the real test. Not whether people are technically allowed to take ownership, but whether it feels safe to do so when the work is on the line.
If you have ever wondered why your “empowered” team is still cautious in practice, start there.
LISTEN TO THE FULL EPISODE
Autonomy by Design: Ownership, Accountability, and Letting Go Without Losing Control
Find the KatAnu Connect Podcast on Apple Podcasts, Spotify, and Amazon Music. Direct link: buzzsprout.com/1994694