
How to Spot an Authority Gap Before It Sinks Your Next Initiative
Two senior leaders once sat six feet apart in a session I was facilitating. Both believed they owned the same decision. Neither had ever said that out loud. The initiative had been stuck for seven months, and the room had been calling it a leadership accountability problem. It wasn't. It was an authority gap, and nobody had named it.
Authority gaps rarely announce themselves. They don't show up on a dashboard. They show up as slow decisions, polite meetings, and work that circles back around three times before anyone commits. Most teams misread that as a people problem. It's almost always a design problem, and you can catch it early if you know what to look for.
Leadership Accountability: What an Authority Gap Looks Like
An authority gap is the space between who is responsible for an outcome and who can actually decide. Someone owns the result. Someone else controls the resources, the timing, or the veto. Both people are behaving rationally. The system is broken.

You've seen the symptoms. A project needs "alignment" before it can move, but nobody can say whose alignment. A leader says yes in the room, then relitigates the same point over email. Decisions get made twice, once by the person accountable and once by the person with real leverage.
Here's what trips up strong teams. Capable people compensate for authority gaps instead of surfacing them. They negotiate, they build coalitions, they work around the ambiguity. It looks like collaboration. It's actually friction-absorbing energy that should be going into the work. This is one reason youroffsite keeps producing the same stale outcomes year after year.
Why Capable Teams Create Authority Gaps Without Noticing
Nobody designs an authority gap on purpose. They accumulate.
A company grows past the size where everyone sits at one table. Roles were fluid, and fluid worked beautifully at twelve people. At eighty, fluid means guessing. Or a new strategy arrives, and ambition gets updated fast. Decision rights get updated slowly, if at all. The new mandate lands on top of old approval thresholds.
There's also a human reason. Naming who decides means telling someone else that they don't. That's an uncomfortable conversation between two peers who respect each other. So the conversation gets deferred, and the ambiguity quietly becomes permanent. Weakteam decision-making is often just deferred conflict wearing a process costume.
A Five-Question Leadership Accountability Test You Can Run
You don't need a consultant to run this leadership accountability test. Answer these about a live initiative you're currently responsible for. Write the answers down, because vagueness hides well in your head.
Can I name the single person who makes the final call? Not the committee. One name.
Can I spend without asking permission? If yes, up to what number, and who set it?
Who can stop this work? List everyone with a real veto, formal or informal.
What would I have to escalate, and to whom? If the path isn't obvious, that's the gap.
If I decided today and someone disagreed tomorrow, would my decision hold? Be honest.

Now do something braver. Ask two peers to answer the same five questions about your role. Then compare. The gap between your answers and theirs is the exact size of your authority gap. I've watched senior teams do this exercise and go completely quiet. That silence is progress.
What Changes Once You Name It
Naming an authority gap does more than clarify a workflow. It changes what the team believes about itself.
Before, the story was about effort or attitude. Somebody wasn't driving hard enough. Somebody was territorial. That story creates defensiveness, and defensiveness is expensive. Once the gap has a name, the conversation moves from personality to structure. Structure is fixable. Personality feels like an accusation.
Practical fixes are usually smaller than people expect. Write down the decision, the decider, and the people who get consulted. Set a spending threshold and say it out loud. Agree on what gets escalated and how fast. Then test it against a real decision within two weeks, because paper agreements don't hold until they've survived contact with something contested.
What mostexecutive team dysfunction needs is not more accountability language. It needs decision rights that match the work being asked for.
Ask the Question Your Team Is Avoiding
You probably already suspect where your authority gap sits. Most leaders do. What stops the conversation isn't ignorance; it's that you're a stakeholder in the outcome, so you can't referee it fairly. That's not a flaw. It's the reason facilitation exists.
At Acrux Consulting, I sit in that room with no stake in who wins. My job is to make the undiscussable discussable, then get the team to a decision they'll actually honor on Monday. If your next initiative is carrying an authority gap you haven't named yet,let's schedule a leadership conversation and find it before it costs you another two quarters.
Frequently Asked Questions
How is an authority gap different from a skills gap?
A skills gap means someone can't do the work yet. An authority gap means they can do it but aren't empowered to. Training fixes the first one. Only a decision-rights conversation fixes the second.
Should decision rights live in job descriptions?
Job descriptions are too static and too private to do this job well. A shared decision map that names owners, consulted parties, and thresholds works better. Keep it visible to the whole leadership team.
How often should a leadership team revisit authority?
Revisit it whenever the strategy, team structure, or ownership changes. Annual reviews are usually too slow. Any time ambition moves, authority should be checked.
Will hiring a stronger leader close an authority gap?
Rarely. A strong hire dropped into ambiguous authority will either burn political capital fighting it or quietly adapt. Fix the design first, then hire into clarity.
What if two leaders genuinely need to share a decision?
Shared decisions can work, but only with a named tiebreaker and a deadline. Without both, shared authority becomes delay. Decide in advance who breaks the tie and how quickly.

