Decision Rights Are More Important Than Reporting Lines

Reporting Lines and Decision Rights Solve Different Problems

A reporting relationship establishes a formal managerial connection. It helps determine who evaluates performance, who provides direction, how resources are allocated, and who is responsible for leading a person or organizational unit. Those are consequential design choices, but many important decisions do not fit neatly inside one reporting relationship.

A pricing decision may require Sales, Finance, Product, and Legal. A hiring decision may involve a business leader, HR, Finance, and recruiting. A product investment may require Technology, Operations, Commercial leadership, and executive governance. A customer exception may depend on expertise and judgment distributed across several parts of the organization. The organization chart identifies where those participants sit. It does not automatically establish what happens when they disagree.

This is where organizations often allow hierarchy to become the decision system. When participants cannot determine whose judgment governs, the issue moves upward until it reaches someone with enough positional authority to force resolution. The decision eventually gets made, but the organization has learned something dangerous: ambiguity can be solved through escalation rather than through design.

If that pattern repeats, senior leaders gradually become integration mechanisms for choices the organization should be capable of resolving elsewhere. Their calendars fill with operating decisions, governance forums expand, and managers become increasingly cautious because consequential choices appear to require senior visibility.

Leadership overload can then be interpreted as a span-of-control problem. Sometimes it is. In other cases, the organization has simply failed to establish a decision system capable of operating independently of hierarchy. Changing reporting lines under those conditions can move the bottleneck without removing it.

Why Hierarchy Becomes the Default Decision System

Hierarchy remains valuable because it offers a reliable mechanism for resolving disagreement. When lower levels cannot reconcile competing perspectives, an issue can move upward to a leader with broader authority and context.

The problem emerges when escalation becomes routine rather than exceptional. Several organizational forces encourage that outcome. Employees usually know who their manager is even when they do not know who owns a particular decision, so the reporting chain becomes the natural route when authority is ambiguous. Escalation can also feel safer than independent action, particularly when consequences for a wrong choice are clear while expectations around delegated judgment remain uncertain.

Leadership behavior can reinforce the pattern. A leader may tell managers they have authority, then revisit or reverse decisions whenever the result differs from what the leader personally would have chosen. Over time, managers learn that formal delegation is conditional.

Research on delegation credibility helps explain this problem. Stea, Foss, and Foss argue that organizations need mechanisms that make delegated authority credible because managers may be tempted to reclaim control when uncertainty rises. Delegation provides limited value when employees expect authority to disappear whenever decisions become difficult.

An organization can therefore advocate empowerment while operating through approval. The language says, "You own the decision." The experience says, "You own it until someone more senior disagrees." No reporting-line change resolves that contradiction.

Formal Authority and Real Authority Are Not the Same

One of the most important distinctions in the research on delegation is between formal authority and real authority. Formal authority is the right the organization says a person possesses. Real authority is the authority that person can actually exercise.

The difference becomes visible in ordinary organizational language. A manager says, "Technically, I can approve this, but I would never do it without checking with my VP." A project leader says, "The steering committee is advisory, but nothing moves without their support." A business-unit leader says, "I own the result, but Corporate has to approve most of the choices that drive it." None of those statements may appear in the governance model. All of them describe the operating decision system.

Dobrajska and colleagues' study is particularly relevant because it examined allocation of both formal and real authority and showed that decision-relevant knowledge and managerial expertise influence how delegation actually operates. The implication for leaders is significant: documenting authority is only one part of designing authority.

A delegated decision can continue escalating because the owner lacks necessary information. Authority can remain behaviorally centralized because senior leaders intervene repeatedly. A manager can hesitate because organizational consequences for mistakes are uncertain. A governance group can acquire informal veto power because leadership never distinguished input from approval.

The formal decision model and the operating decision model can therefore become very different systems. The real test of decision rights is not whether authority appears in a matrix or governance document. It is whether people understand the authority, possess what they need to exercise it, and can act without routinely seeking permission from someone who supposedly no longer owns the choice.

Comparing formal authority with the operating decision system reveals a condition that can remain hidden when leaders examine only the formal organization. The reporting structure shows where accountability and managerial authority are intended to reside, while the operating decision system reveals who actually decides, influences, supplies information, establishes boundaries, triggers escalation, and owns consequences.

The difference becomes consequential when formal and real authority materially diverge. Decisions can slow, escalation can increase, accountability can blur, and organizational capacity can be consumed reconciling the difference. TQG describes this potential capacity loss as Authority Drag.

When Everyone Has Input, No One May Have Authority

Modern organizations rightly value collaboration. Complex choices frequently require multiple forms of expertise, and decisions made without appropriate input can create avoidable risk. The problem is that organizations can confuse participation in a decision with ownership of a decision.

A decision may involve eight functions, but involvement does not mean all eight functions should possess equal authority. If every stakeholder implicitly expects consensus before action, collaboration can become a hidden veto system.

This can happen without any formal requirement for unanimity. A leader may technically own the decision but hesitate to proceed because another function strongly disagrees. A committee may officially provide input while participants behave as though agreement is required. Leaders may describe a decision as shared, leaving employees uncertain about what happens when the shared owners reach different conclusions. The organization becomes good at gathering perspectives and weak at resolving them.

This produces a familiar pattern. More meetings are added because alignment is insufficient. More stakeholders join because someone was omitted previously. Decisions move into governance because working teams cannot resolve disagreements. Senior leaders intervene because no lower-level mechanism has legitimate authority to close the issue.

The answer is not less collaboration. It is clearer differentiation between input, influence, authority, and accountability. A strong decision system allows the right people to contribute without turning every contributor into a decision owner.

Decision Rights and Accountability Must Be Designed Together

Decision rights are often discussed as an empowerment issue, but authority cannot be separated from accountability. Giving someone responsibility without sufficient authority creates frustration. Giving someone authority without clear accountability creates risk. The two must operate together.

Role-ambiguity research provides useful evidence for why this clarity matters. Tubre and Collins' meta-analysis found a negative relationship between role ambiguity and job performance, demonstrating that unclear expectations and responsibilities are not simply administrative inconveniences.

Decision ambiguity is narrower than general role ambiguity, but the organizational logic is related. People perform more effectively when they understand what they are responsible for, what discretion they possess, and where their authority ends.

Consider a leader who is accountable for customer profitability but cannot approve pricing exceptions, change service levels, influence product commitments, or resolve delivery tradeoffs. Accountability has been assigned more cleanly than authority.

The opposite problem also exists. A manager may possess broad discretion over staffing or investment without clear expectations regarding the outcomes that authority should support.

Strong decision architecture aligns the right to choose with the obligation to own the consequences of the choice. That alignment is more important than placing two roles beneath the same executive and assuming hierarchy will reconcile the rest.

Escalation Is a Design Signal

Escalation is not inherently evidence of organizational failure. Some decisions should move upward. A choice may create significant enterprise risk, exceed financial thresholds, affect several business units, create legal exposure, or require tradeoffs that only senior leadership has the authority and perspective to resolve.

The more useful question is whether the organization can distinguish necessary escalation from habitual escalation.

When routine issues repeatedly move upward, leaders should examine the reason rather than merely telling employees to "take more ownership." Repeated escalation can indicate unclear decision ownership, insufficient authority, missing information, weak capability, low trust, contradictory goals, or decision boundaries that no longer fit the business. It can also indicate a behavior problem. Someone may have appropriate authority and capability but still avoid making difficult choices. The important point is that escalation is evidence.

A senior leader who becomes involved in the same class of decision repeatedly is seeing a pattern in the organizational system. The leader can continue resolving each case or investigate why the decision cannot reliably close where the organization says it belongs.

This reframes leadership overload. Some executive overload is created not by the quantity of work leaders formally own, but by the amount of unresolved decision ambiguity the organization sends upward. The executive calendar can therefore become a diagnostic artifact. Repeated categories of escalated decisions tell leaders where decision architecture may be weak.

Centralization and Decentralization Are the Wrong Binary

Organizations frequently frame decision design as a choice between centralization and decentralization. That framing is appealing because it simplifies the issue, but it hides an important reality: different decisions should often reside in different places within the same organization.

Koester and Xia's recent findings demonstrate this clearly. Delegating hiring and customer-related sales and marketing decisions was positively associated with performance in their sample, consistent with the value of local tacit information. Greater delegation of capital investment and new product introduction decisions showed a negative relationship, consistent with the need for broader coordination and oversight.

The implication is not that these exact allocations should apply to every organization. It is that delegation is decision-specific.

A routine customer recovery decision may belong close to the customer because local context matters and delay destroys value. A major capital allocation decision may require an enterprise perspective because resources and consequences extend across the organization. A cybersecurity exception may require centralized authority because risk extends beyond the local team, while a scheduling decision may belong with the manager closest to the work.

The organizational question is not whether authority should generally move up or down. It is whether authority is located where the requirements of the decision can best be satisfied. That requires more sophisticated thinking than simply flattening the organization or declaring a philosophy of empowerment.

Authority Should Follow the Requirements of the Decision

A useful way to think about decision rights is to begin with the decision rather than the hierarchy.

Leaders need to understand what knowledge the decision requires, where that knowledge resides, how quickly the decision must be made, how broad the consequences may be, how reversible the choice is, how much coordination is required, what risk must be governed, and who will ultimately be accountable for the outcome. Those considerations begin to reveal why the appropriate location of authority varies.

Dobrajska and colleagues found that specialization of decision-relevant knowledge, the match between required knowledge and managerial expertise, and information-processing intensity were associated with how authority was delegated across levels of hierarchy. This reinforces the idea that decision authority should be connected to the knowledge and processing requirements of the choice rather than assigned solely according to organizational level.

Authority should be designed around the requirements of the decision, not automatically around the seniority of the person making it.

This shifts the design conversation away from a broad preference for more or less delegation. It asks leaders to consider whether the location of authority makes sense for the specific decisions the organization needs to make.

Authority Drag

When decision rights and decision requirements are poorly aligned, organizations can experience a form of friction that TQG describes as Authority Drag.

Authority Drag is the organizational capacity consumed when a decision cannot close efficiently because the authority required to act is unclear, misplaced, conditional, conflicting, or separated from the knowledge and accountability necessary to exercise it.

The visible symptoms vary. Decisions circulate through multiple leaders. Employees prepare increasingly elaborate materials because every new reviewer asks for different information. Governance meetings become approval forums. Managers wait for executives who have limited context but hold positional authority. Decisions are revisited because participants were unclear whether the previous choice was actually final.

The organization may interpret each delay as a separate issue. Viewed together, however, those delays may reveal a common pattern in how authority operates. The concept does not imply that fast decisions are always better. Some choices deserve deliberation and multiple safeguards. A consequential decision made quickly by the wrong person with inadequate information is not evidence of good organizational design. The issue is whether the time and coordination consumed by the decision are proportionate to what the decision actually requires.

This creates a different question for leaders:

How much organizational capacity is being consumed because authority is not aligned with the requirements of the decision?

That question shifts attention away from individual delays and toward the organizational system producing them.

Once leaders understand where authority actually operates, the next question is where it should reside.

The TQG Decision Authority Profile proposes that different consequential decisions can appropriately require different authority structures. Decision-relevant knowledge, consequence and risk, interdependence, and accountability provide a way to examine that question without reducing organizational design to a generic choice between centralization and decentralization.

The contrast between customer recovery and enterprise investment demonstrates this principle. A decision whose knowledge, consequences, interdependencies, and accountability are primarily local can reasonably point toward authority closer to the work. A decision involving distributed knowledge, broad consequences, significant interdependence, and enterprise accountability can justify broader authority or governance.

The point is not that every decision fits neatly at one end of a continuum. It is that every consequential decision has a unique authority profile. Aligning authority with that profile can reduce unnecessary escalation, clarify accountability, and improve decision flow.

Decision Rights Need Boundaries, Not Constant Permission

Empowerment is sometimes framed as the removal of control. That is not what strong decision architecture requires.

People can exercise substantial autonomy when the organization has clarified the boundaries within which that autonomy operates. Financial limits, risk thresholds, strategic principles, customer commitments, legal requirements, and escalation triggers can all establish guardrails without requiring a superior to approve every individual choice.

This distinction matters because approval and governance are not synonymous. Governance should help the organization determine which decisions require oversight and what boundaries protect the enterprise. Approval is only one possible governance mechanism.

When organizations rely too heavily on approvals, they consume managerial attention continuously. When they rely on clear boundaries, leaders can govern classes of decisions while allowing individual choices to occur closer to the relevant information.

The design challenge is determining when boundaries are sufficient and when explicit approval is genuinely required. That distinction depends on the nature and consequence of the decision rather than on a universal preference for either control or autonomy.

Decision Rights Fail When Information Does Not Follow Authority

Delegating authority without access to information creates only the appearance of empowerment. A manager may have the right to decide but lack relevant financial information. A business leader may own a customer decision without understanding operational constraints. A functional leader may be accountable for workforce choices without sufficient visibility into future demand. The authority is formally present, but the capacity to exercise it well is not.

This is why decision rights and information architecture need to be considered together. Moving decisions closer to local knowledge can create value when that knowledge is difficult to transfer upward, but local decision makers may also need enterprise information to understand consequences beyond their immediate context.

The strongest decision design therefore does not simply move authority to the person with the most information. It asks what information the decision requires and how the organization will ensure the decision owner can access it. Authority without information produces guessing. Information without authority produces frustration. The organization needs both.

How to Know Whether Decision Architecture Is Working

A decision-rights redesign should be evaluated by changes in decision behavior, not by whether a governance document was completed.

The measures will depend on the decisions being examined, but leaders can look for several types of evidence. Are important decisions closing at the level where they are intended to close? Has unnecessary escalation decreased? Are decision cycle times appropriate to the consequence and complexity of the choice? Are decisions being repeatedly reversed or reopened? Do people understand where their authority begins and ends? Has executive involvement shifted away from routine operating decisions toward issues that genuinely require enterprise judgment?

These measures should not be treated in isolation. A reduction in decision time accompanied by poorer quality or increased risk is not necessarily improvement. A decline in escalation may be positive, or it may indicate that employees are making decisions without appropriate oversight. The objective is not to maximize speed. It is to improve the alignment among authority, information, accountability, coordination, and consequence.

Organizations should therefore know whether their decision architecture is producing the behavior it was designed to produce. If leaders can describe where authority is documented but cannot explain how consequential decisions actually move through the organization, they understand the formal system. They do not yet know whether that system is working.

What Great Organizations Do Differently

Great organizations treat decision rights as a deliberate part of organizational design rather than assuming reporting relationships will resolve authority automatically.

They distinguish contribution from decision ownership. Multiple perspectives can improve a choice without requiring every contributor to approve it. The organization can therefore preserve collaboration while maintaining a clear path to closure.

They also recognize that authority should vary by decision. Local knowledge may justify distributing some choices closer to customers or operations, while enterprise risk, interdependence, or capital consequences may justify concentrating others.

These organizations make delegation credible. When managers receive authority, leaders avoid routinely reclaiming it simply because they would have chosen differently. Intervention is reserved for breaches of agreed boundaries, unacceptable risk, missing capability, or decisions that genuinely require a different level of authority.

They design information alongside authority. Decision owners receive the context needed to exercise judgment, while governance provides clear boundaries and escalation conditions rather than relying primarily on repeated approvals. They also treat escalation as evidence. If the same decisions repeatedly travel upward, leadership investigates the underlying condition instead of indefinitely absorbing the work. Most importantly, great organizations understand that the objective is not maximum decentralization. It is appropriate authority. Decision rights are placed where the organization can combine the relevant knowledge, judgment, accountability, coordination, and governance necessary to produce a strong outcome.