Leadership & Decision-Making · 8 min read
Many founders who think they've effectively delegated decision-making have done so in a more nuanced and costly way than they realize. They have merely outlined the distribution, announced that teams are empowered, created org charts indicating ownership, and held off-site meetings to clarify responsibilities. Nonetheless, they remain the primary person their teams turn to before acting.
The difference between a declared decision system and an operational one is where scaling companies often waste the most time, lose their best operators, and fall behind competitively, often quietly and long before anyone realizes what is truly happening.
This issue is known as a decision-rights problem. Nearly all scaling companies face it, but few have identified it with clarity.
The calendar tells you what the org chart won’t
The org chart identifies owners, assigns accountability, outlines reporting lines, and allocates titles. However, it doesn't reveal where decisions truly result.
The founder’s calendar can.
Instead of focusing on official meetings like board meetings or regular one-on-ones, pay attention to what surrounds those events: the pricing exceptions that required a final decision, vendor negotiations initiated by others but not finalized, or hiring choices two levels below the executive team that still needed discussion before proceeding. These are the decisions the org chart suggests should be made by others, but the calendar indicates they are happening here.
When a company is small enough that the founder can oversee nearly every major decision, proximity serves as a substitute for formal design. The individuals with the relevant information, authority, and accountability are a tight-knit group, close to one another, and able to act quickly. However, this isn’t a true decision-making system; it relies on luck and timing. Such an approach cannot sustain growth.
As a company expands with more layers, regions, and complexity, the individuals most knowledgeable about specific decisions are often not the ones empowered to act. Information moves outward to the edge—such as the account manager, operations lead, or regional director—who have insights that the weekly report misses. Meanwhile, decision-making authority remains centralized. This creates a continuous flow cost: information needs to travel up the hierarchy before actions can be executed downward, making the process slower than the market demands.
The org chart does not show this. The calendar does.
Responsiveness is not a decision system
Most founders see their accessibility as a form of discipline. Their phone is constantly on, and answers come within twelve minutes. No one must wait long, which seems like leadership. However, the organization often perceives it differently.
When the founder is the quickest route to a decision, the organization clearly learns this. Teams form habits around seeking their input. As a result, escalation becomes more dependable than decision-making. Waiting is seen as more logical than acting. Those responsible for their areas still technically own them, but they have come to see ownership as conditional and have adjusted their behavior accordingly.
The issue is not the founder’s availability, but what it subsidizes. Each quick response to an escalation alleviates the pressure that would otherwise push the organization to create alternative solutions. The more rapidly answers are provided, the less incentive there is to develop independent decision-making capacity.
Economists Michael Jensen and William Meckling, writing about the economics of organizational structure, clearly state that decision-making is most effective when authority is held where the relevant knowledge resides. When decision-making power is centralized at the top, but essential insights, such as those of an account manager who has interacted with a customer three times this quarter, or an operations leader monitoring real-margin pressures, are held at the edge of the organization, there is a constant need to transfer information between these points. This transfer incurs costs in terms of speed, accuracy, and the confidence of those expected to make decisions, but through experience, have learned not to.
Responsiveness is a workaround. A workaround maintained long enough becomes the system.
What real authority actually requires
Redesigning the org chart is often the initial step when decision-rights issues are identified. However, it is rarely enough by itself. The chart indicates who should decide, but it doesn't show whether they have the resources or authority to do so.
Real authority, the kind that genuinely holds in practice rather than just on paper, depends on four essential aspects: having the necessary information to assess the situation clearly, possessing the formal right to act, being accountable for the outcomes, and establishing a visible boundary that signals to others to keep out. When all four elements are in place, judgment can confidently reside below the executive team. If anyone is absent, judgment tends to shift upward again, regardless of the organizational structure, because the decision-makers recognize that they lack what they need to make sound decisions.
The individual who possesses information but lacks formal authority tends to ask for permission before acting and learns to wait. The one with formal authority but no information makes decisions that seem arbitrary to those involved closely, undermining trust. The person who has both but lacks true accountability makes inconsistent choices, as they have no obligation to own the results. Meanwhile, the individual who holds all three, but whose decisions are often revisited afterward, learns that their authority is only on paper; the real decisions are made elsewhere.
This pattern represents the most common single point of failure in growing companies. The organization relies heavily on one individual being available, willing, and able to make critical decisions. All other parts of the system depend on this structural dependency.
Research tracking thousands of firms across countries by economists Nicholas Bloom, Raffaella Sadun, and John Van Reenen confirms that genuinely decentralized decision-making, where authority is held at the appropriate levels, is linked to significantly better firm performance. The key term is "genuinely." Nominal decentralization, where the organizational structure suggests decentralization, but the decision-making override pattern remains centralized, does not lead to the same benefits. Instead, it creates confusion, hedging, and organizational behaviors that, from an external view, may appear to be cultural issues, but are structural problems.
The speed penalty — and the customer who feels it first
When authority and information are isolated, organizational speed decreases. While this is a common topic of discussion, less often considered is that the first and most costly impact appears not within the organization itself, but in the customer relationship.
Decisions that should be handled by the director are escalated to the VP, and those for the VP go to the CEO. This chain of escalation causes the executive team to spend time on calls they are least suited for, as they are the furthest from the customer, contract specifics, and operational details that really determine effective answers. Every level of escalation introduces delays, and each translation layer diminishes information accuracy.
The account manager who might have responded to a customer's question on Tuesday first consults her manager. The manager then checks with the VP, who arranges a call. By the time the response is received, the opportunity has diminished, the customer has noticed the delay, and the account manager realizes she should have asked for guidance beforehand. This experience subtly influences the organization's future behavior.
Customers notice this before any internal metric detects it. Response times slow down, and account teams struggle to provide clear answers to questions that should be within their scope. Commitments made by one part of the organization are not visible to the team responsible for fulfilling them. None of this shows up on a revenue dashboard until it has become a consistent pattern. By then, the underlying issue had been ongoing for months.
Research examining firms across the 2008–09 global downturn shows that companies with truly decentralized decision-making—where authority, information, and accountability were aligned before conditions worsened—performed much better than their more centralized counterparts in the most affected sectors. Relying on a small top group to make crucial decisions creates structural fragility that remains hidden during stable times but becomes costly in challenging conditions.
The layer that tells you everything
The most evident sign of a decision-rights issue is not at the executive level but rather one or two levels down—in the managers and directors who were initially told they owned their domains but have since discovered, through experience, that this ownership is conditional.
These leaders remain visibly engaged; they show up and execute and have strong business knowledge. However, they no longer make decisions involving significant trade-offs because they fear being overruled more than the effort of waiting. They also refrain from raising concerns immediately, as past concerns were addressed without their involvement. Gradually, they have shifted their focus from making decisions to just documenting them, moving from actively making choices to merely recording that the decision was not theirs.
This isn't resistance; it's adaptation, which incurs costs that aren't reflected in any performance review.
When leaders become silent, the organization forfeits more than just their opinions; it loses its early-warning system. These signals, indicating issues such as contract drift, shrinking margins, or a customer's waning patience, remain on the periphery rather than reaching those who can address them. The information is there, but the structure isn't designed to transmit it effectively.
A practical way to assess progress is to consider the leaders who have left in the past two years. How many of them, when departing, said something like: “I was never quite sure what I was actually empowered to do”? This question is rarely recognized as a decision-rights issue during exit interviews, yet it almost always is.
Three questions before you restructure anything
When decision-rights issues are finally identified, the initial reaction is often to reorganize reporting relationships for change, establish a governance layer, or implement a clearer delegation framework. Sometimes this is the correct approach. However, it is rarely the best first step. Jumping into restructuring without proper diagnosis often just recreates the same authority problems within a new organizational chart.
Three honest answers to these questions better define the actual decision system than any updated org chart.
Where should your focus truly be? Over the past thirty days, identify the major decisions that required your input, not because your judgment was exceptional, but because there was no obvious alternative. The quantity and pattern of these decisions reveal more than any delegation review.
What information reaches you, and when? When issues occur at the customer or operational level, does the relevant signal arrive promptly with sufficient detail for a timely response? Or does it arrive two weeks later, diluted into a summary that loses its original texture and urgency? The quality of the information received at the highest level depends directly on how safe it is to send it.
What occurs when someone decides without your input? When a director or VP acts independently without consulting their superiors, does it stand? Or is it frequently reviewed in a manner that encourages them to verify next time? The answer reveals what the organization truly understands about where authority resides, separate from what the org chart indicates.
These questions are not hypothetical. I ask them in the initial conversation, before any restructuring is considered. They don’t need a formal program or external help to answer. Instead, they require a founder or CEO willing to answer honestly without defending the current system.
The environment surrounding your decisions generates results, regardless of whether you've intentionally designed it. Elements like the organizational chart, delegation framework, and empowerment language from the last offsite are not decision systems; they merely reflect intentions. The true decision system is the organization's accumulated knowledge from ongoing experiences about who can decide what and under which circumstances. This learning occurs daily, and the key question is which lessons it is currently reinforcing.
Companies that successfully transition from founder-led decision-making to a functioning decision system don't achieve this through a simple restructure. Instead, they treat the design of decision processes as a deliberate problem to solve, applying the same rigor as they would to product choices or capital allocation. They establish the four essential conditions, verify their reality by observation rather than trusting the matrix's predictions, and maintain this practice continuously, since the gap between formal and actual authority often reemerges if unchecked.
The upcoming week reveals your current situation. The unnecessary calls, leaders who consult before acting, and customers perceiving slower response times are all signals pointing to a design issue. The key question is whether you will tackle this while it remains a choice.
Frequently Asked Questions
How do I know whether my company has a decision-rights problem or just normal growth pressure?
Growth pressure reduces when the pace of change slows, but a decision-rights problem persists. If decisions keep returning to the same one or two individuals despite adding more leaders, this indicates a structural issue. The key test is whether authority genuinely resides where the org chart indicates or if it repeatedly shifts upward. If you are making the same decisions this quarter as you did last quarter, even when another person was supposed to be responsible, the problem is embedded within the system, not just temporary or seasonal. Is this a delegation problem? Should I just push more authority down? Delegation is only one aspect. Merely distributing decision rights without sharing the relevant information, accountability, and boundaries typically fails. The person receiving the decision ends up responsible for something they cannot fully understand or defend, leading them to return it. Effective design involves aligning all four elements—decision rights, information, accountability, and boundaries, rather than just reallocating titles. We already have a decision-rights matrix. Why isn’t it working? Most matrices specify who should decide, but they seldom detail what each person needs to make informed decisions, what they will retain if the outcome is unfavorable, or where their authority clearly concludes. Without these layers, the matrix remains just a document about intentions. People instinctively sense the difference between a mere document and an effective system, even if they can't articulate it. If the matrix is being bypassed, the more relevant question is not how to enforce it, but what elements are missing from it. At what stage of growth does this typically become a problem? Visibility typically occurs after the founder can no longer personally oversee all critical decisions but before the company develops its first leadership layer that manages other leaders. The specific headcount at this stage varies, but the pattern remains consistent. If the senior team has expanded and the founder’s schedule has not eased, the company is probably in this phase. Does fixing decision rights require a reorganization? It's rare to make a restructuring as the initial step. Typically, the biggest mistake is reorganizing before understanding the root issue, which often leads to the same authority problems reappearing in a new chart. A more effective first step is to honestly assess where decisions are made and identify barriers that prevent them from landing correctly. Sometimes, the redesign involves changing the structure itself. More often, it focuses on clarifying authority, access to information, and consequences within the existing framework. How do I raise this with the board without signaling that I’m the bottleneck? Frame this as enterprise value and execution risk. Sophisticated boards, investors, and operating partners tend to discount firms relying heavily on a single decision-maker—described as key-person risk or bench depth, but the core issue remains the same. A founder who raises this concern early, with a clear understanding of what a well-structured decision system should resemble, is not showing weakness. Instead, they are demonstrating awareness of the company's current state and its future requirements.
If this resonates with where your organization is today, we should talk.