A manager spends three weeks getting agreement on a decision that takes an executive five minutes to make.
The manager ran the meetings, gathered context, wrote the options paper, chased stakeholders, revised the recommendation, and documented the risks. They were responsible for progress. They could not close the decision.
This role appears everywhere in scaled organizations. The title says manager. The work is coordination. The authority sits elsewhere.
Managers without authority create drag because every meaningful choice becomes a negotiation. They cannot allocate resources, override disagreement, enforce priorities, or accept risk on behalf of the system. Their main tool is persuasion. Persuasion is expensive when used as the default mechanism for execution.
What Authority Actually Provides
Authority is decision closure.
A manager with authority can hear the arguments, choose a direction, and commit the team. People may disagree. The decision still moves. The work has a point of closure.
Authority also includes resource control. Budget, staffing, time, and priority are the levers that turn a decision into action. Without those levers, a manager can recommend work but cannot make it happen.
The third component is consequence. If a manager can affect performance reviews, promotions, role assignments, or continued participation, decisions carry weight. Without consequence power, compliance depends on goodwill or shared urgency.
Many organizations remove these components and keep the coordination burden. The manager becomes a facilitator with a delivery target. They are accountable for movement across teams that are free to ignore, delay, or reinterpret the request.
The Consensus Loop
A cross-functional project needs priority across three teams. Each team agrees the project matters. Each has existing commitments. The manager cannot reassign capacity.
The first meeting surfaces the conflict. Team A needs platform work first. Team B says customer commitments cannot move. Team C says its dependency comes before both. No one is wrong.
The manager schedules one-on-ones to understand constraints. They produce a sequencing proposal. One team rejects it because the delay would break a promise made by sales. The manager revises the plan. Another team rejects the revision because it creates technical risk. The manager escalates softly, asking leaders to align.
Weeks pass. Everyone is collaborating. No one has decided.
Eventually the issue reaches a senior leader with enough authority to reorder priorities. The call is made quickly because the leader can absorb the political cost and commit resources. The preceding coordination had value as context-gathering. Much of it also existed because the manager lacked the power to close the trade-off.
The Negotiation Tax
Every decision without authority carries a negotiation tax. The tax is paid in meetings, pre-reads, stakeholder management, follow-up notes, and repeated reframing of the same issue for different audiences.
The tax grows with the number of veto points. Two stakeholders may resolve a disagreement quickly. Six stakeholders across different functions can keep a decision open for weeks, especially when each has local incentives to protect.
The cost is easy to hide. It appears as alignment work, governance, collaboration, and due diligence. These labels sound productive. Sometimes they are. But when the same conversations repeat because no one can decide, the organization is burning time to compensate for missing authority.
This is why managers without authority are often busy and ineffective at the same time. Their calendars are full because the system has made them responsible for resolving conflicts by influence alone.
Why Organizations Create These Roles
The arrangement feels attractive. It promises coordination without more hierarchy. A program manager can organize work across functions while functional leaders keep control. A project lead can own delivery without disrupting reporting lines. A matrix manager can create alignment without changing authority.
This preserves local power. Functional leaders keep their people. Executives keep escalation rights. Teams keep vetoes over their domains. The coordinating manager absorbs the complexity created by that design.
The organization gets an owner for the problem without giving that owner the levers. When progress slows, it can ask the manager for better stakeholder management. The deeper issue stays untouched: the role was designed to coordinate decisions it cannot make.
The Drag Compounds
One manager without authority is survivable. A company full of them becomes slow by design.
Every cross-team initiative needs alignment. Every alignment process generates meetings. Every meeting produces partial agreement and more follow-up. Every unresolved decision escalates upward, where senior leaders become bottlenecks for issues that should have closed closer to the work.
The system then interprets senior leadership overload as a need for better prioritization forums. More forums are created. The managers attend those too.
Drag compounds because the organization adds coordination capacity instead of decision capacity.
How To Tell Whether The Role Has Authority
The test is direct:
- Can the manager commit people or budget?
- Can they choose between competing priorities?
- Can they say no to scope?
- Can they override a stakeholder inside a defined domain?
- Are they accountable for outcomes produced by those choices?
If the answer is mostly no, the role is coordination, regardless of title.
Coordination roles can be valuable when the organization is honest about them. They gather context, maintain cadence, expose risk, and keep complex work visible. They should not be treated as accountable owners of outcomes determined by decisions they cannot make.
Reducing The Drag
The repair is not giving every manager unlimited power. The repair is matching authority to the decisions they are expected to close.
A program lead may need authority to sequence work inside a committed initiative. A product manager may need authority to trade scope against dates. An operations manager may need authority to pause releases that violate reliability standards. Each right can have thresholds and escalation paths.
The point is to avoid making negotiation the default execution engine.
Managers without authority create drag because they are asked to convert disagreement into progress without the tool that ends disagreement. The organization pays for that missing tool in calendars, delays, and decisions made too far from the work.
