The Traction book, written by Gino Wickman and published in 2011, is a complete operating system for small and mid-sized businesses. It describes a framework called EOS, the Entrepreneurial Operating System, and gives you a step-by-step process for implementing it. If you run a company between 10 and 250 people and you feel like the business is running you instead of the other way around, this is the book most operators point to as the turning point.
The core claim is simple: most businesses fail to get traction not because the idea is bad or the team is wrong, but because they have no operating system. No shared language, no accountability structure, no meeting rhythm, no honest data. Traction gives you all of those things in one framework.
Traction by Gino Wickman summary
Wickman opens with a diagnosis most founders recognize immediately. The business has grown past the point where a founder can hold everything in their head, but it has not grown into a real organization with real accountability. People are unclear on priorities. Meetings feel like a waste of time. The same problems keep coming back. Growth has stalled or become chaotic.
His solution is EOS, the Entrepreneurial Operating System, built around six components that every business needs to master. He calls this the EOS Model. The book walks through each component in turn, gives you the tools to build it, and then describes the implementation sequence.
What makes Traction different from most business books is that it is a practitioner manual, not a theory text. Wickman spent years implementing this system with real companies before writing it down. The tools are specific. The Level 10 Meeting format has a precise agenda. The Rocks concept has a precise definition. The Scorecard has a precise structure. You do not have to interpret very much. You can take the tools and start using them this week.
The book ends with a chapter on getting started that tells you exactly which tool to implement first and in what order. That specificity is rare and genuinely useful.
Traction EOS
EOS, the Entrepreneurial Operating System, is the operating framework the Traction book introduces. It is not a piece of software. It is a set of disciplines: specific tools, meeting rhythms, and accountability structures that a leadership team runs together.
Wickman designed EOS around three foundational activities that every leadership team has to do well.
The first is to see clearly. A business cannot run on gut feel. You need a small set of numbers that tell you the true health of the company each week, without interpretation or politics. EOS calls this the Scorecard.
The second is to be disciplined. Every quarter, the leadership team sets three to seven priorities that must get done. These are called Rocks, borrowed from Stephen Covey's metaphor of putting the big things in the jar before the small things. If you do not name the Rocks explicitly, the gravel fills the jar and the big things never happen.
The third is to be healthy. A team that cannot have honest conversations, resolve conflict, and hold each other accountable will fail regardless of how good the strategy is. EOS builds structure for those conversations into every meeting.
Together these three activities, supported by the six key components and the Level 10 Meeting format, make up the EOS operating system.
The EOS model
The EOS Model is a visual representation of the six components every business must master. Wickman uses it as a diagnostic and as a roadmap. A company that scores itself honestly across the six components will know exactly where to focus first.
The model sits inside a larger framework that Wickman calls the Entrepreneurial Operating System. The model is not a hierarchy or a process flow. It is more like a periodic table of what a business needs. You do not move through it sequentially. You work on all six at once, at different depths, as the business grows.
The six key components are where most of the implementation work lives.
Six key components
Wickman names six key components in the EOS Model. Every business running EOS is working to strengthen all six.
Vision. The leadership team gets on the same page about where the company is going and how it plans to get there. This is captured in a document called the Vision/Traction Organizer, or VTO. The VTO has a specific structure: core values, core focus, ten-year target, marketing strategy, three-year picture, one-year plan, Rocks, and issues. If you have read Built to Last or Good to Great, the Vision component covers similar ground but pushes toward a concrete, usable document rather than a framing exercise.
People. You need the right people in the right seats. Wickman defines "right people" as those who share your core values, and "right seats" as those who Get it, Want it, and have the Capacity to do it. He calls this the GWC filter. The Accountability Chart is the tool EOS uses to define who owns what at the leadership level. It is not the same as an org chart. An Accountability Chart defines seats and the primary roles and responsibilities of each seat, with one name per seat at the top.
Data. Every seat on the Accountability Chart produces a number. The leadership Scorecard tracks five to fifteen numbers each week, one per seat, with a goal for each. When a number misses for two consecutive weeks, it becomes an issue to solve rather than a number to hope recovers on its own. The Scorecard is the single tool that makes the most immediate difference for most companies that implement it.
Issues. Every company has a list of things that are not working. EOS calls this the Issues List and gives the leadership team a process for working through it called IDS: Identify, Discuss, Solve. The goal is not to identify all issues, which is endless, but to resolve the most important ones permanently so they do not come back.
Process. The core processes of the business need to be documented and followed by everyone. Wickman recommends identifying six to ten core processes, documenting them at a high level (not a fifty-page manual, but enough that a new person can follow the steps), and then making sure everyone actually uses them.
Traction. This is the execution discipline that makes the other five components real. It has two parts: Rocks (the quarterly priorities) and the Level 10 Meeting. The Level 10 Meeting is a weekly ninety-minute leadership meeting with a fixed agenda. It runs the same way every week: check-in, Scorecard review, Rock review, customer and employee headlines, the to-do list from last week, and then the Issues List. The name comes from Wickman's goal for the meeting: a ten out of ten, every time, because the discipline is tight enough that the meeting produces real decisions.
How this applies if you run an AI-augmented team
Most teams reading Traction today are not running pure human organizations. They have a mix of human seats and AI agents doing real work. The EOS framework handles this better than most people expect, because EOS is seat-based, not person-based.
An AI agent can hold a seat on the Accountability Chart the same way a human does. The seat has a name, a set of primary responsibilities, and a number on the Scorecard. At Sneeze It, this is exactly how we run it. Radar, our chief-of-staff agent, has a seat and produces a number each week. Tally, our scorecard agent, owns the KPI-push function and has measurable output. Dash, our analytics agent, produces a weekly number that sits on our Scorecard next to Bogdan's number and Janine's number.
The discipline is identical. When a seat's number misses, the conversation in the Level 10 Meeting is the same: what is the gap, what is the cause, what is the fix. The fix lands on whoever manages that seat. Whether the seat is human or agent, the accountability structure holds.
This is the part the Traction book does not cover, because it was written before AI agents were a practical option. But the framework is flexible enough to absorb it cleanly. The six key components still apply. The Level 10 Meeting still applies. The Rocks process still applies. You just have more seats available to fill, and some of those seats never sleep.
If you are implementing EOS for the first time and you already run agents, I would suggest reading the seat-definition post in this series alongside Traction. The two documents answer different questions and work together. And if you are already running EOS and wondering where agents fit, the unified scorecard post is the specific answer to that question.
Frequently asked questions
What is the Traction book about? Traction, written by Gino Wickman, introduces EOS, the Entrepreneurial Operating System, a complete operating framework for small and mid-sized businesses. It covers six key components (Vision, People, Data, Issues, Process, and Traction) and gives teams specific tools including the Scorecard, the Accountability Chart, the VTO, and the Level 10 Meeting.
What are the six key components of EOS from Traction? The six key components of the EOS Model are Vision, People, Data, Issues, Process, and Traction. Each component has specific tools associated with it. Traction (the component) covers Rocks and the Level 10 Meeting. Data covers the Scorecard. People covers the Accountability Chart and the GWC filter.
What is a Level 10 Meeting in EOS? The Level 10 Meeting is a weekly ninety-minute leadership meeting format from EOS, the Entrepreneurial Operating System. It follows a fixed agenda every week: check-in, Scorecard review, Rock review, headlines, to-do review, and the Issues List. The name reflects the goal of running every meeting at a ten out of ten through consistent discipline.
What are Rocks in the Traction book? Rocks are the three to seven most important priorities a leadership team commits to completing in a single quarter. They are named after Stephen Covey's rocks-in-a-jar metaphor. EOS uses Rocks to ensure the highest-priority work gets scheduled and completed before day-to-day work fills all available time.
Is OTP an EOS product? No. OTP is not affiliated with EOS Worldwide and is not an official EOS product. OTP is software that helps teams run their operating system, whether EOS-style or otherwise, with both humans and AI agents on the same Accountability Chart, Scorecard, and weekly meeting. It works alongside EOS and Traction as a modern execution layer, not a replacement for the framework.
Run your operating system in OTP
OTP is a chart where humans and agents share scorecards, Rocks, and weekly meetings in one place. Whether you are running EOS from the Traction book or building your own system, OTP gives every seat, human or agent, a number to own and a place on the same chart.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me the Accountability Chart and Scorecard for my organization so I can see which seats have numbers and which do not."