EOS & Operations · September 18, 2026 · 8 min read
How EOS Fails Without the People Work — The Foundation Nobody Pours
EOS is scaffolding, not a foundation. The People Component is the foundation, and it's the one part almost every founder skips — because it costs a relationship.
I sat in a Level 10 Meeting last month with a company doing $18M in top-line and losing an integrator every fourteen months on average.
Their Rocks were tight. Their scorecard was clean. Their VTO was framed on the conference wall. Somebody had clearly read Traction more than once and highlighted the good parts.
Ninety minutes into the meeting I watched the founder cut off his COO mid-sentence for the third time. She stopped, waited, then agreed with him. Nobody in the meeting flinched. This was the pattern. This was the culture. This was why the last integrator quit and the one before her quit and the one before him quit.
They didn't have an EOS problem. They had a People problem wearing an EOS jersey.
EOS Is Scaffolding, Not a Foundation
The best thing about EOS is also the thing that gets founders in trouble.
It gives you a language for what was previously invisible. You suddenly have words for the Vision/Traction Organizer, for Rocks, for Issues, for IDS. You have a cadence — weekly L10, quarterly pulse, annual planning. You have a scorecard where before you had a hunch.
The scaffolding is genuinely useful. I run EOS. I coach EOS. I have watched EOS turn a chaotic $4M shop into a disciplined $12M business inside eighteen months.
But scaffolding is not a foundation. And the foundation of every EOS install is the People Component — the "right people, right seat" work — which almost nobody actually does.
Founders skip it because it's the one part of EOS that costs a relationship. Rocks cost time. Meetings cost calendar. IDS costs ego for maybe ten minutes. But right person, right seat costs you the moment where you have to sit across from someone you've built the last seven years with and tell them they are not the person for what comes next.
The average founder would rather run five perfect Level 10 Meetings a week for the next two years than have that one conversation once.
The Skip Shows Up Downstream
You cannot tell if a founder skipped the People work by looking at the EOS binder. You can only tell by watching what happens in the meetings six months later.
Here's what the skip looks like in the wild.
The scorecard doesn't move. You've had the same yellow numbers for eleven weeks. Nobody owns them because the person accountable can't actually do the work of the seat they're in. Everyone at the table knows it. Nobody says it. The scorecard becomes a weekly ritual of watching the same failure with better lighting.
IDS becomes performance. Real IDS requires the person who owns the issue to actually have the authority and the capacity to solve it. When the wrong person is in the seat, every IDS session ends with a "we'll circle back" or an "I'll take that offline." The issues list grows and the pattern of unresolution grows with it.
Rocks slip in the same seats every quarter. You will see the same three department heads miss their Rocks four quarters in a row. Everyone will nod and set new Rocks. Nobody will name what is actually happening, which is that those three seats are being run by people who cannot deliver the work of those seats.
The Integrator turns over. The Integrator is the canary. When you burn through Integrators, you don't have an Integrator problem — you have a founder-who-hasn't-done-the-People-work problem. The Integrator is trying to hold accountable a leadership team the founder refuses to restructure, and eventually the Integrator quits before losing her reputation.
The scaffolding will hold up all of this for a surprisingly long time. That's the danger. It buys you eighteen to twenty-four months of the appearance of operational discipline while the actual foundation quietly rots.
The People Work Is a Character Test for the Founder
Here's the part nobody says out loud at EOS conferences.
The reason most founders don't do the People work is not that they don't know it needs to be done. They know. They've read the book. They've hired the EOS Implementer and heard it explicitly.
They don't do it because doing it exposes something about them. About the hires they made from a place of loneliness instead of clarity. About the loyalty debt they've been paying with company equity for six years. About the version of themselves that was too insecure to hire people better than them, so they hired people they could stay bigger than.
Every time a founder tells me "I just can't let her go, she's been with me since the beginning," what he's actually saying is "I don't want to look at the version of me who hired her, and I don't want to build the version of me who can build without her."
That is a Five Bridges problem, not an EOS problem. Specifically it's an Internal bridge problem — the standard he holds when no one is watching. And no operating system will fix an Internal bridge that has quietly given itself permission to avoid the hard conversation for another quarter.
What the People Work Actually Requires
If EOS is scaffolding and the People work is the foundation, then the foundation has three specific pieces that founders skip. Fix these three and the EOS install starts producing what it promised.
One: Honest quarterly seat reviews on every seat, including the founder's. Not a performance review. A seat review. Is this person right for this seat right now, given where the company is going in the next twelve months? The answer is either yes, no, or "not without significant development that we're going to invest in on a defined timeline." Any other answer is a dodge.
Two: The willingness to move an "A player in the wrong seat" out of the seat, even if it costs you the relationship. This is where founders fail most often. An A player in the wrong seat is worse than a B player in the right seat, because the A player's presence prevents you from ever finding the right person. And the A player usually knows they're in the wrong seat and is quietly resenting you for not naming it.
Three: Firing the wrong person on time, not eighteen months late. Every founder I've coached has an "I should have done that a year sooner" story. Nobody has an "I fired her three months too early" story. If the pattern is one-directional, the lesson is one-directional. Set a decision date. Hit it.
The Bridge Builder Mastermind is honest about this because half the men at the table are running EOS companies and half of them have skipped the People work. The group is the mirror that says the thing your Integrator has been trying to say for six months.
The Scoreboard You're Not Looking At
There's a scorecard EOS teaches you to build for the business. Weekly numbers. Leading indicators. Green, yellow, red.
There's another scorecard nobody teaches you to build. It's the People scorecard.
Right seats currently filled with right people, on a scale of one to ten. Number of A players in wrong seats today. Number of B and C players you've been carrying past their expiration date. Number of leadership team members you'd re-hire if you were starting the business tomorrow. Number of direct reports who tell you the truth without softening it first.
You can run that scorecard on a Sunday afternoon in twenty minutes. The number that comes back will tell you whether your EOS install is going to compound over the next three years or quietly collapse under a foundation you never poured.
The LQ Assessment is the personal version of the same idea — five bridges, five scores, one honest picture. If your operating system is only measuring the business, you are flying half blind. Fix that this week.
Action Items From Today
- Run the People scorecard on your leadership team today. For each seat, write a one-word answer: yes, no, or develop. If you write "develop," write the specific 90-day plan next to it. If you can't write the plan, the honest answer is no.
- Name the one A player in the wrong seat you've been avoiding. Write down the conversation you owe them. Put it on your calendar for the next fourteen days. Do not push it.
- Ask your Integrator (or your #2) one question this week: "What am I refusing to see about our team?" Do not defend the answer. Take notes.
- Audit your last three L10 Meetings for the same yellow scorecard numbers. If a number has been yellow for four weeks and no IDS session has resolved it, the problem is not the number. The problem is the seat.
- Set a decision date for the one termination you've been putting off. Write the date. Tell your Integrator or a mastermind peer the date so it's witnessed. Then hit the date.
- Write your own founder seat review. Am I the right person for the CEO seat given where the company is going in the next twelve months? Answer honestly. If the answer is "not without development," write the development plan.
Five Bridges Challenges
Internal bridge: Look at the last time you delayed a hard people decision. What was the actual cost to the team of that delay? Name it. If you cannot name it, you have not yet paid for it — and it's still coming due.
Environment bridge: Sit in your next leadership meeting and count how many times someone starts a sentence with "I'll take that offline." That number is a leading indicator of a team where the wrong seats are protected. Bring the count to your Integrator afterward.
Legacy bridge: In ten years, when someone on your leadership team tells the story of working for you, will they say you had the courage to make the hard people decisions, or the tolerance to avoid them? Write the sentence you want them to say. Then reverse-engineer the decisions this quarter that make it true.
Bridge Builder Mastermind is where this work gets done in a small cohort of operators.
Inspire & Impact,
Josh