EOS for Leaders: The Six Components, the Level 10, and Why Operating Systems Fail

I've sat in a lot of leadership team meetings over the years. A few of them were sharp. The rest were a slow leak of two hours I'll never get back.

The difference was almost never the people. The people in the room were smart. They cared. They wanted the business to win.

The difference was whether the room had a system.

That's what EOS does. The Entrepreneurial Operating System — built by Gino Wickman, written down in Traction — gives a leadership team a common operating system to run on. Same vocabulary. Same rhythms. Same way of holding each other accountable. It's not magic. It's not new. It's a framework that takes the friction out of running a business so the leadership team can actually lead.

I'm not writing today to sell you on EOS. Plenty of people have done that already, and Wickman doesn't need my help. I'm writing because I've watched what happens to leaders who run their company without an operating system, and I've watched what happens to leaders who pick one and commit. The gap between the two is enormous.

Here's what I've learned about EOS — what it gets right, where leaders break it, and how it ties into the work we do at Kairos.

The Six Components Are Not Optional

EOS is built on six components: Vision, People, Data, Issues, Process, and Traction. Wickman calls them components, not steps. There's no order to work through. There's no light version. If your leadership team is weak on any one of the six, the business will lean.

I see it most often in Vision and People.

Vision sounds easy. Every founder I know can talk about their vision for an hour. The problem is the leadership team usually can't. They can each describe their version, and the versions don't match. Ask five executives at the same company what the three-year picture is and you'll often get five answers. That's not a vision problem. That's a clarity problem dressed up as a strategy problem.

The Vision/Traction Organizer is the EOS tool that fixes it. Eight questions. Two pages. Core values, core focus, ten-year target, marketing strategy, three-year picture, one-year plan, quarterly rocks, issues list. Eight questions that, if a leadership team answers them honestly and together, will reveal every fracture in the business in a single afternoon.

I've watched leadership teams refuse to do it. Not because they don't believe in the tool. Because they don't want to find out they disagree.

People is the second one leaders flinch at. EOS uses two filters: right person, right seat. Right person means they fit the core values. Right seat means they have the skills, the desire, and the capacity to do the job. The People Analyzer turns it into a scorecard.

The flinch happens when the scorecard reveals what the founder already knew. Someone they like, someone they've worked with for years, doesn't fit either filter. The honest move is to have the conversation. The easy move is to keep them and rationalize the cost. Plenty of leadership teams pick easy. And then the business pays for it for the next three years.

The Level 10 Meeting Is the Force Multiplier

If I had to name the single highest-leverage tool in EOS, it would be the Level 10 Meeting.

Ninety minutes. Same time every week. Same agenda. Five-minute segue, then scorecard review, rock review, customer/employee headlines, to-do list, then IDS — Identify, Discuss, Solve — for the rest of the time. Rate the meeting one to ten at the end.

Sounds boring. Looks like every other meeting agenda you've ever seen.

It's not. The Level 10 works because it forces the leadership team to spend most of their time solving issues, not reporting on them. The reporting is done in the first fifteen minutes. The remaining seventy-five are spent attacking the things that are actually slowing the business down.

I've sat in leadership team meetings where ninety minutes were burned on status updates. Everyone went around the room. Everyone described what they were working on. No one made a decision. No one solved anything. The meeting ended, everyone went back to their desks, and the same problems showed up again the next week.

A real Level 10 meeting is uncomfortable. It surfaces conflict because the issues list is a public list of what's broken. You can't hide. The CEO can't hide. The VP of Sales can't hide. The issue is on the board and somebody has to own solving it before the meeting ends.

That discomfort is the point. The discomfort is what makes the business get better.

Rocks Beat Goals

EOS calls quarterly priorities "rocks." Each person on the leadership team gets three to seven rocks per quarter. A rock is a SMART goal — specific, measurable, attainable, relevant, time-bound — that has to be done in ninety days.

The reason rocks beat annual goals is simple. Annual goals are too far away to feel real in February. By the time October comes around, the goal has either drifted or the world has changed enough that nobody remembers what the original target was.

Ninety days is short enough to feel urgent. It's long enough to do something meaningful. And it forces the leadership team to make trade-offs every single quarter, because nobody can carry forty-seven priorities at once.

The discipline I've watched separate good EOS shops from average ones is rock completion rate. If your leadership team completes 80% of their rocks each quarter, the business will compound. If they complete 40%, you don't have a strategy problem. You have a focus problem. You're committing to more than your team can execute, and the rocks are revealing it.

The fix is harder than it sounds. The fix is saying no. The fix is leaving things off the rocks list that genuinely matter, because the leadership team only has the capacity to truly move three to seven things in ninety days.

Where Leaders Break EOS

I've watched enough teams adopt EOS to see the pattern of how it fails.

It fails when the CEO uses it as a control mechanism instead of an operating system. EOS works because everyone on the leadership team owns a piece of it. The CEO doesn't run the Level 10. The integrator does. The CEO doesn't write everyone's rocks. The leadership team writes their own and commits to them. The moment the CEO turns it into a top-down compliance exercise, the energy leaks out and the team starts going through the motions.

It fails when the leadership team uses EOS for the operations but skips the people work. The People Analyzer and the right-person-right-seat framework are uncomfortable. Leadership teams will happily run Level 10s for two years and never once have the honest People conversation. The business stays stuck because the seats are wrong, but nobody wants to say it out loud.

It fails when leaders treat EOS as the whole answer. It isn't. EOS is an operating system for the business. It's not an operating system for the leader. A leader running a tight EOS shop can still be a wreck personally. The marriage can still be on fumes. The spiritual foundation can still be missing. The discipline of the Internal bridge can still be untended. EOS won't fix any of that. EOS will give you a clean P&L while the rest of your life rots.

That last one is where I've seen the most damage. Smart founders who bought into EOS, ran their business well, hit their numbers, and lost their wife and their kids and their faith on the way.

How EOS Fits the Five Bridges

This is why we don't just talk about EOS at Kairos. We talk about EOS in the context of the Five Bridges.

The Environment bridge is the home for EOS. EOS is the system that runs the room. It's the operating system of your business. Getting the Environment bridge right means the meetings, the rhythms, the structures, the team — everything the leader operates inside — is built to make winning easier instead of harder.

But the Environment bridge is one of five. If a leader builds a tight Environment bridge while the Spiritual, Internal, Relationships, and Legacy bridges are crumbling, the business will run well for a while and the man will run out.

The work at Kairos is the integration. EOS gives the business the bones. The Kairos Code gives the man his foundation. The Five Bridges keeps the whole life aligned. The combination is what holds.

Action Items From Today

1. Score yourself honestly on the six components. Vision, People, Data, Issues, Process, Traction. Give each a rating one to ten. The lowest score is where you start the work. Don't fix the strong ones — fix the weak ones.

1. Audit your last four leadership meetings. Were they Level 10s, or were they status updates? If less than 60% of the time was spent on IDS — identifying, discussing, and solving real issues — you don't have a leadership meeting. You have a reporting meeting. Rewrite the agenda this week.

1. Look at your current rocks. Are there seven? Twelve? Twenty? If anyone on your team has more than seven rocks for the quarter, you don't have priorities — you have a wish list. Cut it back to the real ones.

1. Run the People Analyzer on your leadership team. Right person, right seat. Be honest. If someone fails both filters, you already know what the conversation is. Stop avoiding it.

1. Pick a real integrator. If you're the visionary and you're also trying to run the Level 10 and chase down the to-do list, you're going to burn out and the business will plateau. The integrator role is not optional. Find them, hire them, or develop them.

Five Bridges Challenges

Environment — Score your operating system this week. Pull out the Vision/Traction Organizer, the Accountability Chart, and your last four meeting agendas. Where are the gaps? Pick the single weakest spot and put it on next week's leadership meeting issues list.

Internal — Check what EOS isn't fixing. A tight business doesn't fix a tired man. Where in your own life have you been letting the business carry the weight of an internal practice you've stopped doing? Name it this week and rebuild it.

Legacy — Ask the long question. EOS gives you the next ninety days. The Legacy bridge asks about the next ninety years. If your business runs flawlessly for the next decade but the rest of your life doesn't, what was it for? Write the answer down before the next quarterly meeting.

Inspire & Impact,

Josh