How do you reduce it?
Six steps. Do them on one area. Then do them again on the next area that still stops without you.
-
1
See where the owner gets pulled in
For a few weeks, write down each time work stops for the owner: an approval, a rescue, a question, or a relationship.
-
2
Sort by cause
Group the log by why it came back: a missing decision right, a missing standard, a relationship only the owner holds, missing access, or a habit.
-
3
Decide what transfers first
Score each area from 1 to 5. Transfer an area that stops without the owner before an area that only needs the owner for exceptions.
-
4
Transfer the decision right, the standard, and the limit
Hand a named person the decision right, the standard the work has to meet, and an approval limit they can use without calling the owner.
-
5
Test with an absence window
The owner steps out of that area on purpose. Two consecutive weeks is long enough that the team cannot simply wait. If the work still moves, the transfer held. If it stacks up, the transfer is incomplete.
-
6
Repeat
Take the next area that still stops without the owner. Run the same sequence: see the pull, sort the cause, transfer the decision right with a standard and a limit, and test it with an absence window.
What should transfer first?
The score decides the order. Transfer an area that stops without the owner before an area that only needs the owner for exceptions.
Inside an engagement, each area is scored from 1 to 5. 1 means the area runs without the founder. 5 means it stops without the founder. The score is how far the work gets without the founder, not how busy the founder feels. These are the same five reads used on the Founder Dependency Audit.
A founder dependency audit is a structured review of where an owner-led business still depends on the owner. It names the decisions, relationships, standards, and access that stop when the owner is not in the room.
-
1
Runs without the founder
Decisions, standards, and access sit with the people who do the work. The founder is informed, not required.
-
2
Exceptions only
The founder is consulted on exceptions. Routine work does not need them.
-
3
In the regular loop
The founder is in the regular loop. Non-routine work waits for their read.
-
4
Can start, cannot finish
Most real decisions in the area route to the founder. The team can start the work. They cannot finish it.
-
5
Stops without the founder
The area stops without the founder. Quotes, approvals, hires, or access do not move until the founder is in the room.
Move a 5 or a 4 before you polish a 2. Inside the area, the transfer is always the same three things: the decision right, the standard, and the approval limit. The six places those three things have to land are the same places the audit examines.
Decision rights
Which decisions have a named owner, and which ones still come back. Transfer this with everything else. A person without the right to decide will bring the decision back.
Sales and customer relationships
Quotes, pricing, key accounts, and the vendor calls that wait on the owner. The relationship transfers with a standard for ordinary work and a limit for what still comes back.
Operations and quality approvals
Work that cannot start, ship, or be accepted without the owner's sign-off. The standard has to say what accepted means. The limit has to say which quality holds the owner still sees.
Finance
Spending, pricing exceptions, and the numbers only the owner will release. The approval limit is the transfer. A report is not.
Hiring and people
Who gets hired, who is let go, and the leadership calls the team will not make alone. Name which calls sit with someone else, and which still come to the owner.
Knowledge and access
Logins, files, standards, and know-how that exist only with the owner. Access without a standard moves the confusion. A standard without access still stops the work.
An owner in a specialty trade still signs every change and every quality hold. The crew can start the job. They cannot close it. Over a few weeks the log is the same pull: a change, a punch item, a customer who will only talk to the owner. Sorted by cause, the decision right was never named, the quality standard lives in the owner's head, and no one else has a limit they can approve.
The transfer is a named person for ordinary changes, a written standard for what accepted means, and a limit above which the owner still decides. Then the absence window. If the changes wait in a pile, the standard or the limit is still incomplete. This is not a result. No company is named here.
What usually goes wrong?
Three mistakes put the work back on the owner. Each one looks like progress while it is happening.
Hiring a #2 without handing over decision rights
The new person inherits the system that routes decisions back to you. The seat looks filled. The work still waits. The decision right moves first. Then the hire can hold it.
Documenting without transferring
A binder, a process map, or a shared folder is not a transfer. The decision right, the standard, and the limit have to sit with a named person who uses them when you are not in the room.
The owner taking decisions back
The first exception that comes back, and gets answered, teaches the team to keep bringing exceptions. If you take the decision, say so, and put it back on the log. A transfer you reverse is not a transfer.
How long does it take?
There is no fixed length. One area is done when an absence window does not pile the work back on the owner.
Some areas hold after one window. Some come back because the standard was still in the owner's head, or because the owner took the decision back, and the sequence runs again.
The two-week window tests one transfer. It is not a schedule for the whole company. Do not treat a calendar as a substitute for the test.
Where does Norsten help?
This page is the sequence an owner can run. An engagement is the same sequence, diagnosed across the whole operation.
Norsten Collective works with owner-led companies between $10 million and $100 million in trades, construction, manufacturing, or professional services. Three partners diagnose every engagement. One leads it. Nothing is handed to junior staff.
The path is the Founder Dependency Audit, then The First 90 Days, then The Year. The audit names what still stops when the owner is out of the room. The First 90 Days moves load onto the business. The Year makes strategy how decisions get made.
If you are choosing between kinds of outside help, read embedded leadership advisory vs EOS vs consultants. Advisory can sit alongside an operating system. It does not take the seat.
Questions owners ask.
How do I reduce founder dependency in a $10 million to $100 million owner-led company?
You reduce founder dependency in an owner-led company between $10 million and $100 million by transferring one area at a time: who decides, the standard the work has to meet, and the limit someone else can approve. Then you stay out of that area long enough to see whether the work still moves. If it stacks up, the transfer is incomplete, and you fix the missing piece before you move on.
What should transfer first?
Score each area from 1 to 5. Transfer an area that stops without the owner before an area that only needs the owner for exceptions. The areas are decision rights, sales and customer relationships, operations and quality approvals, finance, hiring and people, and knowledge and access. A transfer is the decision right, the standard, and an approval limit, held by a named person.
What are the common mistakes when reducing founder dependency?
Hiring a #2 without handing over decision rights. Documenting the work without transferring it. Taking decisions back after the transfer, which teaches the team to keep bringing them.
How long does it take to reduce founder dependency?
There is no fixed length. One area is done when an absence window does not pile the work back on the owner. Some areas hold after one window. Some come back because the standard was still in the owner's head, or because the owner took the decision back. The two-week window tests one transfer. It is not a schedule for the whole company.
How is founder dependency scored?
Inside an engagement, each area is scored from 1 to 5. 1 means the area runs without the founder. 5 means it stops without the founder. The score is how far the work gets without the founder, not how busy the founder feels.
What is a founder dependency audit?
A founder dependency audit is a structured review of where an owner-led business still depends on the owner. It names the decisions, relationships, standards, and access that stop when the owner is not in the room.
A diagnostic conversation.
The purpose is diagnosis, not performance. We will tell you what we see, including when what you need is not us. If there is a fit, we say so directly. If there is not, we say that too.
Apply for a Conversation