If every important decision in your business eventually lands on one person’s desk, you do not have a delegation problem alone. You have a business design problem. And the larger the organization becomes, the more expensive that design can be.
Leaders often talk about scaling in terms of revenue, technology, and new opportunities. Those things matter, but they cannot compensate for an operating model that depends on one person interpreting every priority, settling every disagreement, and approving every move. Decision-making authority is not an administrative detail; it determines whether a business can turn its expertise into consistent execution.
This issue came into focus during my conversation with Sara Frasca, a business coach at Point Northeast and former General Mills leader. Sara has worked across corporate and entrepreneurial environments, and her experience points to a useful contradiction: the structure many leaders think will constrain creativity can actually give people the clarity they need to solve problems and move forward. The trick is building a structure that supports judgment rather than replacing it.
A successful business can still be built around a bottleneck
Many founders become the center of decision-making for a perfectly understandable reason. In the early days, they know the customers, understand the work, and carry responsibility for keeping the business alive. Being involved in everything can feel like the most practical way to protect quality and keep things moving.
Then the company grows, and the habits that helped it survive become harder to distinguish from the habits holding it back. Employees learn to bring questions to the founder because that is how decisions have always been made. The founder stays involved because no one has clearly defined which decisions belong elsewhere.
Sara described an architectural firm with approximately $30 million in annual revenue that had developed a substantial professional practice but still operated much like a hub and spoke. According to Sara, decisions routinely came back to the owner, and people throughout the organization felt they reported to him. That is not a criticism of the owner’s expertise; it is a sign that the business had outgrown the decision structure built around it.
The lesson is not that every founder should step away from meaningful decisions. It is that leaders need to distinguish between decisions that require their judgment and decisions that reach them because the organization has no clear alternative. When those two categories get mixed together, the business pays for senior attention that could be better spent elsewhere.
Decision-making authority starts with more than an org chart
One of the changes Sara described at the architectural firm was creating an organizational chart that showed reporting relationships, roles, responsibilities, and accountability. People gained clarity about where they fit and how decisions could move through the business. What sounds like a basic management tool became useful because it made the organization’s responsibilities visible.
An org chart alone will not transform a business. A diagram can tell me who reports to whom and still leave me wondering who can approve a client exception, resolve a conflict between departments, or change a priority when the original plan stops making sense. A good operating model answers those questions before every issue becomes an executive meeting.
That means leaders need to make accountability specific. For a recurring decision, identify who owns it, who needs to contribute, what boundaries apply, and what circumstances require escalation. Then make sure the people involved understand the business context well enough to use that authority responsibly.
Notice what is missing from that description: permission to operate without consequences. Accountability is not a decorative word to add to a job description after authority has been withheld. If someone is responsible for a result but must seek approval for every meaningful choice, the business has assigned responsibility without providing a workable way to exercise it.
Structure should make innovation possible, not bury it
Sara’s perspective was shaped in part by moving from General Mills into an entrepreneurial business and then returning to the corporate environment. She described coming back more willing to question established practices and ask whether another approach might work. That shift matters because a process should earn its place by helping the business accomplish something, not by surviving long enough to become tradition.
At the same time, Sara argued that innovation and creative problem-solving need solid fundamentals to lean against. I agree. If people do not understand the rules, responsibilities, or intended outcomes, challenging the status quo becomes a guessing game. You cannot make an informed decision about which rule to change if nobody can explain why it exists.
The answer is not to document every breath an employee takes. It is to establish enough consistency that teams can see where the work breaks down, where a customer experiences friction, and where an established practice no longer serves its purpose. Then they can propose a change against a shared understanding of the current process.
This is where I return to an equation I use in my own practice: people plus process, multiplied by technology, can support growth and scale or improve effectiveness and efficiency. None of those elements operates in isolation. Technology applied to an unclear decision process may simply move confusion around faster, while a well-designed process still needs people who have the authority and context to act.
Founder dependency creates risk beyond the founder’s calendar
A leader who makes every decision may feel indispensable. That feeling can be flattering right up until the moment the business cannot function comfortably without them. Dependency concentrates knowledge, judgment, and risk in one place, while the people expected to support the business may not have enough room to develop their own judgment.
Sara shared a personal milestone from the architectural firm after the organizational chart and other changes had time to take root. The owner told her he had been able to take a family vacation and disconnect from the business. Her account did not isolate that outcome as the result of the chart alone, and she was clear that meaningful change was not instantaneous.
That distinction matters. A vacation is not a financial statement, and it should not be presented as proof of a specific revenue gain. It can, however, be a meaningful indicator that an owner is no longer required to personally manage every issue. In my work, I use a related question with owner-founders: could you comfortably step away for 30 days and trust that the business would be fine?
That question is a diagnostic, not a universal requirement to take a month off. The useful follow-up is to identify what would make the answer uncomfortable. Which decisions would stop, which customer commitments would be at risk, and which relationships depend on knowledge that exists only in the leader’s head?
Give people context, then test the boundaries
Delegation fails when a leader hands off a task but keeps the information needed to make a sound decision. A manager cannot prioritize well if they do not understand the customer commitment, the business objective, or the tradeoffs leadership is willing to accept. Telling someone to “own it” is not a substitute for making those things clear.
Start with one recurring decision that routinely travels too far up the organization. Agree on the intended outcome, name the person responsible, and define when that person should bring the issue back for support or escalation. Review a few decisions together afterward, not to reclaim control, but to see whether the boundaries and available information were useful.
The review should include the people doing the work and, where appropriate, those serving the customer. Ask where they encountered uncertainty, whether the decision reached the right person, and what information arrived too late. A faster decision is only an improvement if it also supports the outcome the business and its customers need.
Leaders can measure this work without pretending that every benefit will show up immediately in a revenue report. Track how long a recurring decision takes, how often it is escalated, and whether teams have to revisit it because responsibilities or information were unclear. Pair those operational measures with feedback about customer and employee experience, then adjust the process rather than treating the first design as permanent.
Honest feedback is part of the operating system
Decision rights will not fix every bottleneck if leaders cannot see their own contribution to the problem. Sara described giving clients candid observations, including when a leader’s attention to too many new ideas may be pulling a team in competing directions. She also emphasized that her observations are a perspective, not an infallible verdict.
That distinction is important. Constructive feedback is not a license to pronounce judgment and walk away. It is an invitation to examine a pattern, compare perspectives, and decide whether a different behavior would help the business execute more effectively.
The same discipline applies to positive feedback. A leader may be creating trust, building a strong connection with a team, or giving people useful clarity without recognizing that those behaviors are worth protecting. If we only investigate what is broken, we risk redesigning away the practices that are already helping people do good work.
An outside advisor can offer one perspective, but leaders should also create ways for employees and peers to surface friction. Ask for examples, listen without immediately defending the current approach, and look for patterns rather than treating one comment as the whole truth. The goal is not to collect complaints; it is to make better decisions with information that was not reaching the executive table.
Protect the business when leadership changes
Clear responsibilities become especially important when the people at the top no longer want the same future. Sara described working with business partners whose goals had diverged and helping them navigate separation while paying attention to the business and the people connected to it. A change in the partnership is not automatically a failure; sometimes it reflects a genuine change in what each person wants.
The business still has customers to serve and employees who need to understand what happens next. Leaders navigating a transition should identify which commitments, decisions, and relationships could be affected, then establish who will own them during the change. That work deserves attention alongside the needs of the departing and remaining partners.
There is no single operating chart that resolves every transition, and no tidy process can eliminate every difficult conversation. What structure can do is keep important questions from disappearing into the emotion of the moment. It gives leaders a way to focus on continuity while they work through the human realities of change.
Make the bottleneck visible
A business does not become scalable simply because it has grown. It becomes more capable of scaling when people understand the work, have the context to make sound choices, and know where decision-making authority begins and ends. That requires leaders to be as willing to examine their own habits as they are to examine everyone else’s.
Here is the challenge: choose one decision that repeatedly comes back to you and trace its path from the person who first identified the issue to the moment you resolve it. Ask why it reached your desk, what information or authority was missing along the way, and who could own it with the right support. Then change that one path and review what happens.
