traction-eos
The traction-eos skill implements the Entrepreneurial Operating System (EOS) framework to help growing companies align their vision with execution and day-to-day operations. It should be used when companies need structured meeting formats, goal-setting methodologies, accountability frameworks, or solutions for recurring organizational problems, and covers six interconnected components: Vision, People, Data, Issues, Process, and Traction.
git clone --depth 1 https://github.com/wondelai/skills /tmp/traction-eos && cp -r /tmp/traction-eos/traction-eos ~/.claude/skills/traction-eosSKILL.md
# Entrepreneurial Operating System (EOS)
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.
## Core Principle
**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.
## Scoring
**Goal: 10/10.** Rate any business 0-10 on EOS component strength: a 10/10 means all six components are strong, meetings are productive, and quarterly rocks are consistently achieved. Always state the current score and the improvements needed to reach 10/10.
## The Six Key Components
```
Vision → People → Data → Issues → Process → Traction
```
Every business is built on these six components. EOS strengthens all six.
### 1. Vision Component
**Question:** Does everyone in the organization know where you're going and how you plan to get there?
**Tool: Vision/Traction Organizer (V/TO)** — answers eight questions on two pages:
| Question | What It Defines | Example |
|----------|----------------|---------|
| **Core Values** | 3-7 non-negotiable beliefs | "Own it", "Do the right thing", "Grow or die" |
| **Core Focus** | Purpose/cause/passion + niche | "Simplify small business" + "Cloud accounting" |
| **10-Year Target** | Big, hairy, audacious goal | "$100M revenue" or "10,000 customers" |
| **Marketing Strategy** | Target market, 3 uniques, proven process, guarantee | Who you serve, why you're different |
| **3-Year Picture** | What the company looks like in 3 years | Revenue, profit, headcount, key metrics |
| **1-Year Plan** | Revenue, profit, measurables, goals | Specific targets for this year |
| **Quarterly Rocks** | 3-7 priorities for this quarter | Most important things in 90 days |
| **Issues List** | All unresolved obstacles | Problems, ideas, opportunities |
**Process:** Leadership completes the V/TO together (2-day off-site), shares it with the entire organization, reviews quarterly, updates annually.
**Key insight:** If the leadership team can't agree on the V/TO, you have a bigger problem — alignment comes first.
See: [references/vto.md](references/vto.md) for V/TO templates and exercises.
### 2. People Component
**Question:** Do you have the right people in the right seats?
**Tool: Accountability Chart** — not an org chart; it defines the structure and who owns what.
```
Visionary ←→ Integrator
├── Sales/Marketing
├── Operations
└── Finance
```
- **Visionary:** Big ideas, culture, key relationships, creative problem solving
- **Integrator:** Runs the business day-to-day, manages the team, executes the vision
- **Rule:** One person per seat — shared accountability is no accountability
**Tool: People Analyzer** — evaluate every person on two dimensions:
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. **Right Seat (GWC):** **G**ets it (understands the role), **W**ants it (genuinely), **C**apacity (mental, physical, emotional). Must be "yes" on all three.
**People decisions:**
- Right person, right seat → keep and invest in
- Right person, wrong seat → move to the right seat
- Wrong person, right seat → coach or exit (hardest call)
- Wrong person, wrong seat → exit immediately
See: [references/people.md](references/people.md) for accountability chart and People Analyzer templates.
### 3. Data Component
**Question:** Are you managing based on objective data, or subjective opinions?
**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.
**Scorecard rules:**
- Activity-based metrics (leading indicators), not results (lagging)
- Weekly numbers — monthly is too slow to react
- Every number has an owner and a goal
- Red/green: on track or off track
**Example:**
| Metric | Owner | Goal | W1 | W2 | W3 | W4 |
|--------|-------|------|----|----|----|----|
| Revenue | Sales Lead | $50K/wk | ✓ | ✓ | ✗ | ✓ |
| New Leads | Marketing | 100/wk | ✓ | ✗ | ✓ | ✓ |
| Cash Balance | Finance | >$200K | ✓ | ✓ | ✓ | ✓ |
**Metric selection:** If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?
See: [references/data.md](references/data.md) for scorecard templates and metric selection.
### 4. Issues Component
**Question:** Are you identifying, discussing, and solving issues quickly?
**Tool: Issues Solving Track (IDS)** — **I**dentify → **D**iscuss → **S**olve:
1. **Identify:** Ask "Why?" until you reach the root cause (not the symptom); state the issue in one sentence
2. **Discuss:** Everyone gets input (not equal time); stop tangents; one issue at a time, time-boxed 5-15 minutes
3. **Solve:** Make the decision, assign action items (who + what + when), move on
**Three types of issues:**
| Type | Examples | Action |
|------|----------|--------|
| **Problems** | Customer churn, team conflict, outage | IDS → solve |
| **Ideas** | New feature, process change, opportunity | IDS → decide (yes/no/later) |
| **Obstacles** | Blocked rock, resource constraint | IDS → remove or escalate |
**Issues list rules:** Anyone can add issues; prioritize most important first; unsolved issues carry forward — not everything gets solved each meeting.
**Common IDS failures:** discussing symptoms instead of root cause, rehashing the same issue weekly, ending without clear action items.
See: [references/issues.md](references/issues.md) for IDS facilitation guides.
### 5. Process Component
**Question:** Have you documented and consistently followed your core processes?
**Tool: Core Process Documentation** —Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "the project keeps growing", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, fighting feature creep, running a small team, avoiding long-term roadmaps, or killing unnecessary meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "uncontested market", "stop competing on price", "everyone is undercutting us", "the market is too crowded", or "how do we stand out". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved or non-customers, or escaping a brutal price war. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", "business logic is tangled with the framework", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", "unit test quality", "my code is hard to read", "this function is a mess", "clean up this code", or "hard to maintain". Also trigger when reviewing pull requests for readability, untangling messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.
Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", "organic growth", "how do I get people to share this", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", "conversion funnel", "increase signups", "people add to cart but dont buy", or "improve conversions". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", "cant get mainstream customers", or "our go-to-market plan". Also trigger when a startup has early traction but cant grow beyond initial users, or when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.