Accountability Without Authority Is a Set-Up

Organisations often believe they have an accountability problem when what they actually have is an authority problem.1 Roles are clearly named. Expectations are documented. Ownership is assigned.2 And yet, decisions stall, issues circulate, and outcomes drift. When people are held accountable without the authority to act, accountability becomes performative rather than effective.3

What accountability without authority looks like

This misalignment is rarely explicit. It shows up quietly, through patterns such as:

  • leaders expected to deliver outcomes without control over resources
  • managers accountable for adoption without influence over incentives
  • sponsors responsible for benefits without authority to intervene post-go-live
  • teams held to targets without decision rights to change how work is done On paper, accountability exists. In practice, it is hollow.

Why this misalignment persists

Accountability without authority often emerges unintentionally. Organisations want to empower without over-centralising. They want to distribute responsibility while maintaining governance safeguards. They want to avoid bottlenecks. In trying to balance these goals, they create roles that carry responsibility but lack mandate. This feels reasonable at design time. Under pressure, it becomes a liability.4

How authority gaps distort behaviour

When people are accountable but lack authority, they adapt. They escalate more than necessary. They seek consensus to protect themselves. They avoid decisive action when outcomes are uncertain.

None of this is irrational. It is a way of managing personal and professional risk when expectations exceed control. Over time, this produces:

  • slower decision cycles
  • increased reliance on committees
  • diluted ownership
  • frustration on all sides

The organisation becomes busy managing the gap rather than closing it.

Why escalation becomes the default safety mechanism

Escalation fills the vacuum created by missing authority. When people cannot act, they ask permission. When permission is unclear, they seek alignment. When alignment is slow, they wait. Escalation is framed as prudence. In reality, it is often a symptom of structural ambiguity.

As escalation volumes increase, senior leaders become bottlenecks. Response times slow. Pressure intensifies. The very leaders who want accountability end up overwhelmed by its absence.

The hidden cost to value and momentum

Accountability without authority does more than slow decisions. It undermines confidence. People learn that being “accountable” means absorbing pressure without the tools to resolve it. Over time, they protect themselves by narrowing scope, avoiding risk, or disengaging from outcomes they cannot influence. Change loses momentum not because people do not care, but because caring becomes costly.

Why authority is often left implicit

Many organisations avoid explicit conversations about authority because they are uncomfortable.

Authority implies hierarchy. It raises questions about power, trust, and control. It can feel politically sensitive. As a result, authority is left implicit, assumed to be “understood,” or deferred to governance bodies that are too distant to act quickly. In stable environments, this ambiguity can persist. In change, it quickly becomes a problem.

Re-aligning accountability and authority

Effective organisations are explicit about the relationship between accountability and authority. They clarify:

  • what decisions accountable roles can make independently
  • where authority begins and ends
  • how conflicts will be resolved
  • what support exists when accountability creates friction

This clarity does not eliminate tension. It makes it manageable. People act more decisively when they know the boundaries within which they can do so.

Authority is not the same as control

Granting authority does not require centralising control. Authority can be bounded, conditional, and time-limited. It can be accompanied by clear escalation paths and feedback loops. What matters is that those held accountable have some ability to influence outcomes. Without that, accountability becomes a burden rather than a lever.

A more realistic approach to accountability design

If organisations want accountability to work, they need to design it honestly. That means asking:

  • What outcomes are we truly expecting from this role?
  • What authority is required to deliver them?
  • What risks are we asking this role to absorb?
  • What support will be available when trade-offs arise?

Answering these questions upfront prevents many of the issues that surface later as “execution problems.” This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how decision rights, governance, and authority structures shape outcomes during transformation.



  1. Hackman, J. R. (1987). “The Design of Work Teams.” In J. W. Lorsch (Ed.), Handbook of Organizational Behavior (pp. 315–342). Prentice Hall. Hackman demonstrates that team effectiveness depends on having authority commensurate with responsibility — teams that are accountable for outcomes they cannot control cannot function as designed. The accountability/authority gap is not merely uncomfortable; it is structurally incapacitating. Leaders who believe they have an accountability problem are typically looking at the downstream effect of an authority problem they have not named. ↩︎

  2. Lawrence, P. R., & Lorsch, J. W. (1967). Organization and Environment: Managing Differentiation and Integration. Harvard Business School Press. Lawrence and Lorsch’s foundational work on differentiation and integration shows that as organisations differentiate into specialised roles, the authority structures needed to integrate those roles must be explicitly designed — implicit authority assumptions that work in stable contexts fail under the load of coordinating differentiated accountability. Clear documentation of roles without explicit authority design is precisely what produces the hollow accountability they describe. ↩︎

  3. Eisenhardt, K. M. (1989). “Agency Theory: An Assessment and Review.” Academy of Management Review, 14(1), 57–74. https://doi.org/10.5465/amr.1989.4308844. Eisenhardt’s review of agency theory establishes that effective accountability requires the agent to have not only the formal responsibility for outcomes but the decision rights and resources needed to actually influence them. When accountability is assigned to a role that lacks authority, the agent cannot perform their function and accountability becomes a label rather than a mechanism — visible in org charts, inert in practice. ↩︎

  4. Argyris, C. (1957). Personality and Organization: The Conflict Between System and the Individual. Harper & Brothers. Argyris shows that formal organisation design routinely creates conditions that appear empowering at the governance level while generating constraint and dependency at the operational level. Roles are designed to look autonomous while lacking the actual mandate required for autonomous action. This is not malicious; it reflects the difficulty of translating governance intent into operational authority structure. The gap only becomes visible when pressure tests the limits of the mandate people believed they held. ↩︎