Traction Summary & Review: Get a Grip on Your Business

Traction in one minute

Most businesses don’t have a strategy problem — they have a discipline problem. Gino Wickman spent years coaching entrepreneurial companies and noticed the same six areas breaking down again and again: an unclear vision, the wrong people in the wrong seats, no reliable data, unresolved issues piling up, inconsistent processes, and a lack of follow-through. His answer is the Entrepreneurial Operating System (EOS) — a complete, practical framework built around six components that, strengthened in order, turn a founder’s vision into something the whole team can actually execute. Traction isn’t a collection of leadership philosophy; it’s closer to an installation manual, with named tools (the V/TO, the Accountability Chart, Rocks, the Scorecard, IDS, the Level 10 Meeting) that a leadership team can start using in its very next meeting.

Key takeaways

1. Six components, strengthened in order: Vision, People, Data, Issues, Process, and Traction — weakness in any one caps how far the others can take you.
2. Vision means everyone can repeat it: If your leadership team can’t recite your core values, target market, and 10-year target the same way, you don’t have a vision — you have an idea in your head.
3. Right people, right seats: “Right people” fit your culture (measured by core values); “right seat” means they pass the GWC test — they Get it, Want it, and have the Capacity to do it.
4. The Accountability Chart beats the org chart: Define the seats and outcomes a healthy business needs first, then decide which people fill them — not the reverse.
5. Rocks are your 90-day translation of the vision: 3 to 7 priorities per person, per quarter, each with one owner — long enough to matter, short enough to stay urgent.
6. The Scorecard replaces gut feel with numbers: 5 to 15 weekly metrics give a leadership team an early warning system instead of a monthly surprise.
7. IDS is where issues actually die: Identify, Discuss, Solve — a disciplined way to stop the same problem from resurfacing meeting after meeting.
8. The Level 10 Meeting is the heartbeat: One structured 90-minute weekly meeting, same agenda every time, is what makes every other tool stick.
9. Traction is the proof, not the plan: Vision and tools mean nothing without the discipline to execute — traction is what you get when the other five components hold.
10. This is a system, not a single tactic: Wickman is explicit that picking one tool (say, just the Scorecard) without the rest gets partial results — EOS compounds when the components run together.

What is Traction about?

Traction presents the Entrepreneurial Operating System (EOS), a complete framework of six components — Vision, People, Data, Issues, Process, and Traction — that entrepreneurial leadership teams strengthen in order to turn a founder’s vision into a business that executes consistently, instead of depending on the founder to hold everything together personally.

About the author

Gino Wickman started his first business at 21, and at 25 took over his family’s struggling company, which was deeply in debt. After turning it around over seven years and successfully selling it, he distilled what he’d learned into the Entrepreneurial Operating System — a practical method for helping companies clarify their vision and execute on it. He went on to cofound EOS Worldwide, now one of the largest business-coaching organizations of its kind, and has authored or co-authored eight books, including Get a Grip, Rocket Fuel, and The Entrepreneurial Leap. Traction, first published in 2007 and expanded in 2012, has sold more than 2 million copies and become the standard reference for thousands of companies running on EOS. Explore all Gino Wickman book summaries →

Key concepts at a glance

The Six Key Components

Wickman’s core claim is that every business, regardless of industry, has the same six areas that need strengthening: Vision (does everyone see and agree on where you’re going), People (do you have the right people in the right seats), Data (do you manage with a handful of numbers instead of gut feel), Issues (do problems actually get solved, or just discussed), Process (are your core processes documented and followed the same way by everyone), and Traction (does the team execute with discipline and accountability). He argues these components should be strengthened roughly in that order, because weakness upstream — a fuzzy vision, for instance — makes it much harder to fix the components that depend on it.

The Vision component starts with the V/TO (Vision/Traction Organizer), a two-page document intentionally kept simple: page one captures the vision (core values, core focus, 10-year target, marketing strategy, 3-year picture), page two turns it into a 1-year plan and quarterly Rocks. Wickman is blunt that most leadership teams think they have a shared vision until they try to write it down individually and compare notes — the gaps that surface are usually the real reason strategy conversations go in circles.

Right People, Right Seats

Once vision is clear, Wickman turns to People — and specifically to a distinction he insists most companies get wrong: “right people” and “right seat” are two separate questions. A right person fits your culture, measured against a short list of core values you’ve actually written down and use in hiring and firing decisions. A right seat is a role someone passes the GWC test for: do they Get it (understand what the role really requires), Want it (genuinely desire the responsibility, not just the title or paycheck), and have the Capacity to do it (the time, skill, and mental bandwidth). A great culture fit in the wrong seat is still a problem — and so is a highly skilled person who is a poor culture fit.

To make ownership unambiguous, Wickman recommends building an Accountability Chart before deciding who goes where — the opposite order of a traditional org chart. You first define the functions and outcomes a healthy business of your size needs (sales, marketing, operations, finance), then decide which real people should occupy those seats. This flips a common failure mode where a chart gets built around the people you already have, quietly preserving unclear ownership and duplicated work.

Rocks, the Scorecard, and the V/TO in Practice

With vision and people in place, Wickman moves to Data and the mechanics of execution. Rocks are the 3 to 7 most important priorities a person or team commits to finishing in the next 90 days — short enough to stay urgent, long enough to actually matter, and each with exactly one owner so there’s no ambiguity about who’s accountable. Alongside Rocks sits the Scorecard: 5 to 15 leading numbers reviewed every single week, chosen specifically because they predict problems before they show up in a monthly P&L. Together, the V/TO, Rocks, and Scorecard form a chain from 10-year vision down to this week’s numbers — each tool translating the one above it into something more concrete and closer to today.

Wickman is careful to note that a Scorecard is not the same as a dashboard full of every metric you can measure — the discipline is picking the handful of numbers that actually predict trouble, and reviewing them weekly without fail, not the sophistication of the reporting. Many teams start with a Scorecard that’s too broad, then prune it down after a few weeks once they see which numbers actually change the conversation and which ones nobody ever looks at.

The Level 10 Meeting and IDS

Every tool in EOS ultimately routes through one weekly ritual: the Level 10 Meeting, a fixed 90-minute agenda that Wickman insists should never change once adopted. It runs Segue (a quick personal and business check-in), Scorecard review, Rock review, customer and employee headlines, a to-do list review — and then 60 of the 90 minutes on IDS: Identify, Discuss, Solve. IDS is deliberately the largest block, because most leadership meetings fail not from lack of information but from spending all their time reporting status and none of it actually resolving anything.

In an IDS conversation, the team first identifies the real, root issue (not just its symptom), then discusses it openly until everyone with something relevant to say has spoken, then commits to a solution with a named owner and a deadline — closing the loop instead of leaving it to resurface next week. Wickman argues this single habit, run consistently, is what separates companies that feel perpetually busy from companies that actually get unstuck. Teams new to IDS often find the hardest part isn’t solving issues — it’s resisting the urge to solve every issue outside the meeting instead of saving it for the dedicated block.

Who is Traction best for — and who should read something else first?

Traction is best for founders and leadership teams of small-to-midsize businesses, roughly 10 to 250 employees, who feel like every decision routes through them personally and want a complete operating system rather than a single technique. It’s especially valuable for the classic “Visionary” founder paired with an “Integrator” operator — EOS gives that pairing a shared vocabulary and a weekly rhythm instead of ad hoc check-ins. It’s less suited to solo founders with no team yet, or to leaders in large enterprises where EOS’s assumptions about a single visionary and integrator don’t map cleanly onto a much larger org chart.

If your core problem is really about team trust and conflict rather than structure, start with The Five Dysfunctions of a Team instead. If you specifically need a hiring framework rather than a full operating system, The Ideal Team Player is a more targeted read.

Questions to reflect on

• If you asked each member of your leadership team to write down your company’s vision separately, how much would their answers actually agree?
• Is there anyone on your team who is a great culture fit but clearly failing the GWC test in their current seat?
• What are the 3-7 things that absolutely must get done in your business in the next 90 days — and does each one have exactly one owner?
• What 5-15 numbers would give you the earliest possible warning that something is going wrong?
• What issue has come up in your team’s last three meetings without ever actually getting solved?

How to apply Traction (7-day plan)

1. Day 1: Draft your company’s core values and core focus in one page. Don’t overthink it — write what’s actually true today.
2. Day 2: Write your 10-year target and 3-year picture in a few sentences each. Share it with one other leader and compare notes.
3. Day 3: Build a first-draft Accountability Chart: list the functions and outcomes your business needs, before assigning any names.
4. Day 4: Run a GWC check on your own seat and one direct report’s seat. Be honest about gaps.
5. Day 5: Set your first 3-7 Rocks for the next 90 days, each with a single owner and a clear finish line.
6. Day 6: Pick 5-7 numbers for a first-draft Scorecard — things you could realistically review every week.
7. Day 7: Schedule a 90-minute Level 10 Meeting for next week using the fixed agenda, and list the top 3 issues you’ll bring to IDS.

Frequently asked questions

Related summaries

If Traction resonated, continue with The Five Dysfunctions of a Team, Measure What Matters, The Ideal Team Player, and Multipliers. For more, browse our full best leadership books list.