{"slug":"traction-eos","title":"traction-eos","summary":"Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"Entrepreneurial Operating System\", \"V/TO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"my company feels chao","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-06T18:12:40.314638Z","repo":{"url":"https://github.com/wondelai/skills","stars":2263,"forks":230,"license":"MIT","updatedAt":"2026-09-10T21:48:01Z"},"bodyHtml":"
\n

name: traction-eos\ndescription: 'Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"Entrepreneurial Operating System\", \"V/TO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"my company feels chaotic\", \"we keep having the same problems\", or \"get the whole team aligned\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.'\nlicense: MIT\nmetadata:\nauthor: wondelai\nversion: \"1.4.1\"

\n

Entrepreneurial Operating System (EOS)

\n

A complete system for running a business with six key components. Designed for entrepreneurial companies ($2M-$50M revenue, 10-250 employees) that want to align vision and execution.

\n

Core Principle

\n

Most businesses suffer from the same core issues: people, vision, traction. Great vision without traction is hallucination; traction without vision is aimless. EOS connects the two through a practical weekly operating rhythm that strengthens the Six Key Components of any organization.

\n

Scoring

\n

Goal: 10/10. Score the business by how many of the six Quick Diagnostic rows pass (each component is either in place or not), mapped to the bands below. Bands: 9-10 = all six diagnostic rows pass and rocks consistently hit 80%+ completion; 7-8 = five rows pass, one component weak; 5-6 = three to four rows pass; 3-4 = one to two rows pass; <=2 = no operating rhythm in place. Always state the current score, the failing diagnostic rows, and the next action for each.

\n

The Six Key Components

\n
Vision → People → Data → Issues → Process → Traction\n
\n

1. Vision Component

\n

Question: Does everyone in the organization know where you're going and how you plan to get there?

\n

Tool: Vision/Traction Organizer (V/TO) — answers eight questions on two pages:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
QuestionWhat It DefinesExample
Core Values3-7 non-negotiable beliefs\"Own it\", \"Do the right thing\", \"Grow or die\"
Core FocusPurpose/cause/passion + niche\"Simplify small business\" + \"Cloud accounting\"
10-Year TargetBig, hairy, audacious goal\"$100M revenue\" or \"10,000 customers\"
Marketing StrategyTarget market, 3 uniques, proven process, guaranteeWho you serve, why you're different
3-Year PictureWhat the company looks like in 3 yearsRevenue, profit, headcount, key metrics
1-Year PlanRevenue, profit, measurables, goalsSpecific targets for this year
Quarterly Rocks3-7 priorities for this quarterMost important things in 90 days
Issues ListAll unresolved obstaclesProblems, ideas, opportunities
\n

Process: Leadership completes the V/TO together (2-day off-site), shares it with the entire organization, reviews quarterly, updates annually.

\n

Key insight: If the leadership team can't agree on the V/TO, you have a bigger problem — alignment comes first.

\n

See references/vto.md when filling in the V/TO — the eight-question template and the off-site exercise sequence.

\n

2. People Component

\n

Question: Do you have the right people in the right seats?

\n

Tool: Accountability Chart — not an org chart; it defines the structure and who owns what.

\n
Visionary ←→ Integrator\n              ├── Sales/Marketing\n              ├── Operations\n              └── Finance\n
\n\n

Tool: People Analyzer — evaluate every person on two dimensions:

\n
    \n
  1. Right Person (core values fit): Rate +, +/-, or - on each core value. Must be \"+\" on all; one \"+/-\" is a conversation; any \"-\" means wrong person.
    2. \n
  2. Right Seat (GWC): Gets it (understands the role), Wants it (genuinely), Capacity (mental, physical, emotional). Must be \"yes\" on all three.
    3. \n
\n

People decisions:

\n\n

See references/people.md when building the accountability chart or running People Analyzer — templates plus GWC scoring guidance.

\n

3. Data Component

\n

Question: Are you managing based on objective data, or subjective opinions?

\n

Tool: Scorecard — a weekly report card of 5-15 numbers that tell you how the business is doing. Weekly data spots problems 2-4 weeks earlier than monthly and replaces gut-feel management with accountability.

\n

Scorecard rules:

\n\n

Example:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
MetricOwnerGoalW1W2W3W4
RevenueSales Lead$50K/wk✓✓✗✓
New LeadsMarketing100/wk✓✗✓✓
Cash BalanceFinance>$200K✓✓✓✓
\n

Metric selection: If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?

\n

See references/data.md when building the scorecard — templates plus how to pick leading-indicator metrics.

\n

4. Issues Component

\n

Question: Are you identifying, discussing, and solving issues quickly?

\n

Tool: Issues Solving Track (IDS) — Identify → Discuss → Solve:

\n
    \n
  1. Identify: Ask \"Why?\" until you reach the root cause (not the symptom); state the issue in one sentence
    2. \n
  2. Discuss: Everyone gets input (not equal time); stop tangents; one issue at a time, time-boxed 5-15 minutes
    3. \n
  3. Solve: Make the decision, assign action items (who + what + when), move on
    4. \n
\n

Three types of issues:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeExamplesAction
ProblemsCustomer churn, team conflict, outageIDS → solve
IdeasNew feature, process change, opportunityIDS → decide (yes/no/later)
ObstaclesBlocked rock, resource constraintIDS → remove or escalate
\n

Issues list rules: Anyone can add issues; prioritize most important first; unsolved issues carry forward — not everything gets solved each meeting.

\n

Common IDS failures: discussing symptoms instead of root cause, rehashing the same issue weekly, ending without clear action items.

\n

See references/issues.md when facilitating IDS — a Five Whys worked example and tangent-control tactics.

\n

5. Process Component

\n

Question: Have you documented and consistently followed your core processes?

\n

Tool: Core Process Documentation — the 20/80 rule: document 20% of your processes to get 80% consistency.

\n

Core processes to identify: HR (hiring, onboarding, reviews), sales (lead → close), operations (delivery, fulfillment), customer service (support → resolution), finance (invoicing, collections).

\n

Documentation format: Name the process, list 5-20 major steps with just enough detail (not a 50-page manual), make it visual where possible.

\n

Example: Sales Process \"The Closer\"

\n
    \n
  1. Qualify lead (BANT: Budget, Authority, Need, Timeline)
    2. \n
  2. Discovery call (30 min, question guide)
    3. \n
  3. Demo (customized to their pain points)
    4. \n
  4. Proposal (within 24 hours)
    5. \n
  5. Follow up (3 touches in 7 days)
    6. \n
  6. Close or disqualify
    7. \n
\n

Followed By All (FBA): Document it, train on it, measure compliance, update quarterly.

\n

See references/process.md when documenting a core process — full templates and a worked HR/sales/ops example.

\n

6. Traction Component

\n

Question: Are you executing on your vision every day?

\n

Rocks (Quarterly Priorities)

\n

The 3-7 most important things to accomplish in the next 90 days. Ninety days is long enough to achieve something meaningful, short enough to maintain urgency.

\n

Rock-setting process:

\n
    \n
  1. Review the V/TO (vision, 3-year, 1-year)
    2. \n
  2. Brainstorm what must get done this quarter to stay on track
    3. \n
  3. Narrow to 3-7 company rocks, one owner each
    4. \n
  4. Each leadership member also sets 3-7 individual rocks
    5. \n
  5. Share with the organization and track weekly
    6. \n
\n

SMART rocks: Specific (\"Launch new pricing page\", not \"improve pricing\"), Measurable (clear completion criteria), Achievable in 90 days, Realistic given resources, Time-bound (due end of quarter).

\n

Rock scoring: Done = checked off (no partial credit); not done = carried forward or dropped. Target 80%+ completion. Beware rocks that are just \"business as usual\" — they don't move the needle.

\n

See references/rocks.md when setting quarterly rocks — the binary done-test, the nine-row mistakes table, and a mid-quarter check-in.

\n

Level 10 Meeting (Weekly Leadership Meeting)

\n

The most important meeting in EOS. Every week, same day, same time, same agenda — 90 minutes, never longer.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TimeSectionPurpose
5 minSegueGood news, personal and professional
5 minScorecardReview weekly numbers
5 minRock ReviewOn track / off track per rock
5 minHeadlinesCustomer/employee quick updates
5 minTo-Do ListLast week's to-dos: done or not done
60 minIDSIdentify, Discuss, Solve issues
5 minConcludeRecap to-dos, rate meeting 1-10
\n

Rules:

\n\n

See references/level-10.md when running or fixing a Level 10 — facilitation script and how to interpret the meeting rating.

\n

EOS Implementation Timeline

\n

Typical rollout: 2 years to full implementation.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PhaseTimelineFocus
Focus DayDay 1 (8 hours)Accountability chart, rocks, scorecard, Level 10
Vision Building Day 1Month 1V/TO: core values, core focus, 10-year target
Vision Building Day 2Month 2V/TO: marketing strategy, 3-year, 1-year, rocks
Quarterly SessionsEvery 90 daysReview rocks, set new rocks, IDS major issues
Annual PlanningYearlyFull V/TO review, 1-year plan, Q1 rocks
\n

Self-implementation (read the book, follow the tools — free, slower) vs. EOS Implementer (certified facilitator — faster, expensive).

\n

See references/implementation.md when planning the rollout — phase-by-phase sequencing and the self-vs-Implementer decision. For examples of how real companies sequenced it, see references/case-studies.md.

\n

Organizational Checkup

\n

Rate the company 1-5 on each statement:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ComponentStatementScore (1-5)
VisionLeadership team agrees on where we're going and how to get there
PeopleWe have the right people in the right seats
DataWe manage from a weekly scorecard of 5-15 numbers
IssuesWe solve issues quickly and permanently
ProcessCore processes are documented and followed by all
TractionWe set and achieve 90-day priorities (rocks)
\n

Scoring: 25-30 strong (fine-tune) | 20-24 good (close gaps) | 15-19 average (significant work) | below 15 weak (consider an EOS Implementer).

\n

Common Mistakes

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
MistakeWhy It FailsFix
Skipping Level 10sWeekly rhythm lost, issues pile upProtect the meeting, never cancel
No scorecardManaging by gut, constant surprisesChoose 5-15 weekly numbers
Wrong people keptDrags the entire team downPeople Analyzer, make the tough calls
V/TO not sharedTeam doesn't know the visionShare with the entire company
\n

For rock-specific mistakes (too many, too vague, business-as-usual, mid-quarter changes), see references/rocks.md — full nine-row table with fixes.

\n

Quick Diagnostic

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
QuestionIf NoAction
Does leadership agree on vision?MisalignmentComplete the V/TO together
Right people in right seats?Performance issuesPeople Analyzer on all seats
Managing from data weekly?Reactive managementBuild a weekly scorecard
Issues solved permanently?Same problems repeatIDS in Level 10s
Core processes documented?InconsistencyDocument the top 5 processes
90-day priorities set and tracked?No tractionSet quarterly rocks
\n

Further Reading

\n

For the complete system:

\n\n

About the Author

\n

Gino Wickman is the creator of EOS and founder of EOS Worldwide, a community of certified Implementers. Traction has sold over 2 million copies, and EOS is used by more than 250,000 companies worldwide. His work focuses on the practical tools entrepreneurial leadership teams need to get real traction.

\n","files":[{"path":"references/case-studies.md","sizeBytes":18493,"isText":true},{"path":"references/data.md","sizeBytes":12783,"isText":true},{"path":"references/implementation.md","sizeBytes":15501,"isText":true},{"path":"references/issues.md","sizeBytes":14137,"isText":true},{"path":"references/level-10.md","sizeBytes":13552,"isText":true},{"path":"references/people.md","sizeBytes":13330,"isText":true},{"path":"references/process.md","sizeBytes":13666,"isText":true},{"path":"references/rocks.md","sizeBytes":12971,"isText":true},{"path":"references/vto.md","sizeBytes":14569,"isText":true},{"path":"SKILL.md","sizeBytes":14259,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-06T18:13:19.813307Z","sha256":"AEB3137BF9A1D1DF93B10A79C2F1DC44500893E893F937AE0E3D826DEF4027F1","sizeBytes":58788},"review":null,"source":{"repositoryUrl":"https://github.com/wondelai/skills","path":"traction-eos","license":"MIT","commit":"c172996495bed0fcd26896a9416b2093fd7073f0","subtreeSha":"F9F5E862DC3F589487E2C02F26BCA72B1C3F547A0531216BAF9DFB474A8794E8","lastSyncedAt":"2026-09-25T23:12:05.357068Z"},"reviewedAt":"2026-09-06T18:14:43.245267Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/wondelai/skills/tree/main/traction-eos"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wondelai-skills@llmmart"},{"target":"git","command":"git clone https://github.com/wondelai/skills.git"}]}