EOS — the Entrepreneurial Operating System created by Gino Wickman — is known for its toolset. Each tool is simple. Together they cover vision, people, data, issues, process and execution. Here’s what each one does and the business problem behind it. (For the system as a whole, start with what is EOS.)
V/TO — Vision/Traction Organizer
The problem it solves: the vision lives in the owner’s head, and every leader has a slightly different version of it.
What it is: a two-page document. The vision side captures core values, core focus (the company’s purpose and niche), a long-range target, the marketing strategy, a picture of the company a few years out and the one-year plan. The traction side holds the current quarter’s priorities and the issues list.
The generic idea: a one-page or two-page plan everyone can repeat. In BOSS, that’s the Blueprint — see strategic planning for small business.
Accountability Chart
The problem: the org chart shows titles and reporting lines but not who’s actually accountable for what.
What it is: a chart of seats, not people. Each seat lists its main responsibilities, then a name goes in it. At the top, EOS typically shows a visionary and an integrator, with major functions like sales and marketing, operations, and finance below.
The generic idea: seats before people, one name per seat. In BOSS it’s the Ownership Chart — see small business org chart.
Rocks
The problem: too many priorities, nothing finished.
What it is: typically three to seven priorities per quarter for the company and for each leader, each with one owner and a binary outcome: done or not done.
The generic idea: a short list of ninety-day goals. See quarterly business goals.
Scorecard
The problem: nobody knows how the business is doing until the month-end numbers arrive.
What it is: a weekly report of roughly five to fifteen measurables, each with an owner and a goal, usually showing a rolling thirteen-week trend.
The generic idea: a weekly scoreboard of leading numbers. See business scorecard.
Level 10 Meeting
The problem: meetings that wander, run long and end without decisions.
What it is: a weekly ninety-minute leadership meeting, same day and time, with a fixed agenda: a brief check-in, scorecard review, Rock review, customer and employee headlines, the to-do list from last week, a long block for solving issues, and a conclusion where attendees rate the meeting.
The generic idea: a weekly leadership meeting with a fixed agenda that spends most of its time solving problems. In BOSS it’s the Momentum Meeting — see the weekly leadership meeting agenda.
IDS — Identify, Discuss, Solve
The problem: teams talk about issues for weeks without resolving them, or solve symptoms instead of causes.
What it is: a three-step method. Identify the real root issue (often not the one first stated). Discuss it once, openly, with everyone contributing. Solve it with a decision and a to-do that has an owner.
The generic idea: a disciplined problem-solving method in the weekly meeting. See how to solve problems in team meetings.
People Analyzer and GWC
The problem: keeping people who don’t fit the culture or aren’t right for their role, because nobody has a fair way to evaluate it.
What it is: the People Analyzer rates each person against the company’s core values. GWC asks whether each person gets their seat, wants it and has the capacity to do it.
The generic idea: evaluate people on values fit and seat fit. See hiring the right people and company core values.
Core processes
The problem: work depends on who’s doing it.
What it is: EOS asks companies to identify their handful of core processes, document them at a high level and make sure they’re followed by all.
The generic idea: documented, simplified, owned processes. See process documentation.
Common mistakes with these tools
- Too many Rocks. More than a handful per person means nothing gets finished.
- Scorecards full of lagging numbers. Revenue and profit tell you what happened, not what’s about to happen. See leading vs lagging indicators.
- Skipping the issues block. Meetings that spend all their time on reports never solve anything.
- Charts built around people. Drawing seats to fit current employees defeats the purpose.
- Treating tools as paperwork. The tools exist to drive conversations and decisions, not to be filled out.
A note on trademarks and affiliation
EOS, Traction, V/TO, The Accountability Chart, Level 10 Meeting, IDS and related names are trademarks of EOS Worldwide. I describe them here for education and comparison. I’m not an EOS Implementer and I’m not affiliated with EOS Worldwide. If you want to run EOS, read Traction and consider whether to self-implement or work with an implementer.
If you’d prefer a simpler system built for AI-first operations, the BOSS framework uses the same underlying ideas in its own language and toolset.
Next steps
Read Traction book summary for the big picture, or compare systems in best business operating system. If you want help putting any of these ideas to work, request a strategy call.
Questions people ask
What are EOS Rocks?
Rocks are the small number of most important priorities a company, team or person commits to completing in the next ninety days. Each Rock has one owner and is either done or not done at the end of the quarter.
What is a Level 10 Meeting?
The EOS weekly leadership meeting: a ninety-minute meeting with a fixed agenda covering a check-in, the scorecard, Rock status, customer and employee headlines, the to-do list, solving issues using IDS, and a conclusion with ratings.
What is IDS in EOS?
IDS stands for Identify, Discuss, Solve. It’s EOS’s method for working through issues: identify the real root issue, discuss it once openly, and solve it with a clear decision and to-do.