Too Small for EOS? EOS Was Designed for 10–250 Employees — Here's the Version for One

Updated: 5 days ago
Too Small for EOS? EOS Was Designed for 10–250 Employees — Here's the Version for One
Start with the honest part: EOS is good.
The Entrepreneurial Operating System, from Gino Wickman's book Traction, has helped a lot of companies stop running on chaos. Its six components are sound — six questions every real business has to answer, and most one-person businesses are answering at least three of them badly.
But EOS was not built for you, and EOS doesn't pretend otherwise. Its own stated sweet spot is entrepreneurial companies with 10 to 250 employees — companies with a leadership team. A solo-founder analysis puts it plainly: solo operators are not in the design specification. Even an EOS implementer has said on record that EOS "is not designed for startups," and that "the work is often harder when you're a solopreneur."
A business of one has the opposite problems — and the same six questions, wearing different clothes.
Here is EOS, component by component, translated for one.
1. Vision → a one-page compass
EOS starts with vision: everyone seeing the same future, written down — where you're going, who you serve, what makes you different.
For a team, the point is alignment. At size one that sounds like a joke — nobody to align. But ask a solo operator where the business is going, in writing: it's three different answers depending on the day, changing every time a shiny idea walks past. That's a drift problem, worse solo because nobody asks you the question out loud.
The version for one: a single page — call it a compass — stating your target, customer, purpose, red lines, and real advantages, stored somewhere your system reads before it acts. It decides for you on days you're too tired to decide well, and tells your tools and AI help when to proceed and when to stop and ask.
2. People → seats filled by systems, not hires
EOS asks: right people in the right seats, and is every seat on the accountability chart owned by exactly one person?
The seats don't disappear when the staff does. Your business still has a marketing seat, a sales seat, a delivery seat, a follow-up seat, a "remember everything" seat. One name fills every box — you — usually badly: follow-up gets done at midnight and marketing never.
The version for one: draw the seats anyway, then assign each honestly — to you, to a system, or to no one yet. Some seats are yours forever: judgment, relationships, the work customers buy. But follow-up, remembering, "post it on schedule"? Those are desks in my business — defined functions worked by AI agents under written rules, inside a system that keeps the record. The question changes from "who do I hire for this seat" to "does this seat need a human at all?"
3. Data → a weekly scorecard for one
EOS runs on a scorecard: a handful of numbers, reviewed weekly.
This component needs almost no translation, because solo operators run on feelings: busy feels like progress, a quiet week like failure, neither is data.
The version for one: five to ten numbers, once a week, in one sitting. New contacts. Conversations started. Follow-ups done. Things shipped. Money in. The point isn't the numbers — it's a weekly moment where truth is written down instead of felt, and a bad number becomes an issue to solve instead of a mood to carry.
4. Issues → a written list, solved in a review — not in your head
EOS is blunt about issues: keep a written list and work it weekly — identify, discuss, solve, write down the decision.
The solo failure mode is specific and miserable. You do hold the meeting — continuously, in your head, at 2 a.m. Nothing gets decided, and the same five issues return every week, because a decision made in the shower has no record and no force.
The version for one: the list is kept by the system, not by your anxiety. Problems get captured as they occur — by you in a sentence, or by your desks when something stalls. Once a week, in the scorecard sitting, you work it: decide, and write the decision into the record where the system can enforce it. A solved issue in a business of one isn't a conversation that went well. It's a rule that changed.
5. Process → procedures only where a mistake is expensive
EOS wants your core processes documented and followed by everyone — that's how quality survives growth in a 50-person company.
For one person, documenting everything is a trap — manuals written for an audience of yourself, never opened again. Keep the discipline, drop the bulk: write a procedure only for a step that is high-stakes and high-error — money moves, something irreversible gets sent, a promise gets made, a mistake costs reputation. Everything else stays loose.
At size one, a procedure has a second job: it's the instruction set a system or AI desk follows to do that step for you — and how a seat from component two actually gets filled.
6. Traction → 90-day priorities sized by real sessions
EOS ends with traction: a short list of 90-day priorities — "Rocks" — plus a weekly rhythm that keeps them moving.
Solo operators copy this and fail because they size the quarter like a company. A leadership team setting three Rocks commits several people's full-time work. You are committing the leftover hours around a job, a family, and sleep — pretend otherwise, and the quarter ends in guilt instead of results.
The version for one: before setting a priority, count your real sessions. How many actual work sittings will this business get in the next 90 days — honestly, from your calendar, not your intentions? Then size the priorities to that count. One priority that fits beats four sized for a team you'll never have. Ninety days is the right horizon; the math underneath it has to be yours.
The principles are good. The machinery assumes a payroll.
That's the whole article. A business of one needs all six answered, which is why EOS keeps attracting solo operators. What doesn't fit is the machinery bolted onto the answers: leadership team, org chart of employees, meeting of department heads. Translate the machinery — compass, desks, scorecard, written issues, lean procedures, session-sized priorities — and the system runs at size one. And if you grow into a team of ten or twenty someday, EOS as written may genuinely fit you then. It's the on-ramp, not the enemy.
Start by walking the six components above and asking which one is your bottleneck.
The scorecard runs inside SuccessBrian OS — and it is free
SuccessBrian OS is the system I run my own one-person business on. The weekly scorecard from this article works inside it.
In plain words: once a week, you type in five numbers — new leads, sales talks, work delivered, things shipped, cash in. The system keeps them, shows you which ones hit your target and which ones fell behind, and remembers the plan and the promise you made. You do not have to keep a spreadsheet alive. You do not have to remember anything. The system remembers for you.
It costs nothing. There is no form to fill out and nothing to buy. Download it and use it:
Rather start on paper? The scorecard template is printed in full on this blog, in "The Weekly Scorecard for a One-Person Business." Start there if you like. Just start this week.
SuccessBrian OS is not affiliated with EOS Worldwide. EOS, Traction, and the component names above are theirs, named here for comparison; the fit and implementer remarks are from EOS's public positioning and published analysis read in November 2026.
Read more from Brian Lathe on Substack
This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.
Comments