Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

Your company can’t scale if every decision comes back to you

Three systems that reduce dependency.

[Photo: Getty Images]

Profile photo of Stoyana Natseva

Founder CEO of Happy Life Academy® · Happy Life Academy

Many founders believe a slowdown means their company has a people problem, a productivity problem, or a growth problem. Sometimes the obstacle is much closer to home: Every important decision still comes back to the founder.

Early on, that concentration of authority can be an advantage. Founders know the product, understand their customers, protect quality, and move quickly because they carry the original vision. As the company grows, however, the same habits can create delays. The workforce expands while the organization’s capacity to make decisions remains limited.

WHEN INVOLVEMENT BECOMES DEPENDENCY

I don’t believe founders need to step away from their companies as they scale. In expert-led businesses especially, the founder may remain an essential source of methodology, vision, and professional judgment.

Problems arise when even routine matters require that person’s constant approval. Employees wait instead of deciding. Managers escalate issues they could resolve themselves. Customer questions move through several people before they reach the founder, and new ideas stall while someone waits for a yes.

Eventually, the founder’s calendar begins to dictate the pace of the entire operation. Adding employees does little to improve decision-making when authority is still concentrated in one place.

LOOK IN THE MIRROR

As my academy expanded across programs, markets, and functions, I recognized this tendency in my own organization. Too many decisions carried an unspoken question: What does Stoyana think?

At one stage, routine questions about program communications, participant situations, and operational details were escalated to me for approval. None was particularly difficult by itself, but together they created a steady stream of interruptions that slowed both me and the team.

Being consulted can feel flattering to a founder. Operationally, the consequences are serious: Every additional employee, product, or market can generate another layer of questions and exceptions.

We began moving knowledge out of my head and into organizational systems. The first step was to distinguish situations where my involvement added genuine value from those that simply lacked a defined process. Recurring decisions were assigned clear owners. Standards were documented. And team members received decision boundaries rather than vague instructions to “take responsibility.”

We also established when an issue genuinely required escalation. That gave people something they had been missing: confidence about when they had the authority to act.

WHERE DELEGATION FAILS

One of the most common scaling mistakes is to delegate tasks without transferring the judgment behind them. A founder tells an employee, “You own this now,” but leaves that person to guess how to weigh quality, risk, priorities, and exceptions. Responsibility may have moved on paper, yet the employee still has to return for guidance whenever a decision falls outside a familiar pattern. Job descriptions alone cannot resolve that uncertainty.

Leaders need to make their decision criteria visible. Why would I approve one proposal and reject another? Which customer problem demands immediate intervention? What level of quality is acceptable? What risks can a manager take independently, and what must receive senior review?

For founders, the answers may feel obvious after years of experience. For a team that has never heard the reasoning, those standards remain invisible. Documenting enough of that judgment allows people to make decisions consistent with the founder’s priorities, even when the founder is unavailable.

THREE SYSTEMS THAT REDUCE DEPENDENCY

In practice, I focus on three systems:

1. Define decision ownership. Every recurring decision needs one accountable owner. When responsibility is shared vaguely among several people, a final decision often drifts upward. Clear ownership tells the team who is expected to act and who is accountable for the outcome.

2. Codify decision logic. A useful procedure explains the reasoning behind a decision as well as the steps to follow. This is particularly important in businesses built on expertise, a distinctive methodology, or a strong founder brand. Written criteria help managers handle situations that no checklist can anticipate in full.

3. Set escalation rules. Teams need explicit boundaries between decisions they can make independently and those that require higher-level review. With those boundaries in place, routine work can move forward without unnecessary approvals while significant risks still receive appropriate attention.

THE NEEDED EVOLUTION

A founder who participates in every decision may feel highly responsible, but that model eventually places a ceiling on growth. The next stage of leadership demands a different measure of success: whether the organization can make sound decisions without the founder being present. This has changed how I think about scale. I pay more attention to how much of the founder’s knowledge, standards, and judgment becomes usable by capable people throughout the company.

When that happens, delegation becomes a way to build organizational capacity. The founder can devote more attention to the decisions where their experience matters most, while the business develops the ability to operate beyond the limits of one person’s time.

Stoyana Natseva is founder and CEO of Happy Life Academy.