Role Clarity and Delegation With Agency Owners: A Guide for Coaches

When an agency owner can't delegate, don't start with delegation. Start with the role he wants to have in the business and the role he actually fills today. Once both are on the table, you can decide which tasks he keeps, which he hands over and which he drops altogether.

This guide describes a process of 4 sessions plus one review. It is written for coaches who work with owners of small agencies and consultancies, and it applies to any entrepreneur whose desk every important decision has to pass. More on working with these clients is on the page Business coaching with CORE.

In short

• Role clarity comes before delegation. If the owner hands over work without a clear role, the work comes back.
• The process: diagnosis, seat map, delegation decision (keep, hand over, drop), first handover or hire, review.
• The Eisenhower matrix and the GROW model are useful, but they answer different questions than the role question. Use them at specific points in the process.
• A profile, for example from CORE Navigator, is one possible part of the diagnosis. It is optional, and your client always makes the decision.

As a coach, how do I start role clarification with an owner who can't delegate?

Start with an honest look at his actual week, not with delegation tips. An owner who can't let go has usually heard the advice already, mostly "trust more" or "brief more clearly". Little has changed, because the advice starts in the wrong place.

In the first conversation, don't ask "What could you hand over?". Ask "What did you do last week, and which of those things really had to be you?". The first question invites good intentions. The second brings his real week into the room.

Then separate two things the client usually mixes up:

• The role he wants. Where does he want to spend his time a year from now? What should run in the agency without him?
• The role he fills today. Which tasks end up with him, and why? Because only he can do them, because they have always been his, or because nobody else is responsible?

The gap between the two is where you work. Many owners notice at this point that their problem isn't a lack of trust. It's a lack of ownership. When no role is defined, every open question lands on the boss's desk.

As homework, the client keeps a simple task log for two weeks: what he did and for how long, and whether someone else could have made the call. A spreadsheet or a notebook is enough.

The process in 4 sessions

The order matters more than the tools. Each session builds on the result of the one before.

Session	Goal	Result
1. Diagnosis	Clarify the wanted and the actual role	Picture of the target role, task log running
2. Seat map	Sort tasks by role	One page with every role, its tasks and today's owner
3. Delegation decision	Keep, hand over, drop	A first task to hand over, with a clear decision scope
4. Handover or hire	Who takes over, with what mandate	Handover agreement or role profile for a new position
Review after 4 to 6 weeks	What has really been handed over?	Adjusted agreement, next handover

Session 1: diagnosis

In the first session you clarify where the client stands and where he wants to go. That covers the questions in the list further down, a picture of his target role and what has kept him from handing work over so far.

A profile can help here. A profile of how he works gives pointers to the kind of work that energizes him and the kind that drains him. You always check those pointers against his actual tasks. If you prefer to work without an instrument, you get the same information more slowly through the task log and good questions.

Session 2: seat map

A seat map is one page listing the roles in the agency, each with its tasks and the person who fills it today. It shows how many roles sit with the owner. In small agencies it is often 4 or 5.

You build it from the task log. Each task is assigned to a role such as sales, client management, delivery, operations and finance, or team leadership. Then you note for each role who fills it today and who should. There is an example below.

For co-founder duos there is a related method that sorts decisions instead of tasks: the seat map for co-founder duos.

Session 3: delegation decision

In the third session you go through the seat map role by role and decide for each task whether the owner keeps it, hands it over or drops it. The next section describes how.

The session ends with exactly one task to hand over first. Not five. One handover that works convinces the client more than any list.

Session 4: handover or first hire

If someone on the team can take over the task, you work out the handover: what result is needed, what the person may decide on their own and when they check with the owner.

If nobody can, the freed-up role becomes a role profile for a position. The role profile describes the tasks and responsibility of the position and the way of working that complements the owner. It describes the position, not a particular candidate. Choosing the person is a separate step with its own methods, and the owner's profile isn't meant for it.

Review after 4 to 6 weeks

In the review you look at which decisions the other person actually made and where the work ended up back with the owner. Work coming back is normal. It shows where the decision scope was too narrow or the handover too vague. Then you pick the next task.

How does a coach decide with an agency owner which tasks to hand over?

You decide task by task between keep, hand over and drop, based on role rather than preference. The question isn't "What does he dislike doing?". It is "Does this task belong to the role he wants?".

Decision	When	Check question
Keep	The task belongs to his target role, and he creates more value there than anyone else on the team.	Would the agency get noticeably worse if he stopped doing it?
Hand over	The task is necessary but belongs to another role.	Could someone else do it to a similar standard with a clear brief?
Drop	The task is habit, reassurance or a leftover from the early days.	Would anyone notice if it disappeared?

A good starting point is the task that eats a lot of time and has little leverage. That is rarely the big project. More often it is approvals and client emails that cross the owner's desk although they don't need to. The article From founder to managing director describes this order from the owner's side.

Two mistakes are common at this stage. In the first, the client hands over what annoys him and keeps what makes him feel safe, even when it doesn't belong to his target role. In the second, he hands over the task but keeps every decision inside it. The other person then has the work but not the responsibility, and everything still runs through him.

Sample seat map

This example is constructed, not a client case. It shows an agency with 12 employees whose owner is strongest at selling and at client relationships.

Role	Tasks	Today	Target owner	Decision
Sales and new business	First calls, proposals, price negotiation	Owner	Owner	keep
Client management	Ongoing coordination, escalations, satisfaction	Owner	Project lead	hand over; escalations above an agreed project size stay with the owner
Proposal approval	Review of every proposal before it goes out	Owner	Project lead up to a project size limit	hand over, first handover
Delivery	Planning, quality control	Project lead and owner	Project lead	hand over
Operations and tools	Tool choice, templates	Owner	Project lead	hand over
Finance	Invoicing, cash overview	Owner and accountant	Owner with an assistant	keep the cash overview, hand over invoicing
Weekly status report to everyone	Writing the report	Owner	nobody	drop, replaced by a short team meeting
Team leadership	One-on-ones, hiring	Owner	Owner	keep; prepare a role profile for a second lead

Two things stand out. Most of the tasks being handed over belong to roles where the owner isn't at his strongest anyway, and one task disappears entirely. The first handover is also small and clearly bounded: proposal approval up to a project size limit.

Which tools help with an agency owner who is stuck in day-to-day operations?

With an overloaded owner, the tools that help most are the ones that make his week visible and pin down who owns what. No single tool answers the role question on its own. Here is what works at which stage:

Tool	What it's good for	Where it stops	Use in the process
Task log (two weeks)	Shows where the time really goes	Doesn't say who should take a task over	Between sessions 1 and 2
Eisenhower matrix	Sorts tasks by important and urgent	Doesn't say which role a task belongs to	Session 3, for priorities within his own role
Seat map	Assigns tasks to roles and shows who fills several	Needs a picture of the target role	Session 2
Decision scope agreement	Sets what the other person decides alone	Only works if the owner sticks to it	Session 4
GROW model	Structures the conversation from goal to next step	Supplies no content, only the sequence	Every session, as a conversation frame
Work style profile (for example CORE Navigator)	Gives pointers to the kind of work that suits the owner	Judges neither the team nor candidates; doesn't replace looking at the tasks	Session 1, optional

Placing the Eisenhower matrix

The Eisenhower matrix sorts tasks into 4 boxes along the axes important and urgent. It goes back to a line Dwight D. Eisenhower quoted in a 1954 speech: "I have two kinds of problems, the urgent and the important." Eisenhower credited it to a former college president. As a four-quadrant grid, the idea became widely known through Stephen Covey's 1989 book "The 7 Habits of Highly Effective People", which recommends delegating the quadrant "urgent but not important".

For an overloaded owner the matrix is a good way in, because it frees up time quickly. It has one gap, though: it asks how important a task is, not whose task it is. A task can be important and urgent and still belong to the project lead's role. So use the matrix after the seat map, for the tasks the owner keeps.

GROW as a conversation frame

GROW stands for Goal, Reality, Options and Way Forward. The model came out of the UK coaching scene around Graham Alexander, Alan Fine and John Whitmore and was first published in 1992 in Whitmore's book "Coaching for Performance".

GROW fits this process because every session follows the same movement: clarify the target role (Goal), look at this week (Reality), options for keep, hand over and drop (Options), one concrete first handover (Way Forward). What GROW doesn't supply is content. Which roles an agency has and how to split them is something you bring or work out with the client.

Setting the decision scope

Many handovers fail because of an unclear scope rather than the person. A simple scale, agreed per task, helps:

1. The person prepares, the owner decides.
2. The person proposes, the owner approves.
3. The person decides and informs the owner afterwards.
4. The person decides alone; the owner only sees exceptions.

The aim isn't to reach level 4 right away. The aim is that both know which level they are working at, and that the level gets adjusted in the review.

How do I support an entrepreneur moving from specialist work to leadership?

You support the move by treating it as a change of role, not as training in leadership techniques. An entrepreneur who built his agency as its best specialist loses exactly the work that made him successful. That is the core of the resistance.

It helps to make two agreements and then change how success is measured.

Limit specialist work visibly instead of banning it. Agree which specialist work he deliberately keeps, for example the concept work for two key clients. A complete exit from the craft rarely works and often isn't necessary.

Describe leadership work as tasks. "Lead more" isn't an assignment. It becomes concrete when one-on-ones and a weekly team meeting are fixed dates in the calendar, next to the handover agreements from session 4.

Then the measure of success: as a specialist, he measures himself by his own work. As a leader, he measures himself by what the team gets done without him. So in the review, don't ask what he got done. Ask which decision was made well without him.

More on this situation is on the page Leadership coaching and in the article Wrong seat syndrome.

Questions for the first session

You can use these questions in the diagnosis session. You don't need all of them, and the order is a suggestion.

About today's role

1. What did you do last week that only you could do?
2. Which decisions land with you although someone else could make them?
3. Where does your team wait for you before it carries on?
4. Which task do you do because it has always been yours?

About the role he wants

5. If the agency runs well without you for two weeks a year from now, what do you do in a normal week?
6. Which work makes you lose track of time, and which do you keep putting off?
7. Which role would you hand over today if you knew it would be done well?

About the obstacles

8. What happened the last time you handed something over?
9. How would you know that a handover is working?
10. Who on the team could take on more responsibility today but doesn't get it?

About the frame

11. By when should something have changed?
12. Who needs to know about the new split for it to stick?

More on designing the first session is in Diagnostics over gut feeling.

Where CORE fits in this process, and where it doesn't

CORE Navigator is a profile for entrepreneurs and their coaches. It describes how someone works using the 4 CORE Types Constructor, Operator, Rainmaker and Explorer, and CORE Dynamics adds which values guide day-to-day decisions and what shifts under pressure.

In this process a profile fits into the diagnosis. Before you build the seat map, it gives pointers to the roles that suit the owner and where he loses energy. That saves time on orientation. Whether the pointers hold, you check against the real tasks.

What a profile doesn't do: it judges neither the team nor the suitability of the person who is to take over a task. CORE doesn't assess candidates. It also says nothing about the agency's offer, prices or market. The owner decides what he hands over, and you lead the conversation.

The QuickCheck is free and takes about 15 minutes; today you secure your spot through the waitlist. CORE Navigator with your personal CORE profile and Sprints & Checklists costs €247 plus VAT, one-time. How coaches use CORE with clients is on the page for coaches.

FAQ

As a coach, how do I start role clarification with an owner who can't delegate?

Start with his actual week instead of delegation tips. Have him keep a task log for two weeks, and in the conversation separate the role he wants from the role he fills today. The gap between the two shows where handovers should start.

How does a coach decide with an agency owner which tasks to hand over?

Go through each task and decide between keep, hand over and drop. The yardstick is the owner's target role: what belongs to it, he keeps; what is necessary but belongs to another role, he hands over; what is only habit, goes. Start with a task that takes a lot of time and has little leverage.

Which tools help with an agency owner who is stuck in day-to-day operations?

A task log and a seat map help most, plus a written decision scope agreement for each handover. The Eisenhower matrix sorts priorities within his own role, and the GROW model gives each session a conversation sequence. A work style profile can add to the diagnosis.

How do I support an entrepreneur moving from specialist work to leadership?

Treat it as a change of role. Agree which specialist work he deliberately keeps, and describe leadership work as fixed dates. After that he measures success by what the team gets done without him, not by his own output.

Do I need an assessment for this process?

No. The process also works with just a task log, a seat map and good questions. A profile like CORE Navigator can shorten the diagnosis because it gives pointers to the owner's way of working before the first session. You check those pointers against the actual tasks.

Further reading

• Business coaching with CORE
• From founder to managing director: which seat to hand over first
• Exhausted despite growth: your 60-hour week is a seat problem
• Why scaling is not an ops problem but a founder problem
• For owners

Sources

• Dwight D. Eisenhower, address to the Second Assembly of the World Council of Churches, Evanston, Illinois, 19 August 1954, per the American Presidency Project transcript, quoted and discussed by Quote Investigator: https://quoteinvestigator.com/2014/05/09/urgent/ , retrieved 2026-10-26.
• Stephen R. Covey, The 7 Habits of Highly Effective People, 1989, Habit 3 "Put First Things First". Summary: https://en.wikipedia.org/wiki/The_7_Habits_of_Highly_Effective_People , retrieved 2026-10-26.
• GROW model: https://en.wikipedia.org/wiki/GROW_model , retrieved 2026-10-26. First published in John Whitmore, Coaching for Performance, 1st edition 1992. Authorship is disputed between Whitmore, Graham Alexander and Alan Fine, so the text names all three.