Accountability fails when managers own outcomes but cannot make the necessary decisions.
The conversation is familiar.
A manager is asked why service performance slipped.
The team was short-staffed, but the hiring decision sat elsewhere. A failing tool needed to be replaced, but the budget sat elsewhere. Priorities changed, but the manager could not move the committed dates. A recurring process problem crossed several functions, none of which reported to the person expected to fix the outcome.
Then comes the reminder:
“You are accountable.”
Technically, that may be true.
Operationally, it may be theatre.
I have never believed accountability means making someone answer for decisions they were not allowed to make. Responsibility should create an obligation to act, explain and improve. It should not become a convenient place to deposit consequences after authority has been retained somewhere else.
If a manager owns the outcome, the operating system must give them a credible way to influence it.
That does not mean every manager should control every decision.
Financial controls matter. Security standards matter. Workforce decisions need consistency. Sales commitments can affect delivery. Changes to technology can create enterprise risk. Organizations need boundaries, specialist review and executive oversight.
But control is not the same as paralysis.
A manager may not need final authority over hiring, budget or architecture. They do need clear decision rights within their scope, defined routes for decisions outside it and response times that match the consequences they are expected to manage.
Otherwise, escalation becomes a substitute for authority.
The manager raises the issue. Another group asks for more evidence. A committee meets next week. The customer impact continues. Eventually, the manager is questioned about a result that the governance process prevented them from changing.
That is not strong accountability.
It is fragmented decision architecture.
The practical test is simple: take any outcome a role is accountable for and trace the decisions that materially affect it.
Can the role adjust priorities? Reassign work? Approve an exception? Challenge an unrealistic commitment? Access the information needed to act? Trigger a timely decision from the person who holds the authority?
If the answer is no across most of those questions, the role may carry accountability in the organization chart but not in the operating model.
This is where the seven management systems must work together.
Roles should connect outcomes to usable decision rights. Processes should define approval and exception paths. Technology should put evidence in the hands of the people expected to act. Meetings should resolve decisions, not merely acknowledge dependencies. Reporting should expose blocked authority alongside missed results. Analytics should show the operational cost of delayed decisions. Continual improvement should remove recurring approval bottlenecks instead of teaching managers to navigate them repeatedly.
Accountability matters.
But accountability without authority does not create ownership. It creates frustration, delay and defensive reporting.
Before telling a manager to own the outcome, leaders should ask whether the organization has allowed that manager to manage it.
If responsibility and authority are pulling in different directions in your organization, The 7 Essential First-Line Management Systems offers a practical way to reconnect roles, decisions and execution. You can explore the deeper management-system approach at www.imadlodhi.com/flm1.
