Traction is the single best book a founder of a $2M to $15M company can read. It is a prescriptive playbook for installing a real operating cadence on a team that has never had one. The six-component frame is durable, the toolkit is small enough to remember, and the cadence is the most testable promise in modern management writing. Above $25M the prescriptions start to constrain and the book is silent on capital, multi-BU coordination, and leading indicators.
What the book is
Traction: Get a Grip on Your Business was published in 2007 by Gino Wickman, a Detroit-area entrepreneur who had spent years inside his family's business and operating other small companies. The book introduced the Entrepreneurial Operating System (EOS®) and launched the network of Certified Implementers.
The book is short (about 230 pages) and intentionally repetitive. The repetition is a feature; the audience is operating CEOs who will read 40 percent of it and need the key concepts hammered.
Chapter 1: The EOS® model
Introduces the six components: Vision, People, Data, Issues, Process, Traction. The diagnostic is to score each one 0 to 100 percent and treat anything under 80 as a real weakness. The model is the whole book in one page.
Chapter 2: Vision
The V/TO is introduced here. Eight sections across two pages: core values, core focus, 10-year target, marketing strategy, three-year picture, one-year plan, quarterly Rocks, Issues list. Full walkthrough in our
Chapter 3: People
The Accountability Chart replaces the org chart. The People Analyzer uses the GWC rubric (Get it, Want it, Capacity) plus a values match. The chapter's strongest claim: most companies tolerate the wrong people in the wrong seats for far too long, and the People Analyzer makes the conversation concrete.
Chapter 4: Data
The Scorecard: 5 to 15 weekly numbers, each with one owner and a defined target. The chapter's central insight is that most leadership teams confuse 'a lot of data' with 'a few right numbers reviewed weekly.' Less data, more discipline.
The Scorecard chapter is also the most-aged. The format does not naturally distinguish leading from lagging indicators. See our leading vs lagging indicators guide.
Chapter 5: Issues
The Issues List and the IDS protocol. The book's most underrated contribution. Identify the real issue (not the symptom), Discuss once (everyone speaks before anyone speaks twice), Solve with one owner and one deadline. IDS is the operating verb that makes the Level 10 meeting actually solve things.
Chapter 6: Process
The 20/80 rule applied to documentation: write down the 20 percent of process that produces 80 percent of the result. 6 to 10 core processes, each on one page. The chapter is short because the point is short.
Chapter 7: Traction
The two most-cited tools from the book live here. Rocks are 3 to 7 quarterly priorities per person with a binary done-criterion. The Level 10 weekly meeting is 7 blocks adding up to 90 minutes. This chapter is the most prescriptive in the book and the one Implementers spend the most time installing.
Chapter 8: Putting it all together
The install sequence. Focus Day, Vision Building Day 1, Vision Building Day 2, then quarterlies and annuals on ongoing cadence. The book's argument that the install takes 12 to 24 months is honest and has held up across tens of thousands of company-years of evidence.
Where the book is brilliant
- It is prescriptive. Most management books are descriptive. Traction tells you what to do on Monday morning.
- The toolkit is small. Six components, seven tools. The whole system fits in working memory.
- The cadence is the most testable management claim in print. Run the Level 10 weekly for 12 weeks and you can tell whether it works.
- The IDS protocol changes how leadership teams argue. That alone is worth the book.
- It assumes the reader is an operator, not an academic. The voice is direct.
Where it shows its age
- No serious treatment of capital strategy, debt, or M&A. At $5M this is fine. At $40M it is a gap.
- The Scorecard format does not naturally pair leading and lagging indicators.
- The single-Level-10 assumption breaks above 7 people on the leadership team.
- The Accountability Chart silently assumes a single business unit.
- The Visionary/Integrator split (developed further in Rocket Fuel) is right in spirit but rarely installed with real authority. See the Operational Integrator role.
Verdict
Read Traction if you are running a $2M to $25M company without a real operating cadence. The ROI on the $20 book is hard to beat.
Re-read it every 18 months as a refresher on cadence discipline.
When you cross $25M and the format starts to constrain, do not abandon what you learned. The cadence discipline carries forward. The format gets replaced.
What to migrate to and how: outgrowing EOS® and ASCEND vs EOS®.
Already running Traction? See what comes next.
Take the 10-minute ASCEND assessment to see a per-pillar maturity score and whether the gap in your operating system is execution discipline (where Traction shines) or something further upstream.