Most companies that tell me EOS stopped working never really ran it. They adopted the words, skipped the discipline, and blamed the framework when execution started to feel heavy. Of all the ways an operating system fails, this is the most common, and the easiest to miss from the inside.
That's my opinion, and plenty of people will disagree with it. But I've never seen a team fail because the framework was wrong. I've seen a lot of them fail because they stopped doing it.
The problem: borrowed language
Here's what borrowing the language looks like from the inside.
The leadership team calls its priorities "Rocks," but there are 14 of them and half are projects that were already happening. The scorecard exists, but somebody fills it in Monday night so it doesn't look empty. The weekly meeting happens most weeks, runs long, and ends with the same 3 issues still on the list. To-dos get assigned with no date and quietly disappear.
Everyone uses the vocabulary. Nobody changed their week.
This is worse than having no system at all. With no system, at least everyone knows the company is running on the founder's memory. With a borrowed one, the team believes it has discipline it doesn't have. Problems hide behind the right words.
Why you can't run the parts you like
The common approach is to adopt the pieces that feel useful and skip the rest. Keep the weekly meeting, drop the scorecard. Keep the quarterly priorities, stop tracking to-dos.
It doesn't work, because the parts hold each other up.
The scorecard tells you what's off track before the financials arrive. The issues list is where those problems go. The weekly meeting is where they get solved. The to-dos are how the solutions actually happen. The quarterly priorities keep the whole thing pointed at what matters most this quarter.
Pull one out and the others start compensating. The meeting gets longer because there's no scorecard to flag exceptions. The issues list gets longer because nothing turns into a to-do. The founder starts carrying it all in their head again. Execution gets heavier, and the team concludes the system is the problem.
Score behavior, not intent
The fix is simple, and most teams skip it. Once a month, the leadership team scores how well it actually ran the system. Not how committed everyone feels. What happened.
I'd ask five questions, one for each part:
- Scorecard: Did we have 5 to 15 numbers, updated before the meeting, with an owner on each?
- Priorities: Could every leader name the company's few priorities for this quarter without looking?
- Issues: Did the real issue make the list, or did we talk around it?
- To-dos: Did at least 90% of last week's to-dos get done?
- Meeting: Did it start on time, end on time, and spend most of its time solving?
Score each one honestly. The lowest score is where your execution is leaking. Fix that one first and leave the rest alone for a month.
The rule I give every team: score observed behavior, not intent. "We really want to get better at to-dos" is intent. "We closed 6 of 11" is behavior.
The quarterly reset
Every 90 days, step back and reset in four moves.
Review reality. Use the evidence: the scorecard, the priorities you hit and missed, the issues that kept coming back. Not anyone's memory of how the quarter felt.
Name the lessons. What did the business show you that you didn't expect?
Choose focus. Pick fewer priorities than you want to. If everything is important, nothing is important.
Recommit. Go back to the weekly disciplines out loud, as a team, with the scores in front of you.
That's how you build a machine, not a scramble.
What to do this week
Put the five questions on the agenda for your next leadership meeting. Give each leader 2 minutes to score all five, privately, from 1 to 10. Then show the scores side by side.
The gaps between leaders will tell you as much as the scores. If one person rates the issues list a 9 and another rates it a 3, you've found a conversation the team has been avoiding.
Here are the exact words to open it: "We say we run this system. Let's find out whether we do."
Operating System
I built a free tool that walks your team through this. The Operating System tool covers the weekly meeting structure, the scorecard, quarterly priorities, the issues list and to-dos, and it includes a monthly implementation health check that scores what your team actually did. It also walks you through the quarterly reset. Run the health check with your full leadership team so you can see where your scores disagree.
This isn't motivation. It's execution.
Open the Operating System →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →