An article by Shahnaz Hamade, Founder and CEO of Harmonie Consulting

There is a particular kind of exhaustion that many founders understand. It comes from being the answer to every question, the approver of every decision and the person whose phone is never truly off.

From the outside, this can look like commitment. Inside the company, however, it may signal something more serious: the operating model has failed to keep pace with the business.

In the early stages, centralised leadership is often necessary. The founder holds the vision, understands the customer and can make decisions faster than any committee. But as the company hires more people, enters new markets and manages a wider product portfolio, that same concentration of authority can begin to constrain growth.

Research cited by McKinsey found that around 80 per cent of startups in a sample of more than 3,000 'Series A' companies that successfully launched and developed a product did not take it through to full scale. Investors attributed 65 per cent of portfolio-company failures to people and organisational issues.

The lesson is not that founders should become less involved. It is that their involvement must change. Startups do not simply outgrow their founders; they outgrow operating systems that depend on founders for every meaningful decision.

When speed becomes dependency

Founder-led decision-making works when the team is small, trust is still developing and priorities change daily. The founder is often the company’s chief salesperson, product owner, recruiter and cultural reference point.

Problems emerge when temporary habits harden into a permanent structure.

Decisions begin to queue up. Functional leaders wait for approval on matters they should own. Meetings end without resolution because the person with final authority was not present. Employees carry responsibility for results but lack the authority to make the decisions required to achieve them.

The company then moves at the speed of one person’s bandwidth.

This issue is frequently misdiagnosed as a capacity problem. The founder tries to solve it by working longer hours, attending more meetings or hiring another assistant. But additional effort cannot resolve unclear decision rights or weak accountability.

McKinsey’s research on scaling companies identifies an aligned founder and leadership team, clear roles and a structure designed for growth among the capabilities required to scale successfully. The distinction between advisers and decision-makers is particularly important: people can contribute to a decision without all holding the power to delay or veto it.

A founder bottleneck, therefore, is not primarily a time-management problem. It is an organisational design problem.

Why authority remains concentrated

Delegation is often presented as a straightforward management skill: assign the task, set a deadline and review the outcome. In practice, transferring authority is more difficult because it changes the founder’s relationship with the company.

For many of the Arab founders and business leaders I work with, trust is personal and earned gradually. When a company has been built through close relationships, informal agreements and the founder’s direct oversight, formalising authority can feel unnatural. Delegating a decision may be interpreted as losing control or distancing oneself from the business.

This is not unique to the region, but it can become more pronounced in relationship-driven business environments, particularly when companies expand across markets and the founder remains the central link between employees, customers, investors and partners.

There is also an identity question. Founders are rewarded in the early years for being involved in everything. Their responsiveness keeps customers, employees and investors confident. Later, the same behaviour can prevent other leaders from developing.

The founder may appoint a functional head but continue approving that person’s decisions. They may ask managers to take ownership, then reverse their choices without explaining why. Over time, employees learn that authority remains with the founder regardless of what the organisational chart says.

The result is delegated work without delegated power.

Structure does not have to mean bureaucracy

Founders often resist organisational structure, associating it with corporate bureaucracy. Yet the purpose of structure is not to add more approvals. It is to reduce the number of decisions that require escalation.

Effective structure is often barely visible. People know what they own, what requires consultation and what must be escalated. Decisions are taken at the appropriate level, while the founder remains involved in the choices that materially affect the company’s direction.

This process requires clarity across four areas.

1. Define who makes recurring decisions

Start with the decisions the company makes repeatedly: pricing exceptions, hiring approvals, customer refunds, product priorities, marketing expenditure and supplier selection.

For each one, identify a single decision owner. Specify who should provide input, what financial or strategic boundaries apply and when escalation is necessary.

Accountability becomes weak when several people can influence a decision but nobody clearly owns it. A useful principle is to give more people a voice, but fewer people a vote.

2. Separate strategic and operational decisions

Not every decision carries the same risk.

Founders should continue to own choices that could materially alter the company’s future, such as entering a new market, changing the business model, raising capital, making a major acquisition or appointing senior executives.

Recurring operational decisions should usually sit with the relevant functional leaders. If the head of sales needs the founder’s approval for every commercial concession, or the head of product cannot prioritise routine updates, the title carries little genuine authority.

The objective is not to remove founders from decision-making. It is to reserve their attention for decisions where their judgement creates the most value.

3. Build leaders, not just departments

Hiring experienced executives does not automatically create a leadership team. New leaders need clear mandates, measurable outcomes and the freedom to make decisions within agreed boundaries.

They also need an operating rhythm that connects the functions of the business. As startups scale, product, sales, operations and finance become increasingly interdependent. A commercial promise can affect product capacity, hiring requirements and cash flow at the same time.

Regular leadership meetings should focus on these dependencies and the decisions required to resolve them. They should not become a sequence of departmental updates delivered to the founder.

Functional leaders must learn to challenge one another, resolve trade-offs and commit to collective decisions. Otherwise, the founder remains the only person connecting the organisation’s different parts.

4. Redefine the founder’s role

The founder’s job should evolve as the company does.

In the earliest stage, the role centres on direct execution. As the company grows, it shifts towards setting direction, allocating resources, developing senior leaders, protecting the culture and maintaining relationships with key stakeholders.

This does not mean founders must become distant figureheads. Their closeness to customers and ability to challenge assumptions can remain major competitive advantages. The change lies in how that influence is exercised.

Instead of personally solving every problem, the founder should strengthen the system through which problems are solved.

A practical test for founder dependency

Founders can begin by examining five decisions that reach them every week.

For each one, ask:

• Why does this decision still come to me?
• Is the problem a lack of capability, authority or trust?
• Who should own it?
• What information or boundaries would that person need?
• Under what circumstances should it return to me?

Transfer two of those decisions for one month. Make the new ownership explicit to everyone involved and agree on the limits of that authority in advance.

Then measure the result. Did the decision happen faster? Was the outcome materially worse, or simply different from the choice the founder would have made? Did the responsible leader become more confident? Did the founder intervene before the agreed review point?

That final question matters. Delegation fails when founders reclaim authority at the first sign of discomfort. A reasonable decision made independently can be more valuable to the organisation than a marginally better one that reinforces dependence on the founder.

The aim is not to eliminate mistakes. It is to build a company capable of learning and acting without waiting for one person.

Scaling ultimately requires more than revenue growth, larger funding rounds or a bigger team. It requires a different distribution of authority.

A startup has begun to scale operationally when its leaders can make sound decisions, resolve cross-functional problems and deliver against priorities without routing routine matters through the founder. At that point, the founder is no longer the company’s operating system.

They are building one.