Which decisions should the founder still make?
Which decisions should the founder still make?
The team needs to take more ownership”
The founder says this in the leadership meeting.
Later that week, a business head agrees to a pricing exception. The founder hears about it, dislikes the reasoning and reverses the decision. The business head learns to consult the founder next time. The founder sees the consultation as further evidence that the team lacks ownership.
Both people can explain their behaviour. The business head believed the decision had been delegated. The founder believed a choice with long-term consequences should have been discussed. Nobody had defined where routine authority ended and founder stewardship began.
As a company grows, “the founder should let go” is too crude to be useful. Let go of which decisions? At what stage? With what information? What should happen when a delegated decision goes wrong?
These questions deserve better answers than a general appeal to trust.
Scale changes the founder’s information advantage
In the early years, the founder often has the most context. Customer conversations, product choices, hiring, cash and culture all meet in one person or a small founding team. Central involvement can be fast because the distance between information and decision is short.
That advantage reduces as the company grows. Information is created in more places. Specialists understand parts of the business more deeply. The founder sees a larger share of the company and a smaller share of each situation.
Harvard Business School’s work on how scale changes management describes a shift around 75 to 100 employees, when it becomes difficult for founders to remain involved in everything and the responsibilities of managers change.
The exact headcount is less important than the pattern. Decisions wait longer. Context travels through more people. Leaders spend time predicting the founder’s response. The founder receives an edited version of events and still feels expected to settle them.
Hands-on founders can build strong companies. The issue is where they place that attention.
Three kinds of founder decisions
Reviewing decisions in three groups can make the conversation more practical.
1. Decisions the founder should continue to make
Some decisions define the identity or long-term direction of the company. Founder involvement may remain valuable well beyond the startup stage.
Examples can include:
A fundamental change in purpose or positioning
A major capital commitment that could alter the company’s future
The appointment or removal of a CEO or core leadership role
Entry into a business that changes the company’s identity
A transaction affecting control of the company
A choice that tests a genuine cultural non-negotiable
This is a short list by design. If every senior hire, large customer exception and product priority is described as identity-defining, the category will absorb the company.
For each retained decision, explain why founder involvement matters. Is it legal authority, ownership responsibility, unique context, external relationships or stewardship of purpose? A clear reason makes the boundary easier for others to respect.
2. Decisions that need to be transferred
Many decisions can move to the leadership team after judgement has been developed and boundaries are clear.
Pricing is a common example. The founder may carry years of intuition about willingness to pay, strategic customers, delivery risk and the damage caused by an attractive deal with poor economics. A pricing matrix alone will capture only part of that judgement.
Transfer can happen through a period of joint decisions:
The founder explains the factors considered and the relative weight given to them.
The incoming owner recommends a decision before hearing the founder’s view.
Differences in reasoning are discussed.
Principles, thresholds and exceptions are recorded.
The incoming owner takes the decision and reviews patterns with the founder for an agreed period.
The same approach can work for senior hiring, product portfolio choices, major customer commitments and annual resource allocation.
Delegation is often described as a single event. Important judgement is transferred through practice.
3. Decisions the founder should stop making
Routine approvals accumulate because each one appears small.
Normal hiring within an approved plan, discounts within an agreed range, ordinary expense approvals, project sequencing within a function and customer remedies below a defined threshold should have clear owners.
Founder involvement in these decisions sends two messages. The formal owner lacks full authority, and proximity to the founder is a useful route around the system.
Stopping requires more than saying, “You decide.” The founder must also decline to accept side-door escalations. When an employee seeks a different answer, the question should return to the named owner unless an agreed threshold has been crossed.
This can feel slower for a few weeks. People are learning that the new route is real.
Four questions for classifying a decision
How reversible is it?
A reversible decision can move with broader boundaries. An acquisition, major capital investment or public commitment needs a different level of involvement from a three-month experiment.
Does it define who we are?
Founders often care about a decision because it touches the identity they have built. Make that connection explicit. Then test whether the connection is strong enough to warrant founder ownership.
Who has the best current information?
Seniority and information quality are different. The person closest to the work may understand the situation best. Another leader may understand the wider consequences. Good decision design brings both forms of context together without sending every choice to the top.
Does the owner have the capability and context?
If capability is missing, build it. If context is missing, share it. Retaining the decision indefinitely prevents both from developing.
Write a decision contract
For decisions moving away from the founder, record a short agreement:
The outcome the owner is responsible for
The decisions included in the mandate
The boundaries and thresholds
The people who must be consulted
The information visible to the founder
The conditions for escalation
The review period
Avoid requiring founder approval through the information clause. Visibility means the founder can see the decision and its result. Approval means the decision still belongs to the founder.
The agreement should also cover mistakes. What happens when a leader makes a reasonable decision and the outcome is poor? If the founder immediately takes the authority back, leaders will optimise for personal safety. Review the reasoning, improve the boundary if necessary and distinguish a poor outcome from poor judgement.
Watch for these founder traps
Delegating activity while retaining the decision
The team prepares options. The founder chooses. Everybody is busy, and the founder remains the decision point.
Keeping an undeclared veto
The leader has authority until the founder disagrees. Since the boundary is invisible, the safest response is to consult on everything.
Replacing context with rules
Policies can support judgement. A growing collection of rules may indicate that the company is trying to encode every founder preference. Leaders then follow the rule without understanding the purpose behind it.
Treating disagreement as disloyalty
A capable leadership team will sometimes reach a different conclusion. The founder can examine the reasoning, state a concern and use reserved authority where appropriate. If every disagreement becomes a test of trust, agreement will rise and decision quality will fall.
Delegating and disappearing
Decision transfer still needs review. Examine patterns, outcomes and the quality of judgement. The frequency can reduce as confidence grows.
What the transition looks like in practice
Our work with a founder-led cloud infrastructure services company included a move from capability-based dependence to clearer roles, decision ownership and operating reviews. As the company grew from around 100 to nearly 350 people, execution became more predictable and less dependent on the founders.
We have also seen the other side of the transition. A fintech company following a founder exit appeared to have process and discipline problems. A broad diagnostic found fragmented leadership intent, unclear accountability and inconsistent decision-making. Clarifying decision rights and integrating the leadership team helped the organisation regain stability.
Founder dependence and founder absence can both expose an undeveloped leadership system. Look at whether the right decisions are being made at the right level with enough context, authority and review.
For two weeks, keep a founder decision log. Record every request, approval, reversal and informal consultation that reaches the founder. Then classify each one: retain, transfer or stop.
The list may tell you more about the company’s readiness to scale than the organisation chart does.
The Execution Readiness Assessment can help identify where founder intent, leadership authority and organisational action have separated.