By Andreas Pettersson, Founder, Leaders ADAPT
At Arcules I had a real Integrator. The Accountability Chart said operations belonged to that seat. The weekly leadership meeting ran through it. The quarterly priorities were owned there.
And the decisions that mattered still came back to me.
I gave it up from a responsibility perspective, but not from an authority perspective. It took me years to see the difference. Delegating authority is the part of delegation most founders skip, and it is the part that actually frees the second seat to work. This page is part of the Visionary stuck in operations guide.
Quick answer: Delegating authority means handing someone the right to make a defined set of decisions without your approval, not only the work that follows from them. Responsibility is the duty to deliver an outcome. Authority is the power to decide how. Founders often delegate responsibility and keep authority, which leaves the second seat accountable for results it cannot control.
What is the difference between delegating authority and delegating responsibility?
Responsibility is the obligation to deliver an outcome, and authority is the right to make the decisions that produce it.
You can hand over responsibility with one sentence: "You own customer onboarding." Authority takes more. It means the person can change the onboarding process, hire for it, spend on it and say no to you about it, without asking first.
Delegating authority is the act of transferring specific decision rights to another person, with the limits written down, so they can decide without your approval.
Here is what happens when you delegate responsibility and keep the authority. The person owns the result. You own the decisions.
Every change they need waits in line behind your calendar. When the result slips, they carry the blame for a plan they were never allowed to fix.
That is not delegation. That is a job title on a leash.
The classic management line says you can delegate authority but never responsibility. For founders, the practical problem runs the other way. I have said it on calls about my own history: I'm okay delegating responsibility. I struggle to delegate the authority.
Why do founders hand off responsibility and keep every decision?
From the outside it looks like a control freak boss. From the inside it feels like being responsible. Four forces keep the decisions with the founder.
- Identity. The founder built the company by deciding. Letting go of control feels like letting go of the job.
- Expectations above you. A board, investors or a parent company still treat the founder as the one who answers.
- Distrust of the back end. If you do not trust how the work gets done, you hold the decisions as insurance.
- No written limits. Authority without limits feels like risk, so the founder keeps all of it.
The second force was mine. The board and Canon expected me to be the authority, and I had the power to fire the Integrator. That forced more consensus decisions in several situations, instead of truly handing the Integrator the power to decide.
The fourth force is the one you can fix this week. Not because founders are control freaks. Because nobody wrote down which decisions move, and under what conditions they come back.
The same pattern shows up in how companies adopt EOS. I am not a big fan of self implementation, because it is often driven by a Visionary who does not want to give up control to the Integrator. And Level 10 Meetings fail when the Visionary or the CEO does not delegate authority. The meeting can be perfect on paper and still route every real call back to one person.
Leaders ADAPT is an independent advisory firm. EOS Worldwide, Scaling Up, Pinnacle Business Guides and FranklinCovey have not certified, endorsed or partnered with us, and we are not affiliated with any framework owner. Terms such as Integrator, Visionary, Level 10 Meeting and Delegate and Elevate describe their tools, and the worksheet on this page is our own design.
The Decision Rights Ladder: which decisions leave the founder first?
The Decision Rights Ladder is a Leaders ADAPT worksheet that lists a company's recurring decisions and gives each one a rung, from the founder decides alone to the second seat decides and the result shows up in the weekly numbers.
| Rung | Who decides | Who is told, and when | Typical decisions at $1M to $10M |
|---|---|---|---|
| 1 | Founder decides | Team informed after | Vision, capital, the second seat itself, selling the company |
| 2 | Second seat recommends, founder decides | Founder answers within an agreed number of days | Senior hires, prices outside the agreed band, new service lines |
| 3 | Second seat decides, tells the founder before acting | Founder can object within an agreed window | Budget moves inside the plan, larger vendor changes, reorganizing a team |
| 4 | Second seat decides, tells the founder after | Reported at the weekly leadership meeting | Hiring below the leadership team, process changes, customer escalations |
| 5 | Second seat decides, no report needed | Visible in the scorecard | Daily operations, purchasing inside budget, scheduling |
Rungs 2 to 4 follow the three authority levels in the 5 Minute Leader material: recommend options and I decide, decide but tell me before implementing, decide and inform me after. The ladder adds the founder's own rung at the top and a scorecard rung at the bottom.
Three rules make it work:
- Start with the decisions you are worst at making. For most Visionaries that is scheduling, process and people logistics, not strategy.
- Move one type of decision at a time, one rung at a time, and hold it there for a full quarter.
- Write the condition that sends a decision back up.
The third rule came from a client.
The CEO and the COO had never settled authority between them. The CEO did not want to give up the decision rights, even while being poor at operations. We went decision by decision and asked: in what cases must it be true that the CEO gives up the authority, and when does the CEO hold on, for the right reasons or the wrong ones?
The output was a manifest. A rule book for when each of them operates and when they do not.
Here is one decision moving down the ladder. Take pricing exceptions, the discount a salesperson wants to give to close a deal.
- Quarter 1, rung 2. The second seat recommends each exception with the margin impact. The founder decides within two working days.
- Quarter 2, rung 3. The second seat decides inside a written band and tells the founder before the quote goes out.
- Quarter 3, rung 4. The second seat decides and reports the week's exceptions at the leadership meeting.
- The condition that sends it back up. If average margin drops below the agreed floor for two months, the decision returns to rung 2 for a quarter.
Nothing about that is dramatic. That is the point. Delegating decision making in small, reversible steps is how the authority vs responsibility gap closes without a blow up.
The Decision Rights Ladder worksheet is free and ungated.
How do you delegate authority without losing control?
Control and authority are different things. You keep control by keeping visibility, not by keeping the decisions.
Trust but verify, in practice, means four habits:
- Visibility, not approval. The 5 Minute Leader line is the right one: "You own it. Update me weekly for visibility, not approval."
- Check early. Look at delegated work when it is about a quarter done, not the day before the deadline.
- Make it visible. "If it's not on the board, it's not delegated."
- Verify in the weekly meeting. The leadership meeting is where decisions get reviewed, not remade.
The hardest habit is the one I learned in the room.
There were multiple situations where I, as CEO, really wanted to go in a certain direction. I felt it was more important to keep the process and let the Integrator make the decision. Every time I held that line, the Integrator's authority got stronger. Every time I did not, it got weaker for weeks.
Rhythm creates predictability. Predictability creates trust. Trust creates speed.
What happens when the person you gave authority to gets it wrong?
Most wrong calls on reversible decisions are tuition. The 5 Minute Multiplier material puts it well: the cost of a slow decision is usually higher than the cost of a wrong one.
A pattern of wrong calls is different. Then the question is the person or the seat.
Sometimes it is the right person in the wrong seat, and the fix is to move them. Sometimes it is the wrong person. My rule, learned slowly: decide within 30 days. Each time I waited longer, the whole organization paid a tax it did not need to pay.
Do not pull all of the authority back when one call goes wrong. Move that one decision up a rung, openly, with a date to try again. Quiet overruling does more damage than the bad decision did.
Where AI fits when you delegate authority
AI cannot hold authority. It can hold the rules.
An agent can route each decision to its rung, prepare the pre read for a rung 2 recommendation, log what was decided and flag when someone skips a rung. That is what the AI chief of staff does under a written manifest. It makes delegated authority visible without putting the founder back in the loop. Delegation in the age of AI covers the task side of the same shift, and AI for companies running EOS maps it to each component of the system.
The same logic applies to AI adoption itself. The CEO has to be the Visionary who accepts AI, then delegate the implementation to the whole C suite, not just the Integrator.
What stays with people, never with the agent:
- Hiring, firing and moving people between seats
- The judgment inside issue solving
- Consequences for missed commitments
- Commitments about strategy and the year ahead
- Performance conversations
- External promises to customers and lenders
The full reasoning is in what not to delegate to AI.
What delegating authority does not fix
A decision rights map will not fix a wrong person in the seat. It will not fix a leadership team that avoids hard conversations, or a board that still expects the founder to answer for everything.
Those are leadership problems, and they sit underneath the operating system. Leadership team development covers them, and leadership accountability covers the weekly system that holds a team to its commitments. For the seat design itself, read the accountability chart guide. For the operator side of running the cadence, see operational leadership.
The task side of delegation has its own pages: Delegate and Elevate for the EOS exercise, founder to CEO delegation systems, the five level delegation training and delegation and well being. If you are still deciding whether EOS is the right frame at all, read the independent EOS review.
Growing people create growing organizations, and the opposite is also true. Delegating authority is how a founder stops being the ceiling on both.
Which decision will you move down one rung this week? Reply with the decision, and what must be true for you to take it back.
Common questions about delegating authority
What does delegating authority mean?
Delegating authority means transferring the right to make a defined set of decisions to another person, with written limits, so they can act without asking for approval first. It differs from assigning a task or an outcome. A person can be responsible for a result with no authority over it, which is the most common delegation failure in founder led companies.
What is the difference between authority and responsibility?
Responsibility is the obligation to deliver an outcome. Authority is the right to make the decisions that produce the outcome, such as changing a process, spending inside a budget or hiring for a team. Effective delegation matches the two, so the person who owns a result also holds the decisions that control it, within limits agreed in advance.
Can you delegate authority but not responsibility?
Classic management texts say a leader can delegate authority while keeping ultimate responsibility for the result, and that holds for a CEO's duty to the board. Inside a growing company the more common failure runs the other way: founders hand over responsibility for an outcome while keeping every decision that controls it, which leaves the second seat accountable without the means to act.
Which decisions should a founder delegate first?
Start with recurring, reversible decisions the founder handles least well, such as scheduling, process changes, vendor choices inside budget and hiring below the leadership team. Keep vision, capital, the second seat itself and major external commitments. Move one type of decision at a time, hold it for a quarter, and write down the condition under which it would return to the founder.
How do you delegate authority without losing control?
Keep visibility instead of approval. Agree which decisions sit at which level, review outcomes at a fixed weekly meeting, make delegated work visible on a shared board or scorecard, and check in early rather than at the deadline. If a decision has to come back, move it up a level openly, because quiet overruling erodes the other person's authority.
Can AI make decisions on behalf of a manager?
AI can prepare decisions, route them to the right person and log what was decided. It should not hold decision rights over people, strategy, customer commitments or consequences for missed work, because accountability needs someone who can be held to account. What AI does well is enforce the decision rules a leadership team writes down, which makes delegated authority easier to verify.
Your next question
This page is part of the Visionary stuck in operations guide.
- Chief of staff vs COO vs Integrator: which seat holds which decisions
- The AI chief of staff and the two page manifest
- The 5 Minute Leader protocols for delegation and accountability
What it is: the 5 Minute Leader, the protocols for the how that EOS leaves out: delegation, accountability, 1:1s, feedback and rhythm. Who it is for: founders and second seats who have agreed on paper who decides what and now need the weekly habits that make delegating authority stick. See the 5 Minute Leader
