We Run on EOS But Still Depend on One Leader

By Lisa Gonzalez, Certified EOS Implementer® and co-author of Process! (The EOS Mastery Series). Updated October 3, 2026.

If you run on EOS® and the business still depends on one person, that is a Process Component problem, not a Vision or People problem. The work still lives in somebody's head. Document your five to twelve core processes and get them Followed By All, starting with the ones that person is the backstop for.

I'm Lisa Gonzalez, Certified EOS Implementer® and co-author of Process!, the book in the official Traction® Library on this component. I self-implemented EOS in our own residential remodeling company before I became an Implementer, and I was the bottleneck for longer than I want to admit.

Why does EOS fix so much and leave this?

EOS gives a leadership team traction quickly. Vision gets clear. The Accountability Chart sorts out who owns what. The weekly Level 10 Meeting™ surfaces issues instead of burying them. Those three show results in weeks.

Process does not. It pays off over quarters, so it goes last on almost every list. EOS Worldwide names the symptoms of a weak Process Component directly: inconsistent quality, training challenges and key-person dependency. That third one is the thing you are feeling.

So the business gets better at deciding and worse at operating without you. Everything that is still undocumented routes back to whoever knows it. Across hundreds of workshops and consulting engagements, I consistently see 5 to 10% of profit leaking out through those gaps.

How do you tell a process problem from a people problem?

Ask what happens when the question reaches you. Three different answers, three different fixes.

"Nobody wrote down how we do this." A process problem. Document it.
"It's written down and they didn't follow it." Still a process problem, the harder half. It was never trained, measured or managed.
"The right person isn't in the seat." A People problem. The Accountability Chart and the People Analyzer handle that, not a document.

Most leaders I meet assume the third. It is usually the first two.

Where do you start?

Not with everything. Start with the processes where one person is the backstop.

List what still routes to that person. For one week, write down every question that only they can answer. The list is your evidence.
Find which core processes those questions sit inside. Most companies have five to twelve core processes. The questions will cluster into two or three of them.
Make the heaviest one a Rock. One core process, one quarter, one owner. Your Integrator holds the plan.
Document it as an outline. The core process is the 20% of steps that drive 80% of the results, usually one to five pages. Then pick one or two sub-processes underneath it to roll out this quarter.
Get it Followed By All. Train it, put one number on your Scorecard, give it a standing spot in your Level 10 Meeting, and update it when things change.

That last step is the one that ends the dependency. A documented process that nobody follows routes right back to the person who knows it.

How long before it actually feels different?

One quarter per core process, and you feel the first one. Process! puts the whole journey, every core process documented and followed, at nine to twelve months (Ch. 3 and 4).

The honest test is a calendar test. Block two weeks and leave. Whatever breaks is an undocumented process. Whatever people call about is a process that still lives in someone's head. That list is your next two quarters.

When this is not a process problem

The leader does not actually want to let go. No document fixes that. It is worth naming out loud before anyone writes anything.
There is no Integrator. Someone has to hold the leadership team to the plan week after week. Without that seat filled, process work stalls by week three.
The Accountability Chart is wrong. If two people think they own the same seat, or nobody owns it, documenting the work just records the confusion.

Frequently asked questions

We run on EOS but still depend on one leader. Is that normal?
Yes, and it is the most common gap I see in companies a year or two into EOS. Vision, People and the meeting rhythm get built first because they pay off fastest. Process gets left for last, so the business keeps routing around whatever is undocumented. Key-person dependency is one of the named symptoms of a weak Process Component.

Is key-person dependency a Process problem or a People problem?
Usually Process. Ask what happens when a question reaches the leader. If the answer is "nobody wrote it down" or "it is written down and they did not follow it," that is Process. If the answer is "the wrong person is in the seat," that is People, and the Accountability Chart handles it.

Which process should we document first?
The one generating the most questions that only one person can answer. Track those questions for a week, see which core process they cluster inside, and make that core process a Rock. Starting with the easiest process feels productive and changes nothing.

How long does it take to get the business running without that one leader?
Plan on one quarter per core process to feel real change, and nine to twelve months for the full journey, every core process documented and followed. The dependency drops as each one gets Followed By All, not when the documents are written.

Will documenting our processes actually reduce the dependency?
Only if people follow them. Documenting is the easier half. The half that ends the dependency is training the process, measuring it on your Scorecard, managing it in your weekly meeting and updating it when things change. Teams that stop at documented stay dependent.

Do we need an EOS Implementer to fix this?
No. The tools are the same with or without one. An EOS Implementer® adds an outside view and holds the leadership team to the work, which matters most when the same process issue keeps returning to your Issues List. Self-implementing teams can run the whole plan themselves.

What if the leader does not want to let go?
Then no amount of documentation will help, and it is worth saying so plainly before the team spends a quarter on it. This is a leadership team conversation, not a process exercise. Once the decision is real, the process work goes quickly.

Related guides

Want to know what the dependency is costing you? The Profit Leak Calculator puts a number on it in about two minutes. Then Process Success: Get Your Processes Followed By All walks your leadership team through the fix, one step a week. Book a discovery call.