EOS
Entrepreneurial Operating System (Traction)
EOS, the Entrepreneurial Operating System, is a complete way for a small or midsize company's leadership team to run the business. It asks the team to agree on six things: the vision, the right people in the right seats, a few weekly numbers, an open list of issues, the core processes, and three to seven priorities for the next 90 days, called Rocks. A weekly 90-minute leadership meeting keeps it all moving.
TL;DR
- What it is
- A complete way to run a small or midsize company, set out in Gino Wickman's 2007 book Traction. Six parts of the business, a set of simple tools and a fixed meeting rhythm.
- Best for
- Privately held, founder-led companies of about 10 to 250 people whose leaders want one shared way to run the business.
- First cycle
- One or two days to write down the vision and set the first 90-day priorities, then a weekly leadership meeting from the next week.
- You leave with
- Three to seven company priorities for the next 90 days, each owned by one person, and a weekly meeting on the calendar.
EOS is less a goal format and more a full operating system. It covers where the company is going, who does what, which numbers to watch, how problems get solved, how the work gets done, and what must be finished this quarter. The pieces are simple on purpose, so a leadership team can run them without outside help.
The idea is to make the vision concrete and shared, then drive it through a steady weekly and quarterly rhythm rather than an annual burst of planning. The 90-day priorities, called Rocks, are where the plan meets the calendar: each one is owned by one person and is either done or not done at the end of the quarter.
The original EOS, in brief
Created by Gino Wickman and set out in his book "Traction" (2007; revised edition 2011). Owned and taught by EOS Worldwide, which he co-founded in 2008.
EOS, the Entrepreneurial Operating System, comes from Gino Wickman's book Traction: Get a Grip on Your Business. It first appeared in 2007, and BenBella Books published a revised edition in 20111. EOS Worldwide says Wickman created the system in the early 2000s, and that he co-founded EOS Worldwide with Don Tinney in 2008 to teach it2.
The core idea is that a leadership team should run the company on one system, not a patchwork of habits. EOS names six parts of any business to strengthen: Vision, People, Data, Issues, Process and Traction2. Each part has a small tool, such as a short written summary of the vision and plan, a chart of who owns each function, a weekly set of numbers, and a way to solve problems in a meeting23. The same tools are used every week and every quarter, so the system becomes the way the company works.
EOS Worldwide describes two paths. A company can hire a paid EOS implementer, which it says takes about two years and around ten full days of sessions. Or the company can run it alone from the books and free tools24.
Common misreadings
- "EOS is a goal format." It is a whole operating system. The 90-day priorities, called Rocks, are one tool among many, inside the Traction part23.
- "Rocks are just OKRs." A Rock is one larger commitment with one owner, finished or not finished in 90 days35. It has no graded key results. EOS Worldwide advises choosing one framework for quarterly priorities rather than running both5.
- "You need a certified implementer." EOS Worldwide says many companies run it themselves from the books and tools24.
- "The weekly meeting is a status update." In the Level 10 Meeting, 60 of the 90 minutes go to solving issues. The reports at the start take about five minutes each6.
- "It fits any company." EOS Worldwide aims it at privately held companies of roughly 10 to 250 people2.
The EOS template
Vision
Where the company is going and why, written so every leader would say it the same way: values, focus, a long-range target and this year's goals.
People
The functions the business needs, one owner for each, and whether each person shares the values and fits the seat.
Data
A handful of numbers the leadership team looks at every week to see whether the business is on track.
Issues
One open list of problems and ideas, worked through in order of importance until each is solved.
Process
The few core ways the work gets done, written down simply and followed by everyone.
Traction
Three to seven priorities for the next 90 days, each with one owner, and the weekly meeting that checks them.
EOS examples
A 20-person design agency
The two founders make every decision, and projects stall while they are away.
A 150-person manufacturer
Growing fast, with the same problems raised at every leadership meeting.
A 60-person software company
Past product-market fit, but the leadership team pulls in different directions.
When EOS fits, where it struggles, and what it does not answer
Use it when
- The founder is the bottleneck and the leadership team needs one shared way to run the business.
- Meetings run long, the same problems come back every week, and nobody owns the fix.
- Plans get made once a year and then forgotten by spring.
- You want a system you can start from a book, without hiring anyone.
- The company is growing past the size where everyone knows what everyone else is doing.
It struggles when
- Larger or multi-unit companies. EOS is built for one leadership team in a company of about 10 to 250 people2. It says little about aligning many business units or levels.
- Rigidity and cost. In a 2025 study of 12 experienced business leaders, published as a Liberty University dissertation, leaders credited EOS with giving vision and leadership. They also found it inflexible, and costly for smaller companies7.
- Strategy depth. The vision work asks for values, focus and long-range targets. It does not make you study competitors or choose where to compete. A clear vision is not the same as a strategy.
- Mixing systems. EOS Worldwide advises picking one framework for quarterly priorities5. Companies that already run OKRs face a real choice, not an easy blend.
- Leadership time. The weekly meeting takes 90 minutes of the whole leadership team, every week6. Teams that skip it lose most of the benefit.
What it does not answer
- Where to compete and how to win against rivals.
- Which weekly numbers actually predict results. It asks for a handful of numbers, not a method for finding the right ones.
- How to align many teams or sites below the leadership team.
- What is changing in your market.
Pair it with
- Playing to Win Settles where to compete and how to win, which the EOS vision work does not force. Feed its choices into the vision and the Rocks.
- McKinsey 7S When Rocks keep slipping quarter after quarter, 7S helps find the misfit in structure, skills or style behind it.
How to implement EOS
- Decide who will lead it. Run it yourselves from the book, with one leader who owns the process, or hire an outside implementer. Either way, the whole leadership team has to commit to the weekly meeting.
- Write down the vision. Values, what the company does best, a long-range target and this year's goals, in words every leader would repeat the same way.
- Map the functions and give each one owner. Start from the work the business needs, not from the people you have. Then put names in the seats, one per function.
- Set three to seven Rocks for the next 90 days. Each is a finishable project with one owner, done or not done by the end of the quarter. Ongoing work is not a Rock.
- Start the weekly leadership meeting. Same day, same time, same agenda: the weekly numbers, each Rock on or off track, then most of the time on solving the top issues.
- Reset every quarter. Review which Rocks got done and why, clear the issues list, and set the next quarter's Rocks. Once a year, revisit the vision and the one-year goals.
Adopting EOS: the first cycle and the rhythm
First cycle. A leadership team can write down its vision and set its first Rocks in one or two days. EOS Worldwide says the full process with an implementer runs about two years and around ten full days of sessions, covering the first setup days and then quarterly and annual sessions2.
Rhythm. Every week, a 90-minute leadership meeting on the same day and time with the same agenda6. In it, each owner says whether each Rock is on track or off track11. Every 90 days, the team reviews what got done and sets new Rocks11. Once a year, a longer session resets the one-year plan.
How long until it runs itself. Expect several quarters before Rocks are sized well and the weekly meeting spends its time on issues. The two-year span EOS Worldwide gives for the full process is a fair guide to how long the habits take to set2.
What derails it. Too many Rocks. Rocks that are ongoing work, not finishable projects. Skipping the weekly meeting in busy weeks. A founder and an operator who never agree who decides what; EOS Worldwide treats that pairing, the Visionary and the Integrator, as central12. And fatigue with the vocabulary, or with the cost of outside help, in smaller firms7.
How to set EOS at your leadership retreat
The decision the session has to produce: The three to seven company priorities for the next 90 days, each with one owner and a clear finish line, checked against a vision the whole team agrees on.
A half-day outline
- Review last quarter: which priorities got done, which did not, and why (30 minutes).
- Read the vision aloud and fix anything the team no longer believes (45 minutes).
- Everyone lists candidate priorities alone before anyone speaks (15 minutes).
- Break.
- Merge the lists and cut to three to seven company priorities (45 minutes).
- Give each priority one owner and a clear definition of done (20 minutes).
- Work the three biggest issues on the list to a decision (45 minutes).
- Confirm the weekly numbers and book the weekly meeting (15 minutes).
Ask the team beforehand
- What must be true in 90 days for this quarter to count as a success?
- Which problem have we discussed more than twice without solving it?
- Which part of the business has no single owner today?
Who should be in the room
The leadership team, including the founder and whoever runs day-to-day operations. EOS is built around the leadership team; departments set their own priorities after it.
Make a full retreat agenda with the free agenda maker.
Common EOS mistakes
- Too many Rocks. Ten priorities a quarter means none of them gets the attention it needs. Three to seven for the company, fewer for each person.
- Rocks that are ongoing work. "Keep customers happy" never finishes. A Rock is a project that is either done or not done by the end of the quarter.
- Shared ownership. A Rock with two owners has none. Put one name on it, even if a team does the work.
- A weekly meeting that turns into reports. The updates should take minutes. Most of the time belongs to solving the top issues on the list.
- Drawing the chart around the people you have. Map the functions the business needs first, then fill the seats. Otherwise gaps and overlaps stay hidden.
- Adopting the words without the habits. Calling priorities Rocks changes nothing if the weekly meeting is skipped and the quarterly reset never happens.
Does EOS work? The evidence
No independent, peer-reviewed study has tested whether EOS improves company results. A search of academic databases for this page found a few graduate theses and case studies, and no controlled or long-term comparison. EOS Worldwide publishes its own figures on how many companies run EOS2. Those are counts of users, reported by the owner. They are not tests of whether it works.
The closest independent look is small. Michelle Tucker's 2025 PhD dissertation at Liberty University interviewed 12 business leaders with five or more years of experience with EOS, Six Sigma or continuous improvement. It found EOS gave vision and leadership, and was seen as inflexible and costly for smaller companies. It also noted how little academic research on EOS exists7. Twelve interviews can describe experience. They cannot show whether EOS works.
Some of EOS's parts rest on well-tested ideas. Edwin Locke and Gary Latham, reviewing 35 years of research in American Psychologist in 2002, found that specific, hard goals with feedback lead to better performance than vague goals such as "do your best"8. A survey of about 35,000 U.S. manufacturing plants, published in the American Economic Review in 2019, found that structured management practices, such as monitoring, targets and incentives, accounted for more than 20% of the differences in productivity between plants9. A field experiment in Indian textile firms, published in the Quarterly Journal of Economics in 2013, found that adopting basic management practices raised productivity by 17% in the first year10.
None of those studies tested EOS. They support the general idea that clear goals, regular measurement and clear ownership help. Whether the EOS package delivers more than any disciplined version of those habits has not been studied. Read EOS as a practical system with a large user base and no independent proof of results.
EOS compared
| EOS | Scaling Up | OKR | |
|---|---|---|---|
| What it covers | The whole business: vision, people, numbers, issues, process and priorities | The whole business, organized around people, strategy, execution and cash | Goals only: objectives and measurable key results |
| Quarterly priorities | Three to seven Rocks, each done or not done | A few quarterly priorities with owners | A few objectives, each with key results |
| Meeting rhythm | A weekly 90-minute leadership meeting, plus quarterly and annual sessions | Daily, weekly, monthly, quarterly and annual meetings | No fixed rhythm; many teams check in weekly |
| Who runs it | The team itself from the books, or a paid implementer | The team itself, or a paid coach | The team itself; outside help optional |
| Best fit | Founder-led companies of about 10 to 250 people | Growing companies that want more depth on strategy and cash | Teams of any size that want a few measurable goals |
After the retreat: EOS in Throughline
What it holds. The Rocks become priorities, each with one owner, a date and a measure. Owners check in from an email in one click on the rhythm you set, weekly included; a missed check-in counts as off track and their manager is told.
What it doesn’t. Throughline is not EOS software and holds none of the EOS tools: no vision organizer, accountability chart, weekly scorecard or issues list. The weekly leadership meeting happens in your own meeting.
EOS glossary
- Rocks
- The three to seven most important things the company must finish in the next 90 days, each with one owner. Leaders usually carry three to seven; other staff one to three3.
- Level 10 Meeting
- The weekly 90-minute leadership meeting with a fixed agenda. Each person rates it from 1 to 10; the aim is 8 or better6.
- IDS
- Identify, discuss, solve: the way issues are worked in the weekly meeting. Find the real cause, talk it through, agree on a fix6.
- Scorecard
- A handful of weekly numbers that show whether the business is on track3.
- Accountability Chart
- A chart of the functions the business needs and the one person who owns each. Unlike an org chart, it starts from the work, not the people3.
- V/TO
- The Vision/Traction Organizer: EOS's written summary of where the company is going and its plan for the year and the quarter2.
- Visionary and Integrator
- The two top roles EOS describes: the idea person who drives growth, and the operator who runs the business day to day12.
- Issues list
- One open list of problems and ideas, worked through by priority in the weekly meeting.
Free tools that help
EOS: frequently asked questions
- What is EOS?
- The Entrepreneurial Operating System, created by Gino Wickman and set out in his book "Traction". It gives a small or midsize company's leadership team one way to run the business: a shared vision, clear owners, weekly numbers, an issues list, simple processes, and 90-day priorities called Rocks.
- What are the six components of EOS?
- Vision, People, Data, Issues, Process and Traction. In plain words: where you are going, who owns what, which numbers you watch, how you solve problems, how the work gets done, and what you will finish this quarter.
- What are "Rocks" in EOS?
- Rocks are the three to seven most important things the company must finish in the next 90 days. Each has one owner, and each is either done or not done at the end of the quarter. Leaders usually carry a few; other staff one to three.
- What is a Level 10 Meeting?
- The weekly EOS leadership meeting: 90 minutes, same day, same time, same agenda. Short check-ins on the numbers, Rocks and to-dos come first; most of the time goes to solving the top issues. Everyone rates the meeting from 1 to 10 at the end.
- What is the V/TO?
- The Vision/Traction Organizer: EOS's written summary of where the company is going and its plan for the year and the quarter. It is EOS Worldwide's own tool; get it from them rather than from a copy.
- Do you need an EOS Implementer?
- No. EOS Worldwide says many companies run EOS themselves from the books and free tools. A paid implementer leads the sessions and holds the team to the process; EOS Worldwide puts the full process with one at about two years.
- Is EOS better than OKRs?
- They do different jobs. EOS is a whole way of running a company; OKRs are a way of setting goals. EOS Worldwide advises choosing one framework for quarterly priorities rather than running Rocks and OKRs side by side.
- Does EOS work?
- Many companies use it, and EOS Worldwide publishes its own figures on how many. No independent, peer-reviewed study has yet tested whether it improves results. Its core habits, clear goals, weekly measurement and single owners, are backed by broader management research.
Sources
- Gino Wickman, Traction: Get a Grip on Your Business, revised edition, BenBella Books, 2011. First published 2007. benbellabooks.com
- EOS Worldwide, "What is the Entrepreneurial Operating System (EOS)?", eosworldwide.com. eosworldwide.com
- EOS Worldwide, "The Ultimate Guide to Business Operating Systems," eosworldwide.com. eosworldwide.com
- EOS Worldwide, "Two Ways to Implement EOS," eosworldwide.com. eosworldwide.com
- EOS Worldwide, "EOS vs. OKRs," eosworldwide.com. eosworldwide.com
- EOS Worldwide, "Level 10 Meeting," eosworldwide.com. eosworldwide.com
- Michelle Tucker, "Exploring the Deficiencies of Business Improvement Programs: A Qualitative Look Into Continuous Improvement, Six Sigma, EOS, and Developing Hybrid Opportunities," PhD dissertation, Liberty University, 2025. digitalcommons.liberty.edu
- Edwin A. Locke and Gary P. Latham, "Building a practically useful theory of goal setting and task motivation: A 35-year odyssey," American Psychologist 57(9), 2002, pp. 705 to 717. doi.org
- Nicholas Bloom, Erik Brynjolfsson, Lucia Foster, Ron Jarmin, Megha Patnaik, Itay Saporta-Eksten and John Van Reenen, "What Drives Differences in Management Practices?", American Economic Review 109(5), 2019, pp. 1648 to 1683. doi.org
- Nicholas Bloom, Benn Eifert, Aprajit Mahajan, David McKenzie and John Roberts, "Does Management Matter? Evidence from India," Quarterly Journal of Economics 128(1), 2013, pp. 1 to 51. doi.org
- EOS Worldwide, "Leading in a 90-Day World," EOS Worldwide blog. eosworldwide.com
- Don Tinney, "Why Entrepreneurial Companies Need a Visionary and an Integrator," EOS Worldwide blog. eosworldwide.com
- EOS Worldwide, "US Trademarks," EOS Worldwide brand guidelines. branding.eosworldwide.com
EOS was created by Gino Wickman and is owned by EOS Worldwide, LLC; EOS, Entrepreneurial Operating System, Traction, Vision/Traction Organizer, V/TO, Level 10 Meeting, IDS, The Accountability Chart and EOS Implementer are registered trademarks of EOS Worldwide, LLC [13], and Throughline is not affiliated with, licensed by or endorsed by EOS Worldwide. Written by Tom Olajide, Founder. Last reviewed September 24, 2026.