Delegate and Elevate: The Tool, a Free Template, and Why CEOs Stall at 'Delegate'

By Andreas Pettersson, Founder, Leaders ADAPT

You did the Delegate and Elevate exercise. Four boxes, forty activities, a clean list of what to hand over. Ninety days later, almost every one of them is still on your calendar.

That is not a list problem. That is an authority problem.

Delegate and Elevate is one of the most copied tools in the Entrepreneurial Operating System, and the grid is the easy part. It takes an hour.

The handover takes a quarter, and that is where most CEOs stall. I know, because I stalled there myself at Arcules. This page is part of the leadership team development series for companies that already run an operating system.

What is Delegate and Elevate, and what are its four quadrants?

Delegate and Elevate is an EOS delegation framework that sorts every recurring activity by enjoyment and skill, so a leader keeps the work where they add the most and hands over the rest.

People search for it as the EOS Delegate and Elevate tool, but you can run it on a single sheet of paper. In my own words, the four quadrants look like this:

The tool is simple on purpose. That is its strength and its weakness. It tells you what to hand over. It does not tell you how, to whom or with what authority.

How do you run the Delegate and Elevate exercise in one week?

Run it from your calendar, not your memory. Memory leaves out the work you are embarrassed to still be doing.

1. Monday: export two weeks of calendar and email. List every recurring activity. Most leaders find more lines than they expected.
2. Tuesday: sort each line into a quadrant. Be honest about the third one. Skill is not a reason to keep work.
3. Wednesday: name a receiver for every line outside the top quadrant. A person, an AI workflow, or "stop doing it."
4. Thursday: set an authority level for each handover. This is the step nearly everyone skips.
5. Friday: hand over the first three. Three, not thirty.

A free Delegate and Elevate template: the Delegation Ledger

This is our own template. Copy it into any spreadsheet.

The last column is the one that matters. Work that comes back to you within two weeks was never really handed over.

What you are buying with the ledger is time to work on the business instead of in it: the direction, the seats, the people and the rhythm. If the hours you free up refill with other operational work, the exercise has moved your calendar around without changing your job. Block the recovered hours before anyone else books them.

Why do CEOs stall at "delegate"?

Not because they lack people. Because they keep the decision.

I did exactly this at Arcules. I handed the Integrator seat over, and I did not hand it over quickly enough. "I gave it up from a responsibility perspective, but not from an authority perspective." Part of that came from the board and from reporting into Canon, where I was expected to be the authority. The result was consensus decisions in situations where the Integrator should simply have decided.

Here is what happens when you delegate responsibility and keep authority. The receiver does the work, then waits for you. You become the bottleneck on work you no longer do. Both of you get frustrated, and the work drifts back to your desk.

Three more stall patterns are worth naming:

Soft asks. "Could you possibly..." and "If you have time..." The 5 Minute Leader material is blunt about it: "Unclear delegation isn't kindness. It's cruelty."

Reverse delegation. The receiver brings every question back. The fix is one question: "What would you do if I weren't here?"

Phantom delegation. You told someone once, in a hallway. It is on no list. "If it's not on the board, it's not delegated."

The same control instinct shows up at company level. I am personally not a big fan of self implementing EOS, because it is often driven by a Visionary who does not want to give up control to the Integrator. CEO delegation fails for the same reason inside the tool.

The grid is honest. The hand holding the pen is not ready to let go.

What should a CEO delegate first?

Start with the work that is easy to hand over and costly to keep. The 5 Minute Leader material gives a practical filter, the 70 percent test: if someone else can do it at 70 percent of your quality, it goes on the list. "If someone else can get it to 70%, delegate it."

Four conditions make an activity a good first handover:

• You do it regularly.
• Someone can already do it at 70 percent or better.
• It needs little context to do well.
• The stakes are low if it is imperfect for a few weeks.

Scheduling, first drafts of weekly updates, expense reports and basic research usually qualify. Hiring decisions, key customer escalations and board commitments do not, at least not first.

The deeper version of this, from founder to CEO, is in delegation and systems that scale. The step by step skill, including the three minute handover conversation, is in delegation training.

How do you hand over authority, not just the task?

Name the authority level out loud when you hand something over. The 5 Minute Leader protocol uses three levels, and I add what each one means for your calendar.

A sensible default: start each handover at the level the stakes require, and move it one step toward Level 1 after two clean cycles. Level 3 is a starting point, not a home.

Then check at the 25 percent mark of the work, not in the first hour. Early enough to correct. Late enough to leave the owner alone.

Two more things make authority stick. Write the handover into the accountability chart, so the seat owns it. And keep the decision in the room where it belongs.

I have been in situations as CEO where I wanted to go a certain direction, but I kept the process and let the Integrator decide. That is what authority looks like when it is real.

Where AI fits in Delegate and Elevate: which quadrant goes first?

The bottom quadrant goes first: recurring work you neither enjoy nor do well, mostly coordination. Email triage, calendar management, status collection and report assembly.

The numbers from our client work are large. Clients have saved $200,000 to $300,000 in hours per quarter from email, calendar and reporting automation, with about 95 percent of that work automated and the decisions kept with the managers (Leaders ADAPT client figures, rounded, September 2026). In one case a finance team with open roles stopped hiring, because the new AI processes covered the work those hires were meant to do.

Two warnings. First, AI implementation is a delegation too, and the CEO cannot hand it only to the Integrator. The CEO has to be the Visionary who accepts AI and then delegates the implementation to the whole C suite. "AI is a cultural change, if you have one person sandbagging it's never gonna go anywhere."

Second, self implemented AI goes off the rails without validation rules. I have walked into an organization where a vibe coder had built a CRM as a single HTML file with over 12 million lines of code. After about a month of proper training, with the right ontology, rules and framework, results come much faster.

What stays human, whatever quadrant the work came from:

• People decisions
• Issue solving judgment
• Accountability consequences
• Strategic commitments
• Performance conversations
• External promises

The full list with reasons is in what not to delegate to AI. How the trust and autonomy question changes with AI is in delegation in the age of AI, and the map across the whole operating system is in AI for companies running EOS.

What Delegate and Elevate does not fix

The tool frees your time. It does not create people ready to receive the work.

"Growing people create growing organizations, and the opposite is also true." If nobody on the team is growing, every handover lands on someone already at capacity, and the work comes back. The fix is development, and that is a leadership job, not a quadrant.

It also does not fix the reason you held on. Some CEOs keep work because it is the part of the job that still feels good. That cost shows up in more than the calendar, which is why delegation and well-being belong in the same conversation.

The wider set of people problems an operating system surfaces is in the leadership team development hub. If you are weighing the whole system, start with my independent EOS review.

Picture your calendar one quarter from now. The weekly report, the vendor renewals and the pre-read drafts are gone from it, and the decisions attached to them no longer wait for you. The hours you blocked go to the work in your top quadrant.

Common questions about delegate and elevate

Is there a free Delegate and Elevate template?

Yes. A workable template is a table with one row per recurring activity and columns for weekly hours, the quadrant, the receiver, the authority level, a check in date and the status after two weeks. The Delegation Ledger on this page follows that layout. A spreadsheet is enough, because the value comes from the handover rules, not the format.

How do you work on the business instead of in it?

Working on the business means spending time on direction, structure, people and the operating rhythm rather than on the daily output. It usually requires moving recurring operational work to named owners with clear authority, protecting a fixed block of time each week for planning, and measuring the company through a short scorecard instead of personal involvement.

How often should you redo Delegate and Elevate?

Once a quarter is a common rhythm, often timed with quarterly planning, because the list of activities changes as the company grows. A leader in a fast transition, such as a founder handing over operations, may benefit from a monthly review for the first two or three months. Each round should start from the actual calendar, not memory.

What if nobody on the team can take the work?

Then the gap is a hiring, development or structure problem, not a delegation problem. Options include handing the work over at a lower standard with a check in, developing someone through a stretch assignment, automating part of it, hiring for the seat, or stopping the activity. Keeping it indefinitely because nobody is ready usually means nobody will be.

Should the whole leadership team do Delegate and Elevate?

Yes. The exercise is usually introduced for the CEO or founder, but every leader on the team has work that belongs elsewhere. Running it together also exposes work that bounces between leaders or sits with nobody. The results are most useful when they feed directly into the accountability chart and the quarterly priorities.

What is the difference between delegating tasks and delegating outcomes?

Delegating a task hands over a set of steps, and the leader still owns whether the result is good. Delegating an outcome hands over the result itself, with the person free to choose the steps within an agreed authority level. Outcome delegation takes longer to set up and frees far more of the leader's time afterwards.

Your next question

This page is one spoke of the leadership team development series. Three next reads:

• Operational leadership and the move from Operator to Architect
• Leadership accountability: the weekly system
• A fractional AI executive for the AI quadrant

Which Delegate and Elevate handover on your list has boomeranged back to you more than twice?