A leadership team cannot function if nobody is sure who gets to decide. The meeting can look serious. The people can be capable. The titles can be senior. Then a pricing exception, a hiring call, a launch delay, or a customer escalation lands in the room and everyone waits.
They wait because the decision rights were never made explicit.
This is one of the main reasons founders stay in the middle after they have hired functional leaders. The org chart changed. The authority map did not. People discuss, recommend, and then look to the founder to close the loop.
This article explains how decisions should move across the leadership layer: which ones stay with the founder, which belong to functional leaders, and which must be made jointly.
Why Informal Authority Breaks at Scale
In the early company, informal decision-making works. The founder is close to the work. The group is small. Context is shared. A quick conversation is enough.
As the company grows, that same informality creates drag. Leaders guess. They escalate to stay safe. They delay because they do not want to overstep. Or they decide in isolation and create rework for another function.
The founder often interprets this as a confidence problem or a talent problem. In many cases, it is an architecture problem. The company never specified the rules of decision-making at the leadership layer.
There are three common failure patterns.
First, everything important still requires founder approval. Leaders have responsibility without authority.
Second, everything is treated as a team decision. The group discusses issues that should have been owned by one leader. Meetings get longer. Accountability gets weaker.
Third, decisions bounce. Someone decides, another leader objects later, and the issue is reopened because the original authority was never clear.
A working leadership layer needs a simple distinction: solo decisions, joint decisions, and founder decisions.
The Three Buckets
Functional decisions belong to one leader. These are choices inside a defined domain where that leader has the context, the outcomes, and the accountability. Examples include hiring inside the function below an agreed threshold, sequencing work within an approved roadmap, standard discounting inside a policy, or running the operating cadence of that team.
Joint decisions sit between functions. No single leader can make them well because the consequences cross the seam. Examples include launch readiness, sales-to-delivery commitments, pricing changes that affect implementation, capacity tradeoffs between marketing demand and operations, or a policy that changes how two teams hand off work.
Founder decisions are the ones that change strategy, culture, capital risk, or the long-term shape of the company. These should be few. Examples include entering a new market, changing the business model, making a senior leadership hire or exit, taking on unusual contractual risk, or reversing a previously set company priority.
The mistake is putting too many decisions in the third bucket. The other mistake is pretending the second bucket does not exist. Cross-functional issues then either stall or get decided by the founder by default.
How to Tell Which Bucket a Decision Belongs In
Use four questions.
Who owns the outcome this decision will affect most?
Who else is materially affected if the decision is wrong?
Is the decision reversible at reasonable cost?
Does this choice change company direction, culture, or risk posture?
If one leader owns the outcome, others are only lightly affected, and the decision is reversible, it belongs with that leader.
If two or more functions are materially affected, it is a joint decision. The leadership team should resolve it, or the two leaders closest to the seam should resolve it and report the result.
If the decision changes direction, culture, or major risk, it stays with the founder. Input can come from the team. Ownership should not be blurred.
Guidance:
If you cannot classify a recurring decision in one minute, the company is not ready to scale that decision.
Write it down. Assign a bucket. Then hold the line.
Example: The Same Issue in Three Companies
Consider a request to delay a launch by two weeks.
In the first company, the product lead brings it to the founder. Sales is surprised. Operations is unprepared. The founder spends two days gathering context and making the call. That is a founder-centered system pretending to have a leadership layer.
In the second company, the product lead decides alone. Sales had already committed dates to customers. The delay is technically reasonable and commercially expensive. That is functional ownership without joint rights where they are needed.
In the third company, launch timing is defined as a joint decision. Product, sales, and operations have a short working rule: product can slip internal sequencing, but external commit dates require a joint call. The three leaders meet, make the tradeoff, and bring the founder only the customer or revenue implications that exceed an agreed threshold.
The third version is slower in the moment than a founder snap judgment. It is faster over time because the company is not waiting on one person to integrate every seam.
What Should Stay With the Founder
Founders often keep too much because they have been burned by a bad call. That instinct is understandable. It is also how the bottleneck returns.
Keep founder ownership for decisions that are:
Hard to reverse
High in symbolic or cultural weight
Material to cash, control, or strategy
Likely to set a precedent the company will live with
Release founder ownership for decisions that are:
Frequent
Operational
Inside an already approved policy or plan
Better made by the person closest to the work
A useful test is this: if the same type of decision reached you five times in a month, it probably should not be a founder decision. It should be a policy plus a functional or joint owner.
How to Install Decision Rights Without Creating Bureaucracy
You do not need a legal document. You need a one-page map.
List the 12 to 15 recurring decisions that currently create delay or confusion. For each one, name:
Primary owner
Who must be consulted
Whether founder approval is required
What happens if the owner and a peer disagree
Share it with the leadership team. Use it for 30 days. Then revise it based on what still bounced.
The map only works if the founder stops taking back decisions that have been assigned. That is the hard part. The first time a leader makes a different call than you would have made, the company learns whether the rights are real.
Support the decision if it stayed inside the agreed bounds. If it did not, correct the boundary, not just the person. Otherwise the group learns that the map is decoration.
Practical Guidance for This Week
Do not try to classify every possible decision in the company. Start with the ones that are already costing time.
This week:
Write down every leadership-level decision that came to you in the past 10 days.
Mark each one as functional, joint, or founder.
Choose three decisions you are prepared to stop owning.
Tell the relevant leaders, in writing, what they now own and where you still need to be involved.
In the next leadership meeting, refuse to referee one issue that belongs in the joint or functional bucket. Ask the owners to come back with a recommendation or a decision.
The point is not to disappear. The point is to stop being the default path for decisions that now have another rightful owner.
Looking Ahead in This Series
A meeting of functional heads is not a leadership team. Hiring true functional leaders is necessary, but not sufficient. Without explicit decision rights, those leaders will still route the hard calls through you.
Next week we will look at how founders should run the leadership meeting. Decision rights decide who owns the call. The meeting is where those calls should be made visible, resolved, and followed through.
If you completed the Leadership Team Diagnostic Toolkit, look specifically at the Decision Rights section. That score usually explains why the team still behaves like a meeting even after the talent has improved.
Let’s Get Entrepreneurial is published by ProfSpirit LLC.