Accountability is one of the most used words in organizational life. Everyone wants more of it. Leaders talk about building a culture of accountability but there is a principle that many organizations consistently disregard, often without noticing: accountability without authority is unfair.
And when you do it at scale, it doesn’t just feel unfair. It erodes trust, distorts behavior, and quietly poisons the decision-making culture you are trying to build.
Authority has a bad reputation. It conjures images of top-down directives, rigid hierarchies, and bosses who don’t listen. That association has led many organizations to treat authority as something to be minimized or replaced — preferably with influence, collaboration, and consensus.
Authority, in the organizational sense, is simply formal permission. It is the set of decisions you are authorized to make and the actions you are authorized to take in order to fulfill your role. To have authority is to be authorized — nothing more, nothing less.
Think of it this way: if you are accountable for customer acquisition, you need to be authorized to research prospects, initiate contact, and pitch your offering. Not because you have to do all of those things yourself, but because you need the means to get them done. Accountability without that authorization is a setup for failure.
When accountability and authority fall out of alignment, organizations experience one of two failure modes — sometimes both at once.
When someone is held responsible for a result but lacks the authority to shape the conditions that produce it, they will find other ways to get things done. Not because they are manipulative, but because they are resourceful and under pressure. They will drop the name of a senior sponsor. They will imply broader support than actually exists. They will let urgency do the work that legitimate authority should be doing. The organization then mistakes these workarounds for leadership skill, and the underlying misalignment never gets fixed.
When someone can exercise formal authority without being held accountable for how they use it, the damage is different but equally corrosive. Poor decisions go unchallenged. Arbitrary behavior gets normalized. And the message that spreads through the organization is that the rules apply selectively.
Influence without authority (IWA) has become something of an organizational ideal — the mature, collaborative alternative to positional power. And in the right context, it genuinely is. Networking, coaching, brainstorming, building relationships across functions: these are exactly the situations where IWA belongs.
The problem is when IWA becomes a substitute for clarifying authority — when organizations use it to sidestep the harder work of deciding who is actually authorized to decide what.
Consider what genuine IWA requires: you make your case, and if the other person isn’t persuaded, you accept their decision. But how many organizations actually operate that way? More often, IWA is deployed with an implicit expectation of success — which means the person using it is under pressure to succeed by persuasion alone. When persuasion doesn’t work, other forms of leverage tend to fill the gap.
IWA is not a panacea. It is one tool among several, and it works best when the stakes of non-compliance are low and no one is being held accountable for the outcome.
The fear that often drives the retreat from authority is understandable: no one wants a workplace where decisions are made unilaterally without input, context, or dialogue.
But having authority does not mean using it unilaterally. A manager who is accountable for team performance and authorized to set direction can still invite input, build consensus where it makes sense, delegate decision rights to senior team members, and approach feedback as a two-way conversation. What they cannot do — and remain congruent — is pretend they are using IWA while quietly reserving the right to veto any outcome they don’t like.
The key is transparency. Tell your team upfront whether you are asking for input to inform your decision, or whether you are committed to a consensus outcome. Those are different processes, they produce different expectations, and conflating them is where trust gets damaged.
A work role typically has multiple, specific authorities — not a single undifferentiated block of power. A manager may be authorized to set priorities and give feedback to their direct reports, while only being authorized to make recommendations to peer roles. A safety officer may be authorized to issue immediate instructions that others are obligated to follow, while a consultant in the same organization may only be authorized to advise.
When these authorities are explicit, visible, and perceived as legitimate — and when people are held accountable for how they use them — a lot of the friction that organizations attribute to personality conflicts or communication failures turns out to be structural. The conflict wasn’t really about the people. It was about roles that had overlapping or incompatible authority, and nobody had bothered to sort it out.
If you want a quick read on whether accountability and authority are aligned in your organization, ask this: Can the people you hold accountable actually control the conditions required to deliver the results you expect from them?
If the honest answer is “not always” or “not really”, you have a structural problem dressed up as a performance problem. And no amount of accountability culture, feedback training, or influence-without-authority workshops will fix it.
The fix is simpler than it sounds: clarify who is authorized to decide what, make sure that authority matches what you are holding them accountable for, and then hold them accountable for how they use it.