Organizations frequently say they want more accountability.
Leaders want employees to “own the outcome,” and “take responsibility”. When something goes wrong, the natural response is often to reinforce those expectations: clarify the goal, establish a metric, assign an owner, and hold that person accountable. But there is a structural problem that accountability language cannot solve.
You cannot meaningfully hold someone accountable for an outcome while systematically withholding the authority required to influence that outcome.
Accountability and authority are not competing ideas. They are complementary components of good organizational design.
- Accountability answers: Who owns the outcome?
- Authority answers: Who is permitted to make the decisions necessary to produce it?
When those two answers point to different people, accountability begins to break down.
The Accountability–Authority Gap
Imagine that a company tells a marketing director: “You are accountable for revenue growth.”
At first, that sounds reasonable. But suppose the director cannot change pricing without executive approval, cannot alter the promotional calendar without sales approval, cannot increase advertising investment without finance approval, cannot modify the website without IT approval, and cannot change channel strategy without the president’s approval.
The organization has assigned the director an outcome without assigning sufficient control over the variables producing that outcome. The director may be responsible for the metric, but someone else retains much of the decision authority.
This creates what we might call the accountability–authority gap: Accountability > Decision Authority.
The greater that gap becomes, the less meaningful accountability becomes. This distinction has substantial support in organizational research.
Organizational psychologists and work-design researchers J. Richard Hackman and Greg Oldham developed the influential Job Characteristics Model, which identified autonomy as one of five fundamental characteristics of effective job design. More importantly, their model specifically connects autonomy with an employee’s experienced responsibility for outcomes. Autonomy means having meaningful freedom and discretion over how work is performed. When people possess that discretion, they are more likely to experience themselves as responsible for the resulting performance.
The practical implication is simple: responsibility only feels psychologically credible when an employee can connect an outcome to decisions he or she was actually allowed to make.
Accountability Is a Control Problem Before It Is a Motivation Problem
Leaders sometimes interpret weak ownership as an attitude problem. Examples might be an employee that escalates too many decisions, a department leader that becomes reluctant to make commitments, someone that responds to a failed initiative by saying, “I was waiting for leadership.”
From the outside, these behaviors can look like avoidance or “lack of ownership”. Sometimes they are. But sometimes the organization has actually trained employees to behave this way.
Consider what happens when an employee makes a reasonable decision and is subsequently told:
- “You should have run that by me.”
- “Why wasn’t I involved?”
- “You weren’t authorized to make that call.”
- “Next time, get approval first.”
The employee learns something. Not necessarily that the decision itself was wrong.
The employee learns that independent judgment carries organizational risk.
After enough repetitions, rational employees adapt. They escalate. They document. They seek consensus. They request approvals. They wait. Then leadership observes the resulting behavior and concludes: “People around here don’t take ownership.”
But the organization may have unintentionally designed ownership out of the job.
Research on employee control reinforces this point. In its occupational psychology coverage of job-control research, the American Psychological Association summarizes evidence showing that latitude over work-related decisions affects motivation, morale, and employees’ ability to handle workload. Research associated with the demand-control model has also found particularly problematic conditions where employees face high demands while possessing relatively little control over their work.
The result is a familiar organizational paradox: high expectations with low authority usually create pressure, not ownership.
The Difference Between Responsibility and Decision Rights
One reason organizations create this problem is that the language surrounding accountability is often imprecise. Someone can be responsible for performing work without possessing final authority over every decision associated with that work. That is perfectly normal. The problem occurs when organizations fail to explicitly distinguish between:
- who recommends,
- who provides expertise,
- who must approve,
- who executes,
- and who actually decides.
Bain & Company practitioners Paul Rogers and Marcia Blenko, whose work focuses on decision effectiveness and organizational design, developed the RAPID framework specifically around this problem. RAPID distinguishes five roles: Recommend, Agree, Perform, Input, and Decide. The critical insight is that these roles are not interchangeable. Someone may execute a decision without owning the decision itself. Someone else may provide input without possessing veto authority. Most importantly, the organization needs clarity about who actually has the D — the authority to decide.
This sounds obvious. But, in practice, it frequently is not.
Aaron De Smet and colleagues at McKinsey, drawing on the firm’s organizational-design work, have similarly criticized traditional RACI implementations because the distinction between being “responsible” or “accountable” and actually possessing the right to make the decision can remain ambiguous. Their recommendation is straightforward: organizations should establish clear accountable decision makers and explicit escalation protocols.
The distinction matters because an employee can be assigned responsibility on an organizational chart while possessing surprisingly little operational authority.
When Everyone Is Accountable, No One Really Is
There is another failure mode. Instead of withholding decision authority from the accountable person, organizations distribute decision authority across too many people. A leader is supposedly accountable for a project.
- But Finance must agree.
- Operations must agree.
- Sales must agree.
- The executive sponsor must agree.
- The president expects to be consulted.
- Legal occasionally exercises a veto.
And several other stakeholders have acquired informal approval rights simply because previous leaders learned that proceeding without them creates political problems.
The nominal owner now has accountability without finality.
This is why decision-rights frameworks emphasize identifying an actual decider.
Rogers and Blenko describe organizations where ambiguity over decision authority causes decisions to stall, be repeatedly revisited, or fail to occur at all. In one example involving an automobile manufacturer, marketing and product development both believed they possessed decision authority over elements of new vehicle models. The resulting conflict contributed to missed deadlines and lost sales.
The issue is not merely inefficiency. It corrupts accountability because five people may be able to prevent an outcome while only one person is ultimately evaluated for it. At that point, the organization has separated control from consequence.
The Manager Who Owns Everything Eventually Owns Nothing
Ironically, leaders often retain decision authority because they are trying to increase accountability.
A manager may think, “I am ultimately responsible for this department, so important decisions should come through me.”
Individually, each intervention seems sensible.
The manager approves pricing, hiring, customer exceptions, campaign spending, process changes, vendor selection, etc.
Soon the manager has accumulated dozens of decision rights.
The employees beneath the manager still retain their job titles and performance expectations, but increasingly their actual role is to gather information, formulate recommendations, and seek approval. The manager has become the real decision maker. At that point, there is an uncomfortable but necessary organizational conclusion:
If the manager retains the decision, the manager must retain some corresponding accountability for the consequences of that decision.
Authority cannot continually travel upward while accountability remains below.
That is not delegation. It is centralized decision-making disguised as distributed ownership.
The Real-World Cost of Ambiguous Authority
The effects are not merely theoretical.
Related Bain change-management work has documented organizations in which uncertainty over who could decide caused seemingly ordinary operational decisions to become trapped in prolonged discussion. In one supply-chain example, a manager described spending a year trying to obtain a decision on a new replenishment system that was expected to have approximately a three-month payback. Eventually, frustrated by the organization’s inability even to reach a “no,” he left for another company.
A related McKinsey decision-redesign case study describes a government agency where an appeals process typically lasted seven months or more. Mapping the process exposed a fundamental problem: accountability and decision rights were unclear. Redesigning the process around greater transparency and clearer decision rights was projected to reduce the process from roughly seven months to one month.
These examples reveal the hidden cost of poor accountability design. The problem is not only that decisions are bad; it is that decisions become congested. Work starts waiting for permission, meetings accumulate around unresolved choices, senior leaders become bottlenecks, and employees protect themselves by documenting every dependency. Over time, more decisions migrate upward, and the organization becomes confused about why capable managers seem reluctant to act independently.
Accountability Requires Boundaries, Not Unlimited Freedom
None of this means that accountability requires unrestricted autonomy.
Organizations obviously need controls.
A marketing manager should not unilaterally acquire another company because she is accountable for growth. A plant manager should not ignore safety standards because he owns production. A sales executive should not disregard margin requirements because she owns revenue.
Authority must have boundaries. The better question is not whether an employee has complete authority. Almost nobody does. The better question is whether the employee has enough decision authority over the variables for which leadership intends to hold them accountable.
That produces a healthier organizational design. A leader might tell a department head: you own this outcome, you can make decisions within these financial limits, these choices require consultation, these few require executive approval, and here is when to escalate. Everything else is yours to decide.
That is real delegation because the boundary of authority is visible.
A Simple Test for Leaders
Whenever assigning accountability, leaders should examine three things together: the outcome, the decision rights, and the constraints. Start with the outcome: what exactly is this person being asked to own? Then identify the decisions that materially influence that outcome. What choices will the person need to make repeatedly to produce it? Finally, locate where authority actually resides. Can the person make those decisions, or does someone else have to approve them?
If another person retains a critical decision right, leadership has several legitimate choices. It can transfer that decision right, retain it and share accountability for the outcome, narrow the employee’s accountability to the portion the person actually controls, or explicitly name the dependency so performance is evaluated accordingly.
The move to avoid is retaining authority while pretending accountability has been delegated.
The Accountability Equation
A useful way to think about organizational accountability is:
Accountability requires responsibility + authority + visibility of results.
Responsibility gives the outcome a home. Authority gives the person enough room to influence the decisions behind it. Visibility matters because judgment only improves when people can see what their decisions produced.
When one of those pieces is missing, the assignment starts to distort. Without authority, accountability becomes ownership without agency. Without feedback, people may have room to act but no reliable way to learn from what happened.
This closely parallels the logic of Hackman and Oldham’s Job Characteristics Model: autonomy contributes to experienced responsibility, while feedback provides knowledge of results.
Good organizational design therefore does more than assign tasks.
It connects decisions, consequences, and learning.
Accountability Should Follow the Decision
Perhaps the simplest rule is this:
Accountability should follow decision authority.
If I make the decision, some meaningful portion of the consequence belongs to me.
If you make the decision, some meaningful portion belongs to you.
If we genuinely share the decision, then we must acknowledge the shared dependency rather than pretending one person independently controls the outcome.
This does not eliminate hierarchy. It makes hierarchy more intellectually honest.
The purpose of delegation is not simply to move work downward.
It is to move an appropriate amount of judgment downward with the work.
Organizations that delegate responsibility but retain judgment at the top create employees who execute.
Organizations that delegate responsibility and appropriate decision authority create leaders.
And that distinction explains why so many corporate attempts to increase accountability fail.
You cannot ask people to own an outcome while repeatedly reminding them that the decisions producing that outcome belong to someone else.
Before asking employees to become more accountable, leaders should therefore ask a more uncomfortable question:
Have we actually given them something they are allowed to own?
Sources & Further Reading
The argument above draws on work design research, decision-rights frameworks, and organizational-change writing from these sources.
- Hackman, J. R., & Oldham, G. R. (1976). Motivation through the Design of Work: Test of a Theory. Organizational Behavior and Human Performance, 16(2), 250-279.
- Hackman, J. R., & Oldham, G. R. (1980). Work Redesign. Addison-Wesley.
- Rogers, P., & Blenko, M. (2006). Who Has the D? How Clear Decision Roles Enhance Organizational Performance. Harvard Business Review / Bain & Company.
- De Smet, A., Hewes, C., & Weiss, L. (2022). The Limits of RACI-and a Better Way to Make Decisions. McKinsey & Company.
- Acharya, A., Chaudhry, K., & Maxwell, J. R. (2019). Streamline Decision-Making for a Better Customer Journey. McKinsey & Company.
- American Psychological Association. (2003). Occupational Stress and Employee Control.
- Cook, M. (2009). Pulling Away: Managing and Sustaining Change. Bain & Company.