# EOS Case Studies: Companies That Got Traction

Implementing EOS transforms companies across every industry. This collection of case studies illustrates how different types of organizations -- from SaaS startups to manufacturing companies -- used the Entrepreneurial Operating System to overcome specific challenges and achieve measurable results. Each case follows a consistent structure and concludes with lessons that apply broadly.


## Table of Contents
1. [Case Study 1: CloudStack Solutions (SaaS Startup)](#case-study-1-cloudstack-solutions-saas-startup)
2. [Case Study 2: Meridian Consulting Group (Professional Services)](#case-study-2-meridian-consulting-group-professional-services)
3. [Case Study 3: Precision Metal Works (Manufacturing)](#case-study-3-precision-metal-works-manufacturing)
4. [Case Study 4: Spark Digital Agency (Marketing Agency)](#case-study-4-spark-digital-agency-marketing-agency)
5. [Case Study 5: Summit Health Partners (Healthcare)](#case-study-5-summit-health-partners-healthcare)
6. [Common Patterns in Successful EOS Implementations](#common-patterns-in-successful-eos-implementations)
7. [Typical Results Timeline](#typical-results-timeline)

---

## Case Study 1: CloudStack Solutions (SaaS Startup)

### Company Profile

- **Industry:** B2B SaaS (project management software)
- **Revenue at start:** $3.2M ARR
- **Employees:** 35
- **Founded:** 4 years prior
- **Leadership team:** CEO (Visionary), COO (Integrator), VP Sales, VP Engineering, VP Marketing

### Starting Challenges

- Revenue growth had stalled at 15% year-over-year after three years of 80%+ growth
- The CEO was involved in every decision, creating a bottleneck
- Engineering and Sales were in constant conflict over roadmap priorities
- No formal meeting rhythm; ad hoc meetings consumed 30+ hours per week across leadership
- Three key engineers quit in six months, citing lack of direction

### EOS Components Implemented

**Quarter 1:** Focus Day established the Accountability Chart. The CEO stepped into the Visionary role and the COO formally became the Integrator. Weekly Level 10 meetings replaced all ad hoc leadership meetings. Five quarterly rocks were set, including hiring a VP of Customer Success.

**Quarter 2:** V/TO completed. Core Values defined: "Ship It," "Customer Obsessed," "Radical Candor." Core Focus: "Make teams productive" + "Project management for mid-market SaaS." A weekly Scorecard with 10 metrics was launched.

**Quarter 3:** People Analyzer run on all 35 employees. Four people were identified as wrong person/wrong seat. Two were moved to better-fitting roles. Two exited. The engineering-sales conflict was IDS'd: root cause was no product prioritization process. A core process ("The Roadmap Engine") was documented.

**Quarter 4:** Department-level Level 10 meetings rolled out. Department scorecards created. Rock completion rate hit 85%.

### Results

| Metric | Before EOS | After 12 Months | After 24 Months |
|--------|-----------|-----------------|-----------------|
| ARR | $3.2M | $4.8M | $7.1M |
| ARR Growth | 15% | 50% | 48% |
| Employee Headcount | 35 | 48 | 65 |
| Employee Turnover | 28% annually | 12% | 8% |
| Rock Completion | N/A | 75% | 88% |
| Level 10 Score | N/A | 7.2 avg | 8.6 avg |
| CEO Weekly Hours in Meetings | 32 | 12 | 8 |

### Timeline

- **Month 0-3:** Foundation (Focus Day, VB1, VB2). Immediate reduction in ad hoc meetings.
- **Month 3-6:** First quarterly session. Scorecard revealing blind spots in customer health metrics.
- **Month 6-12:** People decisions made. Core processes documented. Revenue growth resumed.
- **Month 12-24:** EOS cascaded to all departments. Company operating as a self-managing system.

### Key Lessons

1. The CEO stepping out of day-to-day operations and into the Visionary role unlocked growth that was being bottlenecked by one person.
2. The engineering-sales conflict was not a people problem -- it was a process problem. Documenting the roadmap prioritization process resolved years of tension.
3. The weekly Scorecard caught a customer health decline that would have resulted in major churn if not addressed early.

## Case Study 2: Meridian Consulting Group (Professional Services)

### Company Profile

- **Industry:** Management consulting
- **Revenue at start:** $8.5M
- **Employees:** 52
- **Founded:** 12 years prior
- **Leadership team:** Managing Partner (Visionary), COO (Integrator), 3 Practice Leads, Head of Business Development

### Starting Challenges

- Revenue had plateaued for two years despite adding consultants
- Utilization rates varied wildly (50% to 95%) across practices
- No consistent delivery methodology; quality depended entirely on the individual consultant
- The Managing Partner was the only person who could close large deals
- High-potential consultants kept leaving for competitors

### EOS Components Implemented

**Focus Day:** Accountability Chart revealed that no one owned business development as a full-time function. The Managing Partner had been doing it as a side task. A Head of Business Development seat was created.

**V/TO Sessions:** Core Values: "Client First," "Own Your Craft," "Straight Talk," "Win Together." Marketing Strategy identified the ideal client profile (mid-market companies, $50M-$500M revenue, undergoing operational transformation) and three uniques: industry-specific expertise, fixed-fee engagements, and a proprietary delivery methodology.

**Process Documentation:** Three core processes were documented: "The Engagement Lifecycle" (sales to delivery to follow-up), "The Consulting Method" (the firm's proprietary delivery approach), and "The Talent Pipeline" (recruiting, onboarding, and development).

**Scorecard:** Key metrics included weekly utilization rate, pipeline value, proposals outstanding, consultant satisfaction score, and client NPS.

### Results

| Metric | Before EOS | After 12 Months | After 24 Months |
|--------|-----------|-----------------|-----------------|
| Revenue | $8.5M | $10.2M | $13.8M |
| Utilization Rate | 62% avg | 74% avg | 78% avg |
| Revenue Per Consultant | $212K | $268K | $310K |
| Consultant Turnover | 35% | 18% | 12% |
| Client NPS | 42 | 58 | 67 |
| Rock Completion | N/A | 70% | 82% |
| Level 10 Score | N/A | 6.8 avg | 8.3 avg |

### Key Lessons

1. Documenting the delivery methodology ("The Consulting Method") was the single highest-impact change. It made quality consistent across all consultants and reduced the firm's dependence on individual talent.
2. Utilization rate visibility on the weekly Scorecard changed behavior immediately. Practice leads started managing capacity proactively instead of reactively.
3. Hiring a dedicated Head of Business Development freed the Managing Partner to focus on strategic relationships, which paradoxically increased deal flow.

## Case Study 3: Precision Metal Works (Manufacturing)

### Company Profile

- **Industry:** Custom metal fabrication
- **Revenue at start:** $18M
- **Employees:** 120
- **Founded:** 25 years prior (second-generation family business)
- **Leadership team:** Owner/President (Visionary), General Manager (Integrator), VP Sales, Plant Manager, Controller

### Starting Challenges

- Profit margins had declined from 12% to 5% over five years
- On-time delivery rate was 71%, causing customer complaints and lost contracts
- The shop floor had no documented processes; veteran machinists each had their own methods
- The owner's son had been promoted to Plant Manager but was struggling
- No weekly management meetings; monthly financial reviews were the only rhythm

### EOS Components Implemented

**People Component:** The People Analyzer revealed the owner's son did not have the Capacity for the Plant Manager role. After a difficult but honest conversation, he moved to a Business Development role where he excelled (he Got it, Wanted it, and had Capacity). An experienced Plant Manager was hired externally.

**Process Component:** Five core shop floor processes were documented with the 20/80 rule. Each process was given a branded name and posted at the relevant workstation. Training was conducted over six weeks. Quality defects dropped 40% in the first quarter after documentation.

**Data Component:** A weekly Scorecard was installed tracking on-time delivery %, scrap rate, labor utilization, quoting turnaround time, and weekly revenue. Numbers were displayed on a large screen on the shop floor.

**Traction Component:** Level 10 meetings were introduced for the leadership team and the shop floor supervisors. Quarterly rocks focused on operational improvements: reducing setup times, implementing a preventive maintenance schedule, and standardizing the quoting process.

### Results

| Metric | Before EOS | After 12 Months | After 24 Months |
|--------|-----------|-----------------|-----------------|
| Revenue | $18M | $19.5M | $22M |
| Profit Margin | 5% | 9% | 13% |
| On-Time Delivery | 71% | 88% | 94% |
| Scrap Rate | 8% | 4.5% | 2.8% |
| Customer Complaints/Month | 12 | 5 | 2 |
| Employee Turnover | 40% | 22% | 15% |
| Rock Completion | N/A | 65% | 80% |

### Key Lessons

1. The hardest decision -- moving the owner's son out of the Plant Manager role -- was also the most impactful. Using the People Analyzer made it an objective conversation rather than a personal attack.
2. Making the Scorecard visible on the shop floor created a sense of ownership among floor workers. They started self-correcting before managers even noticed problems.
3. Manufacturing companies often resist EOS because they think it is for "office businesses." Process documentation and weekly scorecards are arguably even more impactful in production environments.

## Case Study 4: Spark Digital Agency (Marketing Agency)

### Company Profile

- **Industry:** Digital marketing agency
- **Revenue at start:** $4.2M
- **Employees:** 28
- **Founded:** 6 years prior
- **Leadership team:** Founder/Creative Director (Visionary), Director of Operations (Integrator), Head of Accounts, Head of Creative, Head of Media

### Starting Challenges

- Revenue was growing but profitability was near zero due to scope creep on client projects
- The founder was involved in every creative decision, limiting the team's output
- Client retention was 65% (industry average is 72%)
- No standardized project delivery process; every project was a "custom" engagement
- The team operated in constant fire-drill mode with no clear priorities

### EOS Components Implemented

**V/TO:** Core Focus defined as "Make brands unforgettable" + "Performance-driven creative for B2B tech companies." This immediately clarified which clients to pursue and which to stop serving. Three clients that did not fit the niche were transitioned out within two quarters.

**Process Component:** The core delivery process ("The Impact Cycle") was documented in 12 steps from brief to launch to performance review. Scope creep was addressed by adding a formal change request step. Every project now followed the same structure.

**Rocks:** First quarter rocks included: define ideal client profile and update all sales materials, document The Impact Cycle, hire a Creative Director to replace the founder in day-to-day creative decisions, and implement project profitability tracking.

**People Component:** The founder struggled to let go of creative control. An honest Visionary/Integrator conversation established boundaries: the founder would set creative direction and handle top-tier client relationships but would not review every deliverable.

### Results

| Metric | Before EOS | After 12 Months | After 24 Months |
|--------|-----------|-----------------|-----------------|
| Revenue | $4.2M | $5.1M | $6.8M |
| Net Profit Margin | 2% | 12% | 18% |
| Client Retention | 65% | 78% | 85% |
| Revenue Per Employee | $150K | $189K | $227K |
| Scope Creep Incidents/Quarter | 15+ | 4 | 1 |
| Rock Completion | N/A | 72% | 85% |
| Founder Hours/Week on Production | 35 | 15 | 5 |

### Key Lessons

1. Narrowing the niche felt counterintuitive ("We're turning away revenue!") but dramatically improved profitability and client results. Specialization commands higher prices and lower delivery costs.
2. Documenting the delivery process eliminated scope creep, which was the primary margin killer.
3. Agencies where the founder cannot delegate creative work will always have a revenue ceiling. The Visionary/Integrator framework gave the founder a path to step back without losing influence.

## Case Study 5: Summit Health Partners (Healthcare)

### Company Profile

- **Industry:** Multi-location physical therapy practice
- **Revenue at start:** $12M
- **Employees:** 85 (across 6 clinics)
- **Founded:** 10 years prior
- **Leadership team:** Founder/CEO (Visionary), Practice Administrator (Integrator), Clinical Director, Marketing Director, Finance Director

### Starting Challenges

- Six clinics operating independently with inconsistent patient experiences
- Clinical outcomes varied significantly by location
- Difficulty recruiting and retaining therapists (three open positions unfilled for 6+ months)
- No visibility into clinic-level performance; only aggregate monthly financials
- The founder spent all day traveling between clinics putting out fires

### EOS Components Implemented

**Data Component:** A clinic-level weekly Scorecard was the first tool implemented. Each clinic tracked: new patient visits, patient visit volume, plan-of-care completion rate, patient satisfaction score, therapist utilization, and collections. Within weeks, performance differences between clinics became visible.

**Process Component:** The clinical delivery process ("The Recovery Path") was standardized across all six locations. Best practices from the top-performing clinic were documented and rolled out to all locations. Training was completed in one quarter.

**People Component:** Clinic managers were assessed using GWC. Two of six managers did not have the Capacity for the expanded management role. One was moved to a senior therapist role (a better fit). One exited. Replacements were hired using the core values interview process.

**Traction Component:** Each clinic ran its own weekly Level 10 meeting. The leadership team's Level 10 reviewed company-wide Scorecard data and clinic-level issues escalated from clinic meetings.

### Results

| Metric | Before EOS | After 12 Months | After 24 Months |
|--------|-----------|-----------------|-----------------|
| Revenue | $12M | $14.5M | $18M |
| Clinics | 6 | 6 | 8 |
| Patient Satisfaction | 4.1/5 avg | 4.5/5 avg | 4.7/5 avg |
| Plan Completion Rate | 62% | 78% | 85% |
| Therapist Turnover | 30% | 15% | 10% |
| Open Therapist Positions | 3 (6+ months) | 1 (filled in 45 days) | 0 |
| Rock Completion | N/A | 68% | 83% |
| Founder Hours in Clinics/Week | 40 | 15 | 5 |

### Key Lessons

1. Multi-location businesses benefit enormously from EOS because it creates consistency across locations while maintaining local autonomy through department-level Level 10 meetings.
2. The clinic-level Scorecard was transformative. Problems that had been invisible in aggregate monthly financials became obvious in weekly clinic-level data.
3. Standardizing the clinical process actually improved therapist satisfaction because it reduced decision fatigue and gave new hires a clear playbook.

## Common Patterns in Successful EOS Implementations

Across all case studies, consistent patterns emerge:

### What Successful Implementations Share

1. **Full leadership team commitment.** No partial adoption. Every leader attends every session and runs Level 10 meetings in their departments.
2. **Willingness to make hard people decisions.** Every company had at least one difficult personnel change in the first year. Delaying these decisions delayed results.
3. **Process documentation early.** Companies that documented core processes in the first two quarters saw faster improvements than those who waited.
4. **Weekly Scorecard discipline.** The Scorecard catches problems early. Companies that maintained weekly discipline consistently outperformed those that slipped to biweekly or monthly reviews.
5. **The Visionary steps back.** In every case, the founder/Visionary needed to delegate operational decisions to the Integrator. This was always uncomfortable and always transformative.

### What Separates Success from Failure

| Success Factor | Successful Companies | Failed Implementations |
|---------------|---------------------|----------------------|
| Commitment duration | 2+ year commitment | Quit after 6 months |
| Level 10 consistency | Never miss a meeting | Cancel when "busy" |
| People decisions | Made within 90 days | Avoided for quarters or years |
| Rocks discipline | Set SMART rocks, track weekly | Vague rocks, tracked monthly |
| Leadership alignment | Openly debate, then commit | Agree in the room, undermine outside |
| Patience with results | Expect Year 1 = foundation, Year 2 = results | Expect immediate transformation |

## Typical Results Timeline

### What to Expect at 6 Months

- Level 10 meetings are running weekly (may still feel awkward)
- Scorecard is producing weekly data (some metrics may still be unreliable)
- First set of quarterly rocks completed (completion rate typically 60-75%)
- V/TO is drafted but may need refinement
- 1-2 people decisions have been made or are in process
- Meeting hours have decreased; meeting quality has increased
- The team reports feeling "more aligned" but not yet "transformed"

### What to Expect at 1 Year

- Level 10 meetings score 7+ consistently
- Rock completion rate approaches 80%
- Scorecard is a trusted source of truth
- Core processes are documented (FBA may still be in progress)
- People issues are being addressed within 90 days
- Revenue and profit trends are improving
- The leadership team can articulate the V/TO from memory
- Department-level EOS tools are being rolled out

### What to Expect at 2 Years

- Level 10 meetings score 8+ consistently
- Rock completion rate is 80-90%
- Scorecard is reviewed reflexively; off-track metrics trigger immediate IDS
- Core processes are followed by all; new hires learn them in their first weeks
- People decisions are made confidently using the People Analyzer and GWC
- Revenue growth has accelerated
- Profit margins have improved
- Employee turnover has decreased
- The company runs with or without the founder present
- EOS is no longer a "program" -- it is simply how the company operates

# Data Component: Scorecards and Metrics

The Data Component replaces gut-feeling management with objective, weekly numbers. When everyone in the leadership team looks at the same 5-15 metrics every week, problems surface weeks earlier, accountability becomes automatic, and decision-making improves dramatically. This guide covers how to design a Scorecard, choose the right metrics, avoid common mistakes, and connect data to your Level 10 meetings.

## The Weekly Scorecard

A Scorecard is a one-page document that tracks 5-15 activity-based numbers weekly. It is reviewed in every Level 10 meeting. If a number is off track, it drops to the Issues List for IDS.

### Scorecard Design Principles

1. **Weekly cadence.** Monthly financials are too slow. By the time you see a monthly miss, you have lost four weeks of correction time. Weekly numbers give you early warning.
2. **Activity-based metrics.** Measure what people do (calls made, demos given), not just what happened (revenue, churn). Activities are leading indicators you can influence. Results are lagging indicators you can only observe.
3. **5-15 numbers.** Fewer than 5 means blind spots. More than 15 means noise. Most companies land on 8-12.
4. **Every number has an owner.** One person is accountable for each metric. Not a department. A name.
5. **Every number has a goal.** A number without a goal is just a data point. The goal creates the standard for red/green tracking.

## How to Choose Your Metrics

### The Vacation Test

Ask yourself: "If I went on vacation for four weeks with no phone or email, what 5-15 numbers would I want to see when I got back to know exactly how the business performed?"

This question forces you to identify the vital few numbers that genuinely indicate business health.

### Metric Selection by Category

| Category | What to Measure | Example Metrics |
|----------|----------------|-----------------|
| **Revenue** | Money coming in | Weekly revenue, new deal value, average deal size |
| **Pipeline** | Future revenue | New leads generated, qualified opportunities, proposals sent |
| **Sales Activity** | Effort going in | Calls made, demos completed, meetings booked |
| **Customer Health** | Retention and satisfaction | Churn rate, NPS, support tickets resolved, renewal rate |
| **Operations** | Delivery quality | On-time delivery %, defect rate, utilization rate |
| **Financial** | Cash and profitability | Cash balance, AR over 60 days, gross margin |
| **People** | Team health | Open positions, employee satisfaction score, training hours |

### Leading vs. Lagging Indicators

Understanding the difference between leading and lagging indicators is critical to building an effective Scorecard.

| Type | Definition | Response Time | Examples |
|------|-----------|--------------|---------|
| **Leading** | Measures input activities that drive future results | Can be corrected this week | Calls made, proposals sent, content published |
| **Lagging** | Measures output results that have already occurred | Can only be observed, not changed retroactively | Revenue, churn, profit margin |

**The ideal Scorecard is 70% leading indicators and 30% lagging indicators.** Leading indicators let you course-correct before lagging indicators go red.

### Building the Metric Chain

Great Scorecards show the cause-and-effect chain from activity to result:

```
Outbound emails (leading)
  → Meetings booked (leading)
    → Demos given (leading)
      → Proposals sent (leading)
        → Deals closed (lagging)
          → Revenue (lagging)
```

When revenue drops, you can trace back through the chain to find where the breakdown occurred. Was it fewer emails? Lower meeting conversion? Longer sales cycles? The Scorecard tells you.

## Every Number Has an Owner

### The Ownership Rule

Each metric on the Scorecard is assigned to one person. That person:
- Reports the number weekly in the Level 10 meeting
- Explains when the number is off track
- Owns the plan to get it back on track
- Drops it to the Issues List when help is needed

**Ownership does not mean they do all the work.** The VP of Sales owns the "demos completed" metric even though individual reps give the demos. Ownership means accountability for the result.

### Assigning Owners

| Metric | Owner | Why |
|--------|-------|-----|
| Weekly revenue | Head of Sales | Directly manages the revenue-generating team |
| New leads | Head of Marketing | Responsible for lead generation strategy |
| On-time delivery | Head of Operations | Manages delivery team and processes |
| Cash balance | Head of Finance | Manages cash flow and collections |
| Employee satisfaction | Head of People/Integrator | Responsible for culture and retention |

## Every Number Has a Goal

### Setting Goals

Goals should be based on:
- **Historical performance:** What have you averaged over the past 13 weeks?
- **Growth targets:** What does the 1-Year Plan require?
- **Capacity:** What is realistically achievable with current resources?

### Goal-Setting Template

| Metric | 13-Week Average | 1-Year Plan Requires | Goal |
|--------|----------------|---------------------|------|
| Weekly revenue | $42K | $60K/week by Q4 | $45K (Q1), $50K (Q2), $55K (Q3), $60K (Q4) |
| New leads | 80 | 120/week | 90 (Q1), 100 (Q2), 110 (Q3), 120 (Q4) |
| Demos completed | 15 | 25/week | 18 (Q1), 20 (Q2), 22 (Q3), 25 (Q4) |

Goals can be updated quarterly during the Quarterly Session. Do not change them mid-quarter unless the business model fundamentally changes.

## Red/Green Tracking

### How It Works

Each week, every metric is marked as green (on track) or red (off track):

- **Green:** Number meets or exceeds the goal
- **Red:** Number misses the goal

When a number is red, the owner has two options:
1. **Explain and fix:** The issue is understood and a correction is underway
2. **Drop to IDS:** The issue needs the team's input to solve

### Tracking Format

| Metric | Owner | Goal | W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 | W9 | W10 | W11 | W12 | W13 |
|--------|-------|------|----|----|----|----|----|----|----|----|----|----|-----|-----|-----|
| Revenue | Pat | $50K | G | G | R | G | G | G | R | G | G | G | G | G | G |
| Leads | Alex | 100 | G | R | R | G | G | G | G | G | G | R | G | G | G |
| Demos | Jordan | 20 | G | G | G | G | R | G | G | G | G | G | G | R | G |

**The 13-week trailing view** is essential. It shows trends, not just snapshots. Three consecutive red weeks on the same metric is a systemic issue that must be IDS'd.

## Scorecard Templates by Department

### Sales Scorecard

| Metric | Owner | Goal | Frequency |
|--------|-------|------|-----------|
| New qualified leads | SDR Manager | 50/week | Weekly |
| Discovery calls completed | Sales Manager | 25/week | Weekly |
| Proposals sent | Sales Manager | 10/week | Weekly |
| Deals closed | Sales Manager | 5/week | Weekly |
| New revenue booked | VP Sales | $75K/week | Weekly |
| Pipeline value | VP Sales | $500K+ | Weekly |
| Win rate | VP Sales | >25% | Weekly |

### Marketing Scorecard

| Metric | Owner | Goal | Frequency |
|--------|-------|------|-----------|
| Website visitors | Marketing Manager | 5,000/week | Weekly |
| Content pieces published | Content Lead | 3/week | Weekly |
| MQLs generated | Demand Gen Lead | 100/week | Weekly |
| Email open rate | Email Manager | >25% | Weekly |
| Social engagement | Social Lead | 500 interactions/week | Weekly |
| Cost per lead | VP Marketing | <$50 | Weekly |

### Operations Scorecard

| Metric | Owner | Goal | Frequency |
|--------|-------|------|-----------|
| Projects delivered on time | Project Manager | >90% | Weekly |
| Customer satisfaction (CSAT) | Support Lead | >4.5/5 | Weekly |
| Support tickets resolved | Support Lead | <24hr avg | Weekly |
| Utilization rate | Operations Manager | 75-85% | Weekly |
| Quality issues | QA Lead | <3/week | Weekly |
| Capacity available | Operations Manager | >15% buffer | Weekly |

### Finance Scorecard

| Metric | Owner | Goal | Frequency |
|--------|-------|------|-----------|
| Cash balance | Controller | >$300K | Weekly |
| AR over 60 days | AR Manager | <$50K | Weekly |
| Weekly cash burn | CFO | <$40K | Weekly |
| Invoices sent within 48hr | AR Manager | 100% | Weekly |
| Payroll accuracy | Payroll Lead | 100% | Weekly |

## Common Scorecard Mistakes

| Mistake | Why It Hurts | Fix |
|---------|-------------|-----|
| **Too many metrics (>15)** | Information overload, no focus | Cut to the vital few that indicate health |
| **All lagging indicators** | Cannot course-correct, only observe | Add leading indicators: activities and inputs |
| **No owner assigned** | "Someone will handle it" means nobody does | One name per metric, no exceptions |
| **Goals too easy** | Scorecard is always green, masks problems | Set goals that require effort but are achievable |
| **Goals too hard** | Scorecard is always red, creates learned helplessness | Base goals on 13-week average plus realistic stretch |
| **Not reviewed weekly** | Data goes stale, accountability disappears | Scorecard is agenda item #2 in every Level 10 meeting |
| **Monthly instead of weekly** | Lose 4 weeks of correction time | Convert monthly metrics to weekly proxies |
| **Vanity metrics** | Numbers that look good but do not drive the business | Replace with metrics tied to revenue or customer outcomes |
| **No trending view** | See this week but miss the pattern | Always show 13 trailing weeks |
| **Changing metrics too often** | No baseline for comparison | Lock metrics for at least one full quarter |

## Activity-Based vs. Results-Based Metrics

### When to Use Each

**Activity-based metrics** are best when:
- You need early warning signals
- You want to influence behavior
- The sales cycle is long (weeks or months)
- You are building new processes

**Results-based metrics** are best when:
- You need to confirm the activities are producing outcomes
- You are reporting to a board or investors
- The metric is a business health vital sign (cash, churn, revenue)

### Balanced Scorecard Example

```
LEADING (Activities)          LAGGING (Results)
├── Calls made                ├── Revenue
├── Demos given               ├── Profit margin
├── Proposals sent            ├── Customer churn
├── Content published         ├── NPS score
├── Candidates interviewed    └── Cash balance
└── Tickets resolved
```

A healthy Scorecard has both types in roughly a 70/30 split favoring leading indicators.

## How the Scorecard Connects to Level 10 Meetings

The Scorecard is reviewed in the first 5 minutes of the Level 10 meeting, right after the Segue. Here is the protocol:

### Scorecard Review Protocol

1. **Display the Scorecard** so all attendees can see it (projector, shared screen, or printed)
2. **Go metric by metric.** The owner reads the number and states "on track" or "off track."
3. **No discussion during review.** If a number is off track, the owner simply states the number and says "dropping to Issues List."
4. **Time limit: 5 minutes.** This is a quick scan, not a deep dive. Deep dives happen during IDS.
5. **Pattern recognition.** If the same metric is red three weeks in a row, it is automatically the top issue for IDS.

### From Scorecard to IDS

When a metric is off track, the flow is:

```
Scorecard review → Metric is red → Owner drops to Issues List
  → During IDS, team identifies root cause
    → Action items assigned (who, what, by when)
      → Next week: check if action item is complete
        → Check if metric returned to green
```

This weekly cycle ensures no problem goes unaddressed for more than one week. The Scorecard is the early warning system. The Level 10 meeting is the response mechanism.

## Building Your First Scorecard

### Week 1 Checklist

- [ ] Brainstorm 20-30 possible metrics with the leadership team
- [ ] Apply the vacation test to narrow to 5-15
- [ ] Assign one owner per metric
- [ ] Set goals based on 13-week historical average plus 10% stretch
- [ ] Create a simple spreadsheet with 13 trailing weeks
- [ ] Commit to reviewing it in the next Level 10 meeting

### Weeks 2-4: Refine

- [ ] Remove metrics that are always green (too easy or not meaningful)
- [ ] Replace metrics that nobody understands
- [ ] Adjust goals that were set too high or too low
- [ ] Ensure every department has at least one metric on the Scorecard

### Month 2+: Mature

- [ ] Everyone can recite the Scorecard metrics from memory
- [ ] The team looks forward to Scorecard review (it creates clarity)
- [ ] Off-track metrics are solved quickly through IDS
- [ ] New hires are shown the Scorecard in their first week
- [ ] Department-level scorecards cascade from the company Scorecard

# EOS Implementation: The Two-Year Journey

Implementing EOS is not a one-day workshop or a one-month project. It is a systematic, two-year journey that transforms how a company operates. This guide covers the complete implementation timeline, session agendas, the choice between self-implementation and using a certified EOS Implementer, getting buy-in, rolling out to the organization, common failures, and the EOS maturity assessment.

## The Implementation Timeline

EOS implementation follows a structured sequence of sessions over roughly two years. Each session builds on the previous one, layering in new tools and reinforcing existing ones.

### Year 1: Foundation

| Session | Timing | Duration | Focus |
|---------|--------|----------|-------|
| **Focus Day** | Month 0 | Full day (8 hours) | Accountability Chart, Rocks, Scorecard, Level 10 Meeting |
| **Vision Building Day 1** | Month 1 | Full day (8 hours) | Core Values, Core Focus, 10-Year Target, Marketing Strategy |
| **Vision Building Day 2** | Month 2 | Full day (8 hours) | 3-Year Picture, 1-Year Plan, Quarterly Rocks, Issues List |
| **Quarterly Session 1** | Month 5 | Full day (8 hours) | Rock review, new rocks, IDS strategic issues |
| **Quarterly Session 2** | Month 8 | Full day (8 hours) | Rock review, new rocks, process documentation |
| **Annual Planning** | Month 11 | 2 days (16 hours) | Full V/TO review, 1-Year Plan, Q1 rocks for Year 2 |

### Year 2: Mastery

| Session | Timing | Duration | Focus |
|---------|--------|----------|-------|
| **Quarterly Session 3** | Month 14 | Full day (8 hours) | Rock review, people analysis, process refinement |
| **Quarterly Session 4** | Month 17 | Full day (8 hours) | Rock review, scorecard optimization, IDS |
| **Quarterly Session 5** | Month 20 | Full day (8 hours) | Rock review, organizational checkup |
| **Annual Planning 2** | Month 23 | 2 days (16 hours) | Full V/TO review, assess EOS maturity, plan for independence |

After Year 2, the company should be self-sufficient in running EOS. The leadership team facilitates their own sessions, and EOS becomes the operating rhythm of the company.

## Focus Day: Agenda and Outcomes

The Focus Day is the starting point. It installs the foundational tools that create immediate traction.

### Focus Day Agenda

| Time | Activity | Details |
|------|----------|---------|
| 8:00-8:30 | **Welcome and Overview** | What is EOS? The Six Key Components. What to expect today. |
| 8:30-10:00 | **Accountability Chart** | Structure the organization by function, not people. Define the 3-5 major seats. Identify the Visionary and Integrator. |
| 10:00-10:15 | Break | |
| 10:15-11:30 | **Accountability Chart (cont.)** | Assign names to seats. Apply GWC to each person. Identify people issues (do not solve today -- add to Issues List). |
| 11:30-12:30 | Lunch | |
| 12:30-2:00 | **Rocks** | Brainstorm and set the first quarter's rocks. Apply SMART criteria. Assign owners. |
| 2:00-2:15 | Break | |
| 2:15-3:30 | **Scorecard** | Identify 5-15 weekly metrics. Assign owners. Set goals. Build the first Scorecard. |
| 3:30-4:30 | **Level 10 Meeting** | Walk through the 90-minute agenda. Practice each section. Schedule the first real Level 10 for next week. |
| 4:30-5:00 | **Wrap-Up** | Review commitments. Confirm next session date. Q&A. |

### Focus Day Outcomes

- [ ] Accountability Chart drafted with names in seats
- [ ] 3-7 quarterly rocks set with owners
- [ ] Weekly Scorecard designed with 5-15 metrics
- [ ] First Level 10 meeting scheduled
- [ ] People issues identified (not yet solved)
- [ ] Leadership team aligned on next steps

## Vision Building Day 1: Agenda and Outcomes

VB1 focuses on the Vision side of the V/TO: the long-term identity and direction of the company.

### VB1 Agenda

| Time | Activity | Details |
|------|----------|---------|
| 8:00-8:30 | **Check-In** | How is EOS going? Wins, struggles, questions since Focus Day. |
| 8:30-10:30 | **Core Values** | Discovery exercise: generate 50+, consolidate to themes, narrow to 3-7. Define behavioral indicators. |
| 10:30-10:45 | Break | |
| 10:45-12:00 | **Core Focus** | Define purpose/cause/passion and niche. Test against current business activities. |
| 12:00-1:00 | Lunch | |
| 1:00-2:30 | **10-Year Target** | Set the BHAG. Ensure it is specific, measurable, and inspiring. |
| 2:30-2:45 | Break | |
| 2:45-4:30 | **Marketing Strategy** | Define target market, three uniques, proven process, guarantee. |
| 4:30-5:00 | **Wrap-Up** | Review Vision page of V/TO. Confirm completeness. Schedule VB2. |

### VB1 Outcomes

- [ ] 3-7 Core Values defined with behavioral indicators
- [ ] Core Focus statement (purpose + niche) completed
- [ ] 10-Year Target set
- [ ] Marketing Strategy defined (all four parts)
- [ ] Vision page of V/TO complete

## Vision Building Day 2: Agenda and Outcomes

VB2 focuses on the Traction side of the V/TO: the near-term execution plan.

### VB2 Agenda

| Time | Activity | Details |
|------|----------|---------|
| 8:00-8:30 | **Check-In** | Review VB1 decisions. Any adjustments needed? Level 10 meeting feedback. |
| 8:30-10:00 | **3-Year Picture** | Paint a vivid, specific picture of the company in three years. Revenue, profit, headcount, key metrics, qualitative description. |
| 10:00-10:15 | Break | |
| 10:15-12:00 | **1-Year Plan** | Set revenue, profit, and 3-7 specific goals for the next twelve months. |
| 12:00-1:00 | Lunch | |
| 1:00-2:30 | **Quarterly Rocks** | Review and refine rocks set on Focus Day (or set new ones if Q1 has ended). Apply SMART criteria. |
| 2:30-2:45 | Break | |
| 2:45-4:00 | **Issues List** | Build the long-term and short-term Issues Lists. IDS the top 3 strategic issues. |
| 4:00-4:30 | **V/TO Review** | Review the complete V/TO (both pages). Confirm leadership alignment. |
| 4:30-5:00 | **Next Steps** | Plan the company-wide V/TO rollout. Schedule the next quarterly session. |

### VB2 Outcomes

- [ ] 3-Year Picture completed
- [ ] 1-Year Plan with specific goals set
- [ ] Quarterly Rocks confirmed or updated
- [ ] Issues List populated (long-term and short-term)
- [ ] Complete V/TO document finalized
- [ ] Company-wide rollout meeting scheduled

## Quarterly Session Format

After the initial foundation-building sessions, quarterly sessions follow a consistent format:

### Standard Quarterly Session Agenda (8 hours)

| Time | Activity | Details |
|------|----------|---------|
| 8:00-8:30 | **Check-In** | Segue, what's working, what's not |
| 8:30-9:30 | **Previous Quarter Rock Review** | Score each rock (done/not done). Calculate completion rate. Celebrate wins. |
| 9:30-10:00 | **People Headlines** | Review Accountability Chart. Any people issues? People Analyzer updates. |
| 10:00-10:15 | Break | |
| 10:15-11:15 | **V/TO Review** | Quick review of V/TO for any needed updates. Are we on track for 1-Year Plan? |
| 11:15-12:00 | **IDS Strategic Issues (Part 1)** | Tackle long-term Issues List items |
| 12:00-1:00 | Lunch | |
| 1:00-2:30 | **IDS Strategic Issues (Part 2)** | Continue solving strategic issues |
| 2:30-2:45 | Break | |
| 2:45-4:00 | **Set Next Quarter Rocks** | Brainstorm, prioritize, apply SMART, assign owners |
| 4:00-4:30 | **Cascading Messages and Next Steps** | What messages go to the rest of the company? |
| 4:30-5:00 | **Conclude** | Rate the session. Feedback. Confirm next quarterly date. |

## Annual Planning Session Format

The annual session is a two-day event that combines a full V/TO review with detailed planning for the next year.

### Day 1: Review and Reflect

| Time | Activity |
|------|----------|
| 8:00-8:30 | Check-in and segue |
| 8:30-10:00 | Year in review: what worked, what did not, key lessons |
| 10:00-12:00 | V/TO review: Core Values, Core Focus, 10-Year Target (any changes?) |
| 12:00-1:00 | Lunch |
| 1:00-2:30 | Marketing Strategy review and update |
| 2:30-4:30 | 3-Year Picture update |
| 4:30-5:00 | Day 1 wrap-up |

### Day 2: Plan and Commit

| Time | Activity |
|------|----------|
| 8:00-8:30 | Day 2 kickoff |
| 8:30-10:30 | 1-Year Plan: set revenue, profit, and 3-7 goals |
| 10:30-12:00 | IDS strategic issues |
| 12:00-1:00 | Lunch |
| 1:00-3:00 | Q1 Rocks: brainstorm, prioritize, SMART check, assign |
| 3:00-4:00 | People review: Accountability Chart, People Analyzer |
| 4:00-4:30 | Cascading messages and rollout plan |
| 4:30-5:00 | Rate session, feedback, celebrate |

## Self-Implementation vs. EOS Implementer

### Comparison

| Factor | Self-Implementation | EOS Implementer |
|--------|-------------------|-----------------|
| **Cost** | Free (book + time) | $50K-$100K+ over 2 years |
| **Speed** | Slower (learning while doing) | Faster (experienced facilitator) |
| **Facilitation** | Integrator or Visionary facilitates (hard to participate and facilitate) | Neutral third party facilitates (leadership fully participates) |
| **Accountability** | Self-policed | External accountability partner |
| **Customization** | High flexibility (can adapt tools) | Purist approach (tools used as designed) |
| **Common for** | Bootstrapped companies, strong Integrators | Funded companies, teams with internal conflict |
| **Risk** | Higher (easy to skip hard parts) | Lower (Implementer pushes through resistance) |

### When to Self-Implement

- The leadership team has read *Traction* and is aligned on implementing EOS
- The Integrator is a strong facilitator who can run sessions
- Budget constraints make an Implementer impractical
- The company is smaller (under 20 people) and the dynamics are simpler

### When to Hire an Implementer

- The leadership team has unresolved conflict that requires a neutral party
- No one on the team is a strong enough facilitator
- Previous self-implementation attempts have stalled
- The company is growing fast and cannot afford a slow rollout
- The budget allows for the investment ($4K-$8K per session, typically 10-12 sessions)

## Getting Leadership Team Buy-In

EOS only works if the entire leadership team is committed. Partial adoption creates more problems than it solves.

### The Buy-In Process

**Step 1: Share the book.** Give every leadership team member a copy of *Traction*. Ask them to read it within two weeks.

**Step 2: Discuss openly.** Schedule a 2-hour meeting to discuss:
- What resonated? What did not?
- What problems could EOS solve for us?
- What concerns or objections do people have?

**Step 3: Address objections honestly.**

| Common Objection | Response |
|-----------------|----------|
| "We don't have time for another meeting" | Level 10 replaces your existing meetings, not adds to them. Most companies cut total meeting time. |
| "This is too rigid" | The tools are simple and flexible. The discipline is what creates results. |
| "We've tried frameworks before" | EOS is not a flavor-of-the-month. It is a complete operating system adopted consistently for two years. |
| "I don't want to be told how to run my department" | EOS defines what to achieve, not how to achieve it. Your autonomy within your seat is preserved. |
| "Our business is different" | EOS works for every entrepreneurial company. Over 250,000 companies use it across every industry. |

**Step 4: Commitment vote.** After the discussion, ask each leader: "Are you in? Yes or no." Anything less than full commitment from the entire leadership team means EOS will struggle.

## Rolling Out EOS to the Whole Organization

Once the leadership team has completed Focus Day, VB1, and VB2, it is time to share the vision with the entire company.

### The Company-Wide Rollout Meeting

**Duration:** 90 minutes
**Attendees:** Everyone in the company

**Agenda:**
1. **What is EOS?** (10 min) Brief overview of the Six Key Components
2. **Our Core Values** (15 min) Share each value with behavioral indicators and examples
3. **Our Core Focus** (10 min) Purpose and niche
4. **Our V/TO** (20 min) Walk through the complete V/TO: 10-Year Target, 3-Year Picture, 1-Year Plan, Quarterly Rocks
5. **What Changes for You** (15 min) Level 10 meetings at every level, rocks for every team, scorecards for every department
6. **Q&A** (20 min) Open floor for questions

### Departmental Rollout

After the company-wide meeting, each department head runs a department-level session:

- [ ] Share how the department supports the company rocks
- [ ] Set department-level rocks for the quarter
- [ ] Build a department-level Scorecard
- [ ] Schedule the department's weekly Level 10 meeting
- [ ] Answer team-specific questions

## Common Implementation Failures and How to Avoid Them

| Failure | Root Cause | Prevention |
|---------|-----------|------------|
| **EOS fades after 3 months** | Leadership loses discipline when initial excitement wears off | Commit to the full 2-year journey. Schedule all sessions in advance. |
| **Level 10 meetings get cancelled** | "Too busy" becomes an excuse | Non-negotiable: the meeting happens every week, no exceptions. |
| **Visionary disengages** | Visionaries get bored with operational discipline | Define the Visionary's specific roles and keep them engaged in strategic IDS. |
| **Integrator overwhelmed** | Integrator tries to do everything | Delegate operational functions. The Integrator manages leaders, not tasks. |
| **Rocks are set but not tracked** | Weekly review skipped or superficial | Track rocks in every Level 10. IDS off-track rocks immediately. |
| **People issues avoided** | Leadership avoids hard conversations | Use the People Analyzer as an objective tool. Set 90-day deadlines. |
| **Core values are ignored** | Values defined but not used in hiring, firing, or reviews | Reference values in every people decision. Fire someone who violates values (it sends a message). |
| **Partial adoption** | Some leaders do EOS, others do not | Full leadership team must be committed. No opt-outs. |
| **Overcomplication** | Adding extra tools, extra metrics, extra meetings | Keep it simple. EOS is powerful because it is simple. Resist the urge to add complexity. |
| **No cascading to departments** | EOS stays at the leadership level | Every department should have Level 10s, rocks, and scorecards within 6 months. |

## EOS Maturity Assessment

Use this assessment quarterly to track your EOS implementation progress. Rate each item 1-5 (1 = not started, 5 = mastered).

Rate each item 1-5 (1 = not started, 5 = mastered). 30 items total across all six components.

| Component | Key Items to Rate |
|-----------|------------------|
| **Vision** | V/TO complete, leadership aligned, shared with org, reviewed quarterly, filters all decisions |
| **People** | Accountability Chart defined, single owners, People Analyzer run, GWC assessed, tough decisions made in 90 days |
| **Data** | 5-15 weekly metrics, owners and goals set, reviewed in Level 10, off-track IDS'd, department scorecards exist |
| **Issues** | IDS used consistently, root cause focus, permanent solutions, both lists maintained, safe to raise issues |
| **Process** | 5-7 core processes identified, documented, trained and followed, compliance measured, reviewed quarterly |
| **Traction** | Rocks set and tracked, 80%+ completion, weekly Level 10s, meetings score 8+, to-do completion 90%+ |

**Scoring (out of 150):**
- **120-150:** EOS mastery. Fully embedded.
- **90-119:** Strong adoption. Close remaining gaps.
- **60-89:** Good progress. Focus on lowest-scoring areas.
- **30-59:** Early implementation. Stay the course.
- **Below 30:** Just starting. Commit to the two-year journey.

# Issues Component: IDS Process Deep Dive

Every organization has issues. The difference between great companies and mediocre ones is how quickly and permanently they solve them. The Issues Component provides a disciplined process called IDS -- Identify, Discuss, Solve -- that turns chronic problems into resolved action items. This guide covers the full IDS framework, facilitation techniques, issue types, list management, and practice scenarios.


## Table of Contents
1. [The IDS Framework](#the-ids-framework)
2. [Step 1: Identify the Real Issue](#step-1-identify-the-real-issue)
3. [Step 2: Discuss](#step-2-discuss)
4. [Step 3: Solve](#step-3-solve)
5. [Three Types of Issues](#three-types-of-issues)
6. [Issues List Management](#issues-list-management)
7. [Common IDS Facilitation Mistakes](#common-ids-facilitation-mistakes)
8. [Practice Scenarios for IDS Training](#practice-scenarios-for-ids-training)

---

## The IDS Framework

IDS stands for Identify, Discuss, Solve. It is the core problem-solving methodology in EOS, used in every Level 10 meeting and every quarterly session. The framework is deliberately simple because simplicity drives discipline.

```
IDENTIFY the real issue
    ↓
DISCUSS openly and efficiently
    ↓
SOLVE with clear action items
```

### Why IDS Works

| Traditional Problem Solving | IDS |
|---------------------------|-----|
| Discusses symptoms endlessly | Forces identification of root cause first |
| Everyone gets equal airtime | Everyone gets input, not equal time |
| Conversations meander | Tangents are stopped immediately |
| Decisions deferred | Decision made before moving on |
| Vague next steps | Specific who/what/when action items |
| Same issue returns next week | Solved permanently or escalated |

## Step 1: Identify the Real Issue

This is the most critical and most frequently skipped step. Teams jump to discussion before they agree on what the actual issue is.

### Root Cause Analysis

**The symptom is not the issue.** The issue is the root cause underneath the symptom. Use these techniques to dig deeper:

**The Five Whys:**
1. Revenue is down this quarter. Why?
2. We closed fewer deals. Why?
3. We gave fewer demos. Why?
4. We had fewer qualified leads. Why?
5. Our main lead source (paid ads) stopped converting after the algorithm change.

**Root cause:** Overdependence on a single lead source. The fix is not "close more deals." The fix is "diversify lead generation channels."

**The One-Sentence Test:**

After identifying the issue, state it in one sentence. If you cannot state it in one sentence, you have not identified it clearly enough.

| Vague | Clear |
|-------|-------|
| "We have a marketing problem" | "Our paid ad CAC increased 40% after the platform algorithm change and we have no alternative lead channels" |
| "The team isn't performing" | "Three of five reps are below 80% quota because they are not following the demo script" |
| "Customer complaints are up" | "Onboarding takes 3 weeks instead of 1, causing 60% of complaints" |

### Identifying the Real Issue: Checklist

- [ ] State the symptom that surfaced the issue
- [ ] Ask "Why?" at least three times to find the root cause
- [ ] State the root cause in one clear sentence
- [ ] Confirm with the group: "Is this the real issue, or is there something deeper?"
- [ ] If the group disagrees on the root cause, spend more time on Identify before moving to Discuss

## Step 2: Discuss

Discussion is where the team adds perspective, data, and experience. The goal is not consensus. The goal is to hear all relevant input so the best decision can be made.

### Discussion Facilitation Techniques

**The Round-Robin Open:**
Go around the table. Each person gets 60 seconds of uninterrupted input. No rebuttals during the round. This ensures quieter voices are heard before dominant personalities take over.

**The Data Check:**
Before opinions fly, ask: "What data do we have on this?" Opinions without data are just guesses. If no data exists, note it as an action item to gather data before the next meeting.

**The Tangent Stop:**
When the discussion drifts off topic, the facilitator says: "That's a separate issue. I'm adding it to the Issues List. Let's get back to [original issue]." No apology needed. This is not rude -- it is discipline.

**The Devil's Advocate:**
If the group is quickly converging on a solution, pause and ask: "What could go wrong with this approach?" or "If we're wrong, what would that look like?" This prevents groupthink.

**Time-Boxing:**
Most issues should take 5-15 minutes to IDS. If an issue is taking longer than 15 minutes:
- The issue may be too big for a Level 10 meeting (move to a separate meeting)
- The team may not have enough information (create a to-do to gather data)
- The facilitator may be allowing tangents (tighten the discussion)

### Discussion Ground Rules

| Rule | Rationale |
|------|-----------|
| One conversation at a time | Side conversations split attention |
| No devices | Full presence required |
| Attack the issue, not the person | Psychological safety enables honest input |
| Share your perspective, then let go | Once you've said it, trust the process |
| Facilitator controls the floor | Prevents dominant personalities from hijacking |
| Silence is agreement | If you don't speak up, you support the outcome |

## Step 3: Solve

Solving means making a decision and assigning action items. A discussion without a clear decision and next steps is wasted time.

### The Solve Protocol

1. **State the decision.** The facilitator summarizes: "Here is what we've decided."
2. **Confirm agreement.** Quick fist-to-five: 0 = block, 3 = can live with it, 5 = love it. Anything 3+ moves forward.
3. **Assign action items.** Every action item has three elements:

| Element | Example |
|---------|---------|
| **Who** | Sarah |
| **What** | Research three alternative lead gen channels and present options |
| **When** | By next Tuesday's Level 10 |

4. **Record it.** The action item goes on the To-Do List (7-day items) or becomes a Rock (if it is a 90-day initiative).
5. **Move on.** Do not revisit. Do not second-guess. The decision is made.

### Solve Outcomes

Not every issue results in an action item. There are several possible outcomes:

| Outcome | When to Use | Example |
|---------|------------|---------|
| **Action item (To-Do)** | Issue can be resolved in 7 days | "Jordan will update the pricing page by Friday" |
| **Rock** | Issue requires 90 days of effort | "Launch customer success program" becomes a Q2 rock |
| **Kill it** | Issue is not worth pursuing | "We decided the new feature request doesn't align with our Core Focus" |
| **Information needed** | Cannot decide without data | "Alex will pull churn data by cohort and present next week" |
| **Escalate** | Beyond the team's authority | "This requires board approval; Integrator will present at next board meeting" |
| **Combine** | Issue is a duplicate | "This is the same root cause as issue #3; we'll solve them together" |

## Three Types of Issues

### Problems

**Definition:** Something that is broken, underperforming, or causing pain.

**Examples:**
- Customer churn increased from 3% to 7% this quarter
- Two team members are in open conflict and it is affecting the department
- Our main vendor raised prices 25% and our margins are squeezed

**IDS approach:** Focus on root cause. The fix should prevent recurrence, not just patch the symptom.

### Ideas

**Definition:** A new opportunity, initiative, or approach that someone wants to propose.

**Examples:**
- "What if we added a freemium tier to our product?"
- "I think we should open a second office in Austin."
- "Should we sponsor the industry conference this year?"

**IDS approach:** The decision is yes, no, or not now. If yes, it becomes a to-do or rock. If not now, it stays on the long-term Issues List.

### Obstacles

**Definition:** Something blocking a Rock or key initiative from moving forward.

**Examples:**
- Engineering capacity is blocking the product launch rock
- Legal review is delaying the partnership agreement
- Budget constraints prevent hiring the needed role

**IDS approach:** Remove the obstacle or find a workaround. If the obstacle is outside the team's control, escalate it.

## Issues List Management

### Two Lists

EOS maintains two Issues Lists:

| List | Contents | Reviewed |
|------|----------|----------|
| **Short-Term (Level 10)** | Tactical issues for this week | Every Level 10 meeting |
| **Long-Term (V/TO)** | Strategic issues for quarterly sessions | Every quarterly session |

### Adding Issues

Anyone in the organization can add issues to either list. The format is simple: a short phrase that captures the issue. Details are discussed live during IDS.

**Good issue entries:**
- "Sales demo no-show rate is 40%"
- "Need to decide on CRM migration"
- "Conflict between engineering and product on roadmap priorities"

**Poor issue entries:**
- "Marketing" (too vague)
- "Everything" (not an issue)
- Three paragraphs of background (save it for discussion)

### Prioritizing Issues

At the start of IDS in every Level 10 meeting:

1. **Review the list.** Read each issue title aloud.
2. **Identify the top 3.** Ask: "Which three issues, if solved today, would have the biggest impact?"
3. **Number them 1, 2, 3.** Start with number 1.
4. **Re-prioritize after each solve.** The top 3 may shift as issues are resolved.

**Critical rule:** Not all issues get solved every meeting. That is expected. Unsolved issues carry forward to next week. What matters is that you always work on the most important issues first.

### Issue Hygiene

Every quarter, review the long-term Issues List:
- Remove issues that are no longer relevant
- Promote issues that have become urgent to the short-term list
- Merge duplicate issues
- Clarify vague entries

## Common IDS Facilitation Mistakes

| Mistake | Impact | Fix |
|---------|--------|-----|
| **Skipping Identify** | Team solves the wrong problem | Require the one-sentence root cause statement before any discussion |
| **Discussion without structure** | Conversation goes in circles | Use round-robin, then open discussion, then time-box |
| **Allowing tangents** | Meeting goes long, real issues not addressed | Facilitator immediately names tangent and redirects |
| **Seeking consensus** | Decisions watered down to please everyone | Integrator makes the call if team cannot agree in 15 minutes |
| **No action items** | "Great discussion" but nothing changes | Facilitator does not close an issue without who/what/when |
| **Rehashing solved issues** | Undermines the process, wastes time | Once solved, it is done. If the solution did not work, it is a new issue |
| **One person dominates** | Other perspectives are lost | Facilitator actively invites input: "We haven't heard from you, what's your take?" |
| **Too polite** | Real issues avoided to maintain comfort | Establish that healthy conflict is expected and valued |
| **Solving symptoms** | Root cause persists, issue returns | Ask "Why?" at least three times before moving to Discuss |

## Practice Scenarios for IDS Training

Use these scenarios to practice IDS with your leadership team. Each scenario should take 10-15 minutes.

### Scenario 1: The Underperforming Sales Rep

**Symptom:** Q2 revenue is 20% below target.

**Information revealed during Identify:**
- One of four reps is at 30% of quota
- That rep was a top performer last year
- They recently took on a new territory
- Their pipeline is full but close rate dropped from 30% to 8%

**Practice questions:**
- What is the real issue? (Symptom vs. root cause)
- What data would you want before discussing solutions?
- What are three possible root causes?

### Scenario 2: The Competing Priorities

**Symptom:** Engineering team missed their Rock deadline by four weeks.

**Information revealed during Identify:**
- The VP of Sales requested "urgent" feature changes mid-quarter
- Engineering spent 3 weeks on unplanned work
- No one in leadership approved the scope change
- This is the third quarter in a row this has happened

**Practice questions:**
- Who owns the decision about engineering priorities?
- Is this a people issue, a process issue, or both?
- What structural change would prevent recurrence?

### Scenario 3: The Culture Problem

**Symptom:** Three employees resigned in the past month, all citing "culture."

**Information revealed during Identify:**
- Exit interviews mention a specific manager who "rules by fear"
- That manager's team has the highest performance metrics in the company
- Two of the departing employees were identified as high-potential
- The manager has been with the company for seven years

**Practice questions:**
- Is this a right person or right seat issue?
- How do you weigh performance metrics against culture impact?
- What is the root cause: the manager's behavior, or the system that enabled it?

### Scenario 4: The Strategic Opportunity

**Symptom:** A major competitor just went out of business, freeing up 200 potential customers.

**Information revealed during Identify:**
- Your team is already at capacity
- Hiring 5 new reps would take 3-4 months
- A partner firm could handle overflow but at lower margins
- The window of opportunity is 60-90 days before other competitors move in

**Practice questions:**
- Is this a problem, an idea, or an obstacle?
- What is the core decision that needs to be made?
- What are the trade-offs of each option?

### Scenario 5: The Process Breakdown

**Symptom:** Customer onboarding satisfaction dropped from 4.5 to 3.2 out of 5.

**Information revealed during Identify:**
- The onboarding team grew from 2 to 6 people in the past quarter
- The four new hires were trained informally by the two original team members
- There is no documented onboarding process
- The two original team members each do onboarding differently

**Practice questions:**
- Which EOS component is this really about? (Process? People? Both?)
- What is the fastest fix? What is the permanent fix?
- How would you prevent this from recurring as the team continues to grow?

# Level 10 Meeting: Complete Facilitation Guide

The Level 10 Meeting is the most important meeting in the Entrepreneurial Operating System. It is a weekly, 90-minute leadership team meeting that follows a precise agenda, creates accountability, surfaces issues, and keeps the company on track. When run well, it eliminates the need for most other meetings. This guide covers every section of the agenda, facilitation protocols, rules, and how to consistently score 8 or higher.

## Why "Level 10"

At the end of every Level 10 meeting, each participant rates the meeting on a scale of 1-10. The goal is for every meeting to score a 10 -- hence the name. In practice, teams aim for a consistent 8 or above. The rating system creates a feedback loop: if the meeting scores below 8, the team discusses what to improve, and the facilitator adjusts.

## The Non-Negotiable Rules

Before diving into the agenda, these rules are absolute:

| Rule | Why It Matters |
|------|---------------|
| Same day, same time, every week | Rhythm creates discipline. No rescheduling. |
| Starts on time | Waiting for stragglers trains people to be late. Start without them. |
| Ends on time (90 minutes) | Parkinson's law: work expands to fill the time available. Hard stop at 90 minutes. |
| No cancellations | The meeting happens even if two people are out. Cancel only for true emergencies (office fire, not a client call). |
| Full attendance expected | If someone misses more than 2 in a quarter, it is an issue to IDS. |
| No phones or laptops | Except for the person taking notes and anyone referencing the shared agenda. |
| One conversation at a time | Side conversations are stopped immediately by the facilitator. |

## The 90-Minute Agenda

The agenda is fixed. It does not change week to week. This predictability is a feature, not a bug. Everyone knows exactly what to expect, which reduces meeting anxiety and increases preparation.

```
00:00 - 05:00  Segue (Good News)
05:00 - 10:00  Scorecard Review
10:00 - 15:00  Rock Review
15:00 - 20:00  Customer/Employee Headlines
20:00 - 25:00  To-Do List Review
25:00 - 85:00  IDS (Identify, Discuss, Solve)
85:00 - 90:00  Conclude
```

## Section 1: Segue (5 Minutes)

### Purpose

Start with a human connection. Each person shares one piece of good news -- personal or professional. This transitions the team from whatever they were doing before the meeting into a present, connected state.

### Protocol

- Go around the table, one person at a time
- 30-45 seconds per person
- Personal news is encouraged (not just work wins)
- No discussion or follow-up questions during the segue
- The facilitator keeps it moving

### Examples of Good Segue News
- "My daughter scored her first soccer goal this weekend."
- "We just signed a deal I've been working on for three months."
- "I finished a half marathon on Saturday."
- "Our team hit 100% on their to-dos for the first time."

### Why It Matters

The Segue sets the tone. Teams that skip it jump straight into problems and data without any human connection. The 5-minute investment builds trust and camaraderie that pays dividends during difficult IDS conversations later in the meeting.

## Section 2: Scorecard Review (5 Minutes)

### Purpose

Review the weekly Scorecard to identify any metrics that are off track.

### Protocol

1. Display the Scorecard (screen, projector, or printout)
2. Go metric by metric. The owner states the number.
3. If the number is on track (green), move on. No discussion.
4. If the number is off track (red), the owner says: "Off track. Dropping to Issues List."
5. No discussion during Scorecard review. All off-track numbers will be IDS'd later.
6. Total time: 5 minutes maximum.

### Facilitator Tips

- Move quickly. The Scorecard is a scan, not a deep dive.
- If someone starts explaining why a number is red, gently stop them: "We'll get to it during IDS."
- Track consecutive red weeks. Three in a row means it automatically becomes the first issue in IDS.

## Section 3: Rock Review (5 Minutes)

### Purpose

Review the status of every quarterly Rock to ensure progress is on track.

### Protocol

1. Display the Rock sheet
2. Go person by person. Each leader states each Rock and one word: "On track" or "Off track."
3. No discussion or explanation during review
4. Off-track rocks are noted and may be added to the Issues List
5. Total time: 5 minutes

### On Track vs. Off Track

A Rock is on track if the owner believes, based on current progress, it will be completed by the end of the quarter. It is off track if there is meaningful risk of missing the deadline.

**Rules:**
- Be honest. Declaring "on track" when you know it is at risk wastes the team's time when the truth surfaces later.
- Off track is not shameful. It is information that lets the team help.
- If a Rock has been off track for 3+ consecutive weeks, it must be IDS'd.

## Section 4: Customer/Employee Headlines (5 Minutes)

### Purpose

Share brief, important updates about customers and employees that the leadership team needs to know about.

### Protocol

1. Go around the table
2. Each person shares 1-2 headlines (not stories, headlines)
3. Format: "[Good/Bad news]: [One sentence summary]"
4. If a headline needs discussion, it drops to the Issues List
5. Total time: 5 minutes

### Examples

| Type | Headline |
|------|----------|
| Customer (positive) | "Acme Corp renewed for 3 years and doubled their contract" |
| Customer (negative) | "Beta Industries is threatening to leave due to implementation delays" |
| Employee (positive) | "Sarah passed her certification exam on the first attempt" |
| Employee (negative) | "We lost two engineers to a competitor this week" |

### Headlines, Not Stories

The facilitator must enforce brevity. A headline is one sentence. If someone starts telling a story, redirect: "That sounds important. Add it to the Issues List and we'll IDS it."

## Section 5: To-Do List Review (5 Minutes)

### Purpose

Review every to-do from the previous week and confirm whether it is done or not done.

### Protocol

1. Display the to-do list from last week
2. Read each to-do. The owner states: "Done" or "Not done."
3. Done to-dos are checked off and removed
4. Not-done to-dos are either carried forward (one more week) or dropped to the Issues List
5. Total time: 5 minutes

### To-Do Rules

| Rule | Details |
|------|---------|
| 7-day items only | To-dos are completed within one week |
| 100% = done | Partial completion is "not done" |
| Each to-do has an owner | One name, no shared ownership |
| Target: 90%+ completion | If the team consistently falls below 90%, it is an issue |
| Carried forward once | If a to-do is not done two weeks in a row, it goes to IDS |

### What Makes a Good To-Do

- "Jordan: Send revised proposal to Acme Corp by Friday" (clear)
- "Look into marketing stuff" (too vague -- who? what? when?)

Every to-do must answer: Who will do what by when?

## Section 6: IDS -- The Core of the Meeting (60 Minutes)

### Purpose

Identify, Discuss, and Solve the most important issues facing the organization. This is where the real work of the Level 10 meeting happens.

### Protocol

**Step 1: Build the Issues List (2 minutes)**
- Ask: "Does anyone have new issues to add?"
- Quickly capture new issues in 3-5 words each

**Step 2: Prioritize (3 minutes)**
- Read the full list aloud
- Ask: "What are the top 3 issues? Which three, if solved today, would have the greatest impact?"
- Number them 1, 2, 3

**Step 3: IDS Issue #1**
- **Identify:** The person who raised the issue states it clearly in one sentence. Ask: "What is the real issue here?" Dig to root cause.
- **Discuss:** Open the floor. Relevant perspectives are shared. Facilitator stops tangents.
- **Solve:** The team decides. Action items are created with who/what/when. The issue is resolved or escalated.

**Step 4: Repeat for remaining issues**
- After each issue, re-prioritize remaining issues
- Continue until the 60 minutes are up
- Unsolved issues carry forward to next week

### Time Management During IDS

| Issue Complexity | Typical Time | Facilitator Action |
|-----------------|-------------|-------------------|
| Simple decision | 5 minutes | Drive quickly to a decision |
| Moderate discussion | 10-15 minutes | Allow input, then push for resolution |
| Complex strategic issue | 15-20 minutes | If not resolved in 20 minutes, create a to-do to schedule a separate meeting |
| Recurring issue | Varies | Address why it keeps recurring, not just the symptom |

### The Facilitator's Job During IDS

The facilitator (typically the Integrator) has specific responsibilities:

- **Keep the team on one issue at a time.** When someone introduces a tangent, say: "That's a separate issue. I'm adding it to the list."
- **Push past discussion to solving.** When the conversation is circling, say: "I think we have enough input. What's the decision?"
- **Draw out quiet voices.** Ask: "We haven't heard from you on this. What's your take?"
- **Break ties.** If the team cannot agree after sufficient discussion, the Integrator makes the call.
- **Capture action items in real time.** Every solved issue produces a to-do (who, what, when) or a decision.

## Section 7: Conclude (5 Minutes)

### Purpose

Wrap up the meeting with clarity on next steps and feedback on meeting quality.

### Protocol

**Step 1: Recap To-Dos (2 minutes)**
Read aloud every new to-do created during the meeting. Confirm each owner understands their commitment.

**Step 2: Cascading Messages (1 minute)**
Ask: "Are there any decisions or messages from this meeting that need to be communicated to your teams?" List them. Ensure consistent messaging.

**Step 3: Rate the Meeting (2 minutes)**
Each person rates the meeting 1-10. Go around the table.
- If the average is 8+: "Great meeting. See you next week."
- If any rating is below 8: Ask that person: "What would have made it an 8?" Take note for next week.

### Rating Criteria

| Rating | Meaning |
|--------|---------|
| 10 | Best possible use of 90 minutes. All important issues addressed. Clear outcomes. |
| 8-9 | Productive meeting. Most issues addressed. Minor improvements possible. |
| 6-7 | Decent but felt unfocused or rushed. Key issues may have been skipped. |
| 4-5 | Significant dysfunction. Too much tangent, not enough solving, or wrong issues prioritized. |
| 1-3 | Meeting failed. Waste of time. Fundamental problems with facilitation or participation. |

## How to Consistently Score 8+

### The Preparation Factor

Meetings score higher when people come prepared. Before every Level 10:

- [ ] Scorecard numbers are updated
- [ ] Rock statuses are current
- [ ] To-dos from last week are completed or flagged
- [ ] Issues to raise are thought through (not raised cold)

### The Facilitation Factor

| Technique | Impact |
|-----------|--------|
| Start on time, every time | Sets the standard for discipline |
| Enforce the agenda strictly | Prevents scope creep and overruns |
| Stop tangents immediately | Keeps IDS focused and productive |
| Push for decisions, not just discussion | Creates momentum and resolution |
| End on time, every time | Builds trust that 90 minutes means 90 minutes |

### The Participation Factor

- Every person speaks during IDS (facilitator draws out quiet members)
- No one dominates (facilitator manages airtime)
- People are honest about off-track rocks and red Scorecard numbers
- The team engages in healthy conflict, not avoidance

## Common Meeting Dysfunctions and Fixes

| Dysfunction | Symptom | Fix |
|-------------|---------|-----|
| **Tangent spiral** | Discussion jumps from issue to issue without solving any | Facilitator parks tangents: "Good point, adding to the list. Back to the current issue." |
| **One person dominates** | Same voice 70%+ of the time | Facilitator uses round-robin: "Let's hear from everyone. Sarah, you first." |
| **Avoid hard topics** | Elephants in the room are never raised | Facilitator names it: "I sense there's an issue we're avoiding. What is it?" |
| **Scorecard not updated** | Numbers missing or stale | Make it a to-do. If repeated, IDS it as a process issue. |
| **No one rates below 8** | Artificial harmony, no real feedback | Facilitator asks directly: "What specifically would improve this meeting?" |
| **To-dos always incomplete** | Same items carry forward week after week | IDS the pattern. Is it capacity? Commitment? Accountability? |
| **Rocks always on track until week 12** | People hide bad news until the last minute | Create safety for early off-track declarations. Praise honesty, not perfection. |
| **Meeting keeps running over 90 min** | Agenda discipline has broken down | Hard stop at 90 minutes. Unsolved issues carry forward. No exceptions. |
| **People check out during IDS** | Disengagement, phone checking | Remove devices. Facilitator actively engages: "What do you think about this?" |
| **Same issues every week** | IDS is not producing permanent solutions | When solving, ask: "What structural change will prevent this from recurring?" |

## Level 10 Meeting Checklist

**Before:** Room booked, Scorecard updated, Rock statuses current, to-dos from last week reviewed, issues identified, agenda displayed.

**During:** Segue (5 min), Scorecard (5 min), Rocks (5 min), Headlines (5 min), To-dos (5 min), IDS (60 min), Conclude with rating (5 min). New to-dos captured with who/what/when.

**After:** To-do list distributed within 1 hour. Cascading messages to teams within 24 hours. Below-8 ratings addressed before next meeting.

# People Component: Right People, Right Seats

The People Component is where most entrepreneurial companies struggle the hardest. Having the right people in the right seats is the single biggest factor in a company's ability to execute its vision. This guide covers the Accountability Chart, the Visionary/Integrator dynamic, the People Analyzer, GWC assessment, and practical frameworks for making difficult people decisions.

## The Accountability Chart

The Accountability Chart is not an org chart. An org chart shows hierarchy and reporting lines. An Accountability Chart shows the major functions of the business and who is accountable for each function's results.

### Why Not an Org Chart?

| Org Chart | Accountability Chart |
|-----------|---------------------|
| Shows who reports to whom | Shows who owns what outcomes |
| People-centric | Function-centric |
| Grows with headcount | Stays simple (5-7 major functions) |
| Can mask shared accountability | Enforces single-point accountability |

### Building the Accountability Chart

**Step 1: Start with the Three Major Functions**

Every business has three core functions, regardless of industry:

```
         Visionary ←→ Integrator
                        |
         ┌──────────────┼──────────────┐
         |              |              |
   Sales/Marketing  Operations     Finance
```

**Step 2: Define 3-5 Accountabilities per Function**

Each major function has specific outcomes it is responsible for. Write these as bullet points under each seat.

| Function | Key Accountabilities |
|----------|---------------------|
| **Sales/Marketing** | Revenue targets, lead generation, brand management, customer acquisition, sales process |
| **Operations** | Service/product delivery, quality assurance, project management, customer satisfaction, capacity planning |
| **Finance** | Financial reporting, cash flow management, budgeting, legal compliance, risk management |

**Step 3: Add Custom Functions if Needed**

Some companies need additional major functions:

- **Technology/Engineering** (for product companies)
- **People/HR** (for companies with 50+ employees)
- **Customer Success** (for subscription businesses)

**Step 4: Name the Seat, Then Fill It**

Design the Accountability Chart for the company you need, not the company you have. Determine the right structure first, then identify who should fill each seat. Sometimes one person holds multiple seats (common in smaller companies). That is fine as long as it is explicit.

### The One-Person-Per-Seat Rule

Every seat has exactly one accountable owner. Shared accountability is no accountability. If two people share a seat:
- Neither feels fully responsible
- Conflicts go unresolved
- Results suffer

When two people argue about who owns a function, the Integrator decides.

## Visionary vs. Integrator

The two most important seats in any EOS company are the Visionary and the Integrator. These roles are complementary and must work in partnership.

### Role Comparison

| Dimension | Visionary | Integrator |
|-----------|-----------|------------|
| **Focus** | Future, big picture | Present, details |
| **Strength** | Ideas, relationships, culture | Execution, accountability, alignment |
| **Energy** | Inspires and energizes | Organizes and stabilizes |
| **Meetings** | Often bored in operational meetings | Runs the Level 10 meeting |
| **Decisions** | Makes 10 decisions, 7 are great | Makes fewer decisions, all well-considered |
| **People** | Attracts talent | Develops and manages talent |
| **Conflict** | May avoid hard conversations | Resolves conflict directly |

### The Visionary's Five Roles

1. **Big ideas:** Generate new products, markets, and strategies
2. **Culture:** Set the tone, model core values
3. **Key relationships:** Manage top customers, partners, industry connections
4. **Creative problem solving:** Tackle the company's biggest challenges
5. **Selling:** Close major deals and evangelize the company

### The Integrator's Five Roles

1. **Run the business:** Manage day-to-day operations
2. **Lead the leadership team:** Facilitate meetings, hold leaders accountable
3. **Execute the V/TO:** Translate vision into quarterly and weekly action
4. **Resolve conflicts:** Break ties, mediate disputes, make hard calls
5. **Filter Visionary ideas:** Evaluate which ideas to pursue and which to shelve

### The Visionary-Integrator Relationship

**Healthy dynamics:**
- [ ] They meet weekly for a 30-60 minute "Same Page Meeting"
- [ ] The Visionary shares ideas freely; the Integrator evaluates and filters
- [ ] The Integrator has authority to run the business without daily Visionary approval
- [ ] Disagreements are resolved privately, not in front of the team
- [ ] Both publicly support each other's decisions

**Unhealthy dynamics:**
- The Visionary micromanages the Integrator
- The Integrator blocks all new ideas
- They contradict each other in team meetings
- Neither is willing to let the other lead in their domain

## The Five Major Seats

Below is a detailed breakdown of each major seat, including common sub-functions and what "great" looks like.

### 1. Sales/Marketing

**Purpose:** Generate revenue and build the brand.

| Sub-Function | Accountabilities |
|-------------|-----------------|
| Marketing | Lead generation, content, brand, campaigns, market research |
| Sales | Pipeline management, closing, account management, forecasting |
| Business Development | Partnerships, strategic accounts, new market entry |

### 2. Operations

**Purpose:** Deliver the product or service at the promised quality.

| Sub-Function | Accountabilities |
|-------------|-----------------|
| Delivery/Fulfillment | On-time delivery, quality standards, capacity planning |
| Project Management | Resource allocation, timeline management, scope control |
| Customer Service | Issue resolution, satisfaction metrics, retention |

### 3. Finance

**Purpose:** Manage the money and mitigate risk.

| Sub-Function | Accountabilities |
|-------------|-----------------|
| Accounting | Books, AP/AR, payroll, tax compliance |
| Financial Planning | Budgets, forecasting, cash flow management |
| Legal/Compliance | Contracts, regulatory compliance, risk assessment |

### 4-5. Custom Seats

Added based on your business model. Common additions:

- **Technology:** Product development, infrastructure, security, technical debt
- **People/HR:** Recruiting, onboarding, training, culture, performance management

## The People Analyzer

The People Analyzer is a simple tool that evaluates every employee on two dimensions: core values fit (Right Person) and role fit (Right Seat).

### Scoring Guide

**Step 1: Rate Core Values**

For each core value, score every team member:

| Symbol | Meaning | Description |
|--------|---------|-------------|
| **+** | Most of the time | Exhibits this value consistently (80%+) |
| **+/-** | Sometimes | Exhibits this value inconsistently (50-80%) |
| **-** | Rarely | Does not exhibit this value (<50%) |

**The Bar:** Everyone must be "+" on every core value. One "+/-" is a coaching conversation with a 90-day deadline to improve. Two "+/-" or any "-" means this is the wrong person.

### People Analyzer Template

| Name | Core Value 1 | Core Value 2 | Core Value 3 | Core Value 4 | GWC | Decision |
|------|-------------|-------------|-------------|-------------|-----|----------|
| Sarah | + | + | + | + | Y/Y/Y | Keep (A-player) |
| James | + | +/- | + | + | Y/Y/Y | Coach (90-day plan) |
| Priya | + | + | + | + | Y/N/Y | Move seat |
| Dave | - | +/- | + | + | Y/Y/Y | Exit |
| Lisa | + | + | + | + | Y/Y/N | Develop or move |

## GWC Assessment

GWC stands for Get it, Want it, Capacity to do it. All three must be "yes" for someone to be in the right seat.

### Get It

Does this person truly understand the role? Not just the tasks, but the nuances, the judgment calls, the unwritten rules. Someone who "gets it" can anticipate problems, see connections, and make decisions without being told.

**Diagnostic questions:**
- Can they explain the role's purpose in one sentence?
- Do they see the downstream impact of their decisions?
- Do they need constant direction, or do they figure things out?

### Want It

Does this person genuinely want this specific role? Not a paycheck. Not a title. This actual work, every day. People who "want it" show up with energy for the role, not just tolerance.

**Diagnostic questions:**
- Would they choose this role if money were not a factor?
- Do they light up when talking about their work?
- Are they making sacrifices willingly, or resentfully?

### Capacity to Do It

Does this person have the intellectual, physical, emotional, and time capacity to excel? Capacity is the hardest to change. Skills can be trained. Capacity is more fundamental.

**Diagnostic questions:**
- Can they handle the volume and complexity of the role?
- Do they have the emotional resilience the role requires?
- Are they already at capacity, or do they have room to grow into the role?

### GWC Decision Matrix

| G | W | C | Verdict | Action |
|---|---|---|---------|--------|
| Y | Y | Y | Right seat | Invest and retain |
| Y | Y | N | Capacity gap | Train, reduce scope, or move |
| Y | N | Y | Motivation issue | Have honest conversation, likely move seats |
| Y | N | N | Wrong seat entirely | Move to a different seat |
| N | Y | Y | Doesn't get it | Coach for 90 days, may not be fixable |
| N | Y | N | Square peg, round hole | Move seats |
| N | N | Y | Capable but wrong fit | Find the seat they get and want |
| N | N | N | Wrong seat | Move immediately |

## Right People, Right Seats Matrix

| | Right Seat | Wrong Seat |
|---|-----------|------------|
| **Right Person** | A-player. Protect, invest, promote. | Move to the right seat. They share your values -- find where they thrive. |
| **Wrong Person** | Hardest call. They produce results but damage culture. The answer is almost always exit. | Exit. No fit on either dimension. Delay makes it worse. |

### The Three-Strike Rule for Wrong Person/Right Seat

This is the most painful scenario. A top performer who violates core values:

1. **Strike 1:** Direct conversation. "Here is the core value you are violating, here is the specific behavior, here is what needs to change."
2. **Strike 2:** Written 30-day improvement plan with specific behavioral milestones.
3. **Strike 3:** Exit. The team is watching. Keeping a wrong person teaches everyone that core values are negotiable.

## Difficult Conversations Framework

### Preparing for the Conversation

- [ ] Write down the specific issue with concrete examples
- [ ] Identify which core value or GWC element is in question
- [ ] Choose a private setting with no interruptions
- [ ] Plan to listen more than talk (60/40 rule)
- [ ] Have a clear outcome in mind (coaching plan, role change, or exit)

### The Conversation Structure

1. **State the issue directly.** "I need to talk about [specific behavior/performance]. This is important for both of us."
2. **Give specific examples.** "On [date], [what happened]. Last week, [another example]."
3. **Connect to core values or GWC.** "This conflicts with our core value of [value]" or "I'm concerned about your capacity for [specific aspect]."
4. **Listen.** Ask: "What's your perspective?" Listen without interrupting.
5. **Agree on next steps.** "Here's what needs to change, by when, and how we'll measure it."
6. **Document.** Confirm the conversation and commitments in writing within 24 hours.

## Hiring for Core Values Fit

### Interview Process

**Step 1: Screen for core values first.** Before evaluating skills, assess whether the candidate aligns with each core value.

**Step 2: Use behavioral questions tied to each core value.**

| Core Value | Interview Question |
|-----------|-------------------|
| Own It | "Tell me about a time you made a mistake at work. What happened and what did you do?" |
| Do the Right Thing | "Describe a situation where you had to choose between what was easy and what was right." |
| Grow or Die | "What's the last skill you taught yourself? How did you go about it?" |

**Step 3: Back-channel references.** Ask references specifically about core values behaviors, not just competence.

**Step 4: Trial period.** The first 90 days are an extended interview. Evaluate core values fit at 30, 60, and 90 days.

## Quarterly Performance Conversations Template

Every quarter, each leader has a 30-minute conversation with each direct report covering four areas:

| Section | Time | Focus |
|---------|------|-------|
| Core Values Review | 10 min | Rate each value (+, +/-, -). Discuss any +/- with specific examples. Acknowledge strengths. |
| GWC Check | 10 min | Get it (clear on role?), Want it (still energized?), Capacity (right-sized workload?) |
| Rock Review | 5 min | On track / off track. What support is needed? |
| Forward Look | 5 min | Next quarter outlook, development goals, feedback for the leader |

### Documentation Template

```
Employee: ____________  Manager: ____________  Date: ____________
Core Values: [V1] +/+/-/-  [V2] +/+/-/-  [V3] +/+/-/-
GWC: G(Y/N) W(Y/N) C(Y/N)
Assessment: Right Person/Right Seat | Action Needed
Action Items: ____________  Next Review: ____________
```

# Process Component: Core Process Documentation

Most companies have processes. Few have them documented. Even fewer have them followed consistently. The Process Component fixes this by identifying your handful of core processes, documenting them simply, and ensuring they are followed by all. This guide covers the 20/80 rule, how to identify your core processes, documentation format, implementation through FBA (Followed By All), and department-specific examples.

## The 20/80 Rule

You do not need to document every procedure in your company. That leads to thousand-page manuals nobody reads. Instead, document the 20% of your processes that drive 80% of your results.

**What this means in practice:**
- Identify 5-7 core processes (not 50)
- Document each process in 5-20 major steps (not 200)
- Add just enough detail so someone competent can follow it (not a manual for someone with zero context)

### The Documentation Spectrum

| Too Little | Just Right | Too Much |
|-----------|------------|----------|
| "Handle customer complaints" | 8 steps from complaint received to resolution confirmed, with key decision points noted | 47-page complaint handling manual with scripts for every scenario |
| No one knows the process | New hires can follow it in their first week | No one reads the documentation |
| Inconsistent execution | 80%+ consistency across the team | Rigid process that cannot adapt |

## Identifying Your Core Processes

Every company, regardless of industry, has a set of core processes that define how the business runs. Most companies have 5-7 core processes.

### Common Core Processes

| Process | What It Covers | Who Owns It |
|---------|---------------|-------------|
| **HR Process** | Hiring, onboarding, performance reviews, offboarding | Head of People / Integrator |
| **Sales Process** | Lead qualification through close and handoff | Head of Sales |
| **Marketing Process** | Lead generation, nurturing, and conversion to sales-ready leads | Head of Marketing |
| **Operations/Delivery Process** | How you produce and deliver your product or service | Head of Operations |
| **Customer Retention Process** | Onboarding, support, renewals, upsells | Head of Customer Success |
| **Finance Process** | Invoicing, collections, reporting, budgeting | Head of Finance |
| **Product/Engineering Process** | Ideation, development, QA, deployment | Head of Product/Engineering |

### Discovery Exercise

Ask your leadership team:
1. "What are the major processes that run our business?"
2. "If a new leadership team took over tomorrow, what processes would they need to understand to run the company?"
3. "Where does inconsistency cause the most problems for customers or employees?"

List everything mentioned, then consolidate into 5-7 core processes. Each should span a meaningful arc of work (lead to close, not just "make a phone call").

## Process Documentation Format

Every core process follows the same documentation structure. Keep it simple. The goal is clarity, not comprehensiveness.

### Documentation Template

```
Process Name: _________________________ (give it a branded name)
Owner: _________________________
Last Updated: _________________________
Version: _________________________

Purpose: One sentence describing what this process achieves.

Steps:
1. [Step Name]
   - Key details or substeps
   - Decision point or criteria

2. [Step Name]
   - Key details or substeps

3. [Step Name]
   ...
```

### Naming Your Processes

Give each process a memorable, branded name. This makes it easier for the team to reference and creates a sense of identity around how you work.

**Examples:**
- Sales Process: "The Closer" or "The Revenue Engine"
- Onboarding Process: "The Welcome Track" or "First 30 Days"
- Support Process: "The Resolution Path" or "Care Loop"
- Delivery Process: "The Build Cycle" or "Ship It"

## Process Examples by Department

### Sales Process: "The Revenue Engine"

**Owner:** VP of Sales
**Purpose:** Convert qualified leads into paying customers through a consistent, repeatable process.

| Step | Action | Key Details | Exit Criteria |
|------|--------|-------------|--------------|
| 1 | **Qualify Lead** | Apply BANT criteria (Budget, Authority, Need, Timeline). Score 1-4. | Score of 3+ moves forward |
| 2 | **Discovery Call** | 30-minute structured call using question guide. Uncover 3 core pain points. | Pain points documented, next step agreed |
| 3 | **Demo** | Customized to prospect's pain points. Show, don't tell. 45 minutes max. | Prospect confirms fit |
| 4 | **Proposal** | Send within 24 hours of demo. Include 3 options (good/better/best). | Proposal delivered and receipt confirmed |
| 5 | **Follow Up** | 3 touches in 7 days: email (day 1), call (day 3), email (day 7). | Decision received |
| 6 | **Close** | Signed agreement and payment terms confirmed. | Contract signed |
| 7 | **Handoff** | Introduce customer to onboarding team. Complete handoff doc. | Onboarding team confirms receipt |

### Operations Process: "The Build Cycle"

**Owner:** VP of Operations
**Purpose:** Deliver projects on time, on budget, and at the quality standard promised.

| Step | Action | Key Details | Exit Criteria |
|------|--------|-------------|--------------|
| 1 | **Kickoff** | Internal kickoff within 48 hours of signed contract. Review scope, timeline, team. | All team members clear on deliverables |
| 2 | **Planning** | Create project plan with milestones. Identify risks. | Plan approved by project sponsor |
| 3 | **Execution** | Weekly status updates. Flag blockers within 24 hours. | Milestones met on schedule |
| 4 | **Quality Check** | Internal review before any deliverable goes to client. | Passes quality checklist |
| 5 | **Client Review** | Present deliverable. Collect feedback. | Client approval or revision list |
| 6 | **Revisions** | Address feedback within 3 business days. One round included. | Revisions approved |
| 7 | **Close Out** | Final delivery, documentation, lessons learned, satisfaction survey. | Survey score 4+/5 |

### HR Process: "The People Path"

**Owner:** Head of People / Integrator
**Purpose:** Attract, hire, develop, and retain people who are the right people in the right seats.

| Step | Action | Key Details | Exit Criteria |
|------|--------|-------------|--------------|
| 1 | **Job Definition** | Write Accountability Chart seat description with core values requirements. | Approved by hiring manager and Integrator |
| 2 | **Source** | Post on 3+ channels. Employee referral bonus active. | 10+ qualified applicants |
| 3 | **Screen** | Phone screen (15 min) for core values and basic qualifications. | 5 candidates advance |
| 4 | **Interview** | Two rounds: core values interview (behavioral), skills interview (technical). | 2-3 finalists |
| 5 | **People Analyzer** | Score each finalist on core values and GWC. | All "+" on values, all "Y" on GWC |
| 6 | **Offer** | Extend offer within 48 hours of final interview. | Offer accepted |
| 7 | **Onboard** | 90-day onboarding plan: Week 1 orientation, 30/60/90 check-ins. | 90-day review passed |
| 8 | **Develop** | Quarterly conversations using core values and GWC framework. | Ongoing |

### Customer Support Process: "The Care Loop"

**Owner:** Head of Customer Success
**Purpose:** Resolve customer issues quickly and use feedback to improve the product and service.

| Step | Action | Key Details | Exit Criteria |
|------|--------|-------------|--------------|
| 1 | **Receive** | Ticket created via email, chat, or phone. Auto-acknowledge within 1 hour. | Ticket logged in system |
| 2 | **Triage** | Classify severity (P1-P4). Assign to appropriate team member. | Assigned within 2 hours |
| 3 | **Investigate** | Reproduce the issue. Check knowledge base. Consult engineering if needed. | Root cause identified |
| 4 | **Resolve** | Implement fix or workaround. Communicate resolution to customer. | Customer confirms resolution |
| 5 | **Follow Up** | Check in 48 hours later. Confirm issue has not recurred. | Customer satisfied |
| 6 | **Document** | Update knowledge base if new issue type. Flag product bugs for engineering. | KB updated |
| 7 | **Report** | Weekly metrics: volume, resolution time, CSAT, recurring issues. | Scorecard updated |

### Finance Process: "The Money Flow"

**Owner:** Head of Finance / Controller
**Purpose:** Manage the company's financial health through timely invoicing, accurate reporting, and proactive cash management.

| Step | Action | Key Details | Exit Criteria |
|------|--------|-------------|--------------|
| 1 | **Invoice** | Generate invoice within 24 hours of deliverable/milestone. | Invoice sent and confirmed |
| 2 | **Track** | Monitor payment status weekly. Flag AR over 30 days. | AR report updated |
| 3 | **Collect** | Follow up on overdue invoices: email at 31 days, call at 45 days, escalate at 60 days. | Payment received or escalated |
| 4 | **Report** | Weekly flash report (revenue, expenses, cash). Monthly P&L. | Reports delivered on schedule |
| 5 | **Forecast** | Quarterly cash flow forecast. Annual budget review. | Forecast approved by leadership |

## FBA: Followed By All

Documented processes are worthless if nobody follows them. FBA (Followed By All) is the implementation framework that turns documentation into habit.

### The FBA Cycle

```
Document → Train → Measure → Update → Repeat
```

**Step 1: Document** (covered above)

**Step 2: Train**
- Every employee involved in a process receives training on the documented steps
- Training is not a 2-hour lecture. It is hands-on practice with feedback.
- New hires are trained on relevant processes in their first two weeks

**Step 3: Measure**
- Spot-check compliance monthly (review 5-10 random instances of the process)
- Track process-related quality metrics on the Scorecard
- Ask: "Is the process being followed? If not, why?"

**Step 4: Update**
- Processes should be reviewed quarterly
- If the team consistently deviates from a step, either enforce it or update it
- The person who owns the process owns the updates

### FBA Compliance Checklist

| Question | Yes/No | Action if No |
|----------|--------|-------------|
| Is the process documented and accessible? | | Write/share it |
| Has everyone been trained on it? | | Schedule training |
| Are we measuring compliance? | | Add spot-checks |
| Is the process producing consistent results? | | Identify which step is failing |
| Has it been reviewed in the past quarter? | | Schedule review |

## Visual Process Documentation Tips

Processes are easier to follow when they are visual. Use these approaches:

### Flowchart Format

```
[Lead Received] → [Qualify (BANT)] → Score 3+?
                                       ├── Yes → [Discovery Call]
                                       └── No  → [Nurture Sequence]
```

### Swimlane Format

Use swimlanes when multiple people or departments are involved:

| Marketing | Sales | Operations |
|-----------|-------|------------|
| Generate lead | | |
| Qualify MQL | | |
| | Accept SQL | |
| | Discovery call | |
| | Close deal | |
| | | Kick off project |
| | | Deliver |

### Checklist Format

For processes with many parallel tasks (like onboarding), a checklist works better than a flowchart:

**New Employee Onboarding Checklist**
- [ ] Equipment ordered (IT, day -7)
- [ ] Accounts created (IT, day -3)
- [ ] Welcome email sent (HR, day -1)
- [ ] Office tour (Manager, day 1)
- [ ] Core values training (HR, day 1)
- [ ] Process training begins (Manager, day 2)
- [ ] 30-day check-in scheduled (Manager, day 1)

## Training New Employees on Processes

### The See-Do-Teach Method

1. **See:** New hire observes an experienced team member performing the process
2. **Do:** New hire performs the process with the experienced team member coaching
3. **Teach:** New hire explains the process back to someone else

If they can teach it, they know it. This method works for any process in any department.

### Training Schedule Template

| Week | Focus | Method | Assessment |
|------|-------|--------|------------|
| 1 | Company overview, core values, core processes overview | Orientation sessions | Can state core values and name all core processes |
| 2 | Primary process (the one they will use daily) | See-Do-Teach | Completes process independently with <2 errors |
| 3 | Secondary processes (ones they interact with) | See + documentation review | Can explain how their work connects to upstream/downstream processes |
| 4 | Edge cases and exceptions | Scenario-based practice | Handles 3 of 4 edge case scenarios correctly |

## Quarterly Process Review Cadence

Every quarter, each process owner reviews their core process:

### Review Agenda (30 minutes per process)

1. **Compliance check (10 min):** Are people following the process? Where are the deviations?
2. **Results check (10 min):** Is the process producing the desired outcomes? What do the Scorecard metrics say?
3. **Improvement check (10 min):** What feedback have we received? What steps should be added, removed, or changed?

### Process Health Scorecard

| Process | Compliance Rate | Outcome Quality | Last Updated | Status |
|---------|---------------|-----------------|-------------|--------|
| The Revenue Engine | 85% | Win rate 28% | Jan 15 | Healthy |
| The Build Cycle | 70% | On-time 82% | Dec 1 | Needs attention |
| The People Path | 90% | 90-day retention 95% | Jan 20 | Healthy |
| The Care Loop | 60% | CSAT 3.8/5 | Oct 15 | At risk |
| The Money Flow | 95% | AR <30 days 92% | Jan 10 | Healthy |

Any process below 80% compliance or with declining outcome quality goes to the Issues List for IDS.

# Rocks: Quarterly Priority-Setting Guide

Rocks are the 3-7 most important priorities for the next 90 days. They are the bridge between your annual plan and daily execution. Without rocks, teams default to urgency-driven work, reacting to whatever is loudest instead of progressing toward what matters most. This guide covers the complete rock-setting process, SMART criteria, facilitation, tracking, common mistakes, and the cascade from company to individual.

## Why 90 Days

The 90-day cycle is the heartbeat of EOS. It works because of human psychology and business reality:

- **Long enough** to accomplish something meaningful (launch a product, hire a key role, build a process)
- **Short enough** to maintain urgency (the deadline is always visible)
- **Natural rhythm** that aligns with quarterly business cycles
- **Frequent reset** that prevents stale priorities and allows course correction

Research on goal-setting consistently shows that shorter time horizons with clear deadlines produce higher completion rates than annual goals.

## SMART Rocks

Every rock must pass the SMART test. If it fails any criterion, rewrite it before committing.

### The Five Criteria

| Criterion | Question | Bad Example | Good Example |
|-----------|----------|-------------|-------------|
| **Specific** | What exactly will be accomplished? | "Improve marketing" | "Launch LinkedIn content program with 3 posts per week" |
| **Measurable** | How will you know it is done? | "Get more leads" | "Generate 200 MQLs from LinkedIn by end of quarter" |
| **Achievable** | Can it be done in 90 days? | "Build and launch a new product line" | "Complete MVP and run beta with 10 customers" |
| **Realistic** | Given current resources and constraints? | "Double revenue" (from $5M to $10M in one quarter) | "Increase revenue 15% through upsell program" |
| **Time-bound** | Clear deadline? | "Sometime this quarter" | "Complete by March 31" |

### The Binary Test

A rock is either done or not done at the end of the quarter. No partial credit. No percentages. This binary nature forces clarity in how the rock is written.

**Ask:** "On the last day of the quarter, could someone who is not on my team look at this rock and definitively say it is done or not done?" If the answer is no, rewrite it.

## Company Rocks vs. Individual Rocks

### Company Rocks

Company rocks are the 3-7 most important priorities for the entire organization. They are set by the leadership team and represent the strategic priorities that will move the company toward its 1-Year Plan and 3-Year Picture.

**Characteristics:**
- Owned by one leadership team member (but may involve cross-functional effort)
- Directly tied to 1-Year Plan goals
- Visible to the entire organization
- Reviewed weekly in the Level 10 meeting

### Individual Rocks

Each leadership team member also has 3-7 personal rocks. These include:
- Their company rock(s) if they own any
- Department-specific priorities
- Personal development goals (if applicable)

**The total should not exceed 7.** If someone owns 2 company rocks and has 5 individual rocks, they have 7 total. That is the maximum.

### Rock Cascade: Company to Department to Individual

```
COMPANY ROCKS (3-7)
  Set by leadership team
  Example: "Launch customer success program"
      ↓
DEPARTMENT ROCKS (3-7 per department)
  Set by department head, aligned to company rocks
  Example: "Hire 2 customer success managers and onboard them"
      ↓
INDIVIDUAL ROCKS (3-7 per person)
  Set by individual with manager, aligned to department rocks
  Example: "Complete CS manager interview process and extend 2 offers by March 15"
```

Each level should clearly support the level above it. If an individual rock does not connect to a department or company rock, question whether it belongs.

## Rock-Setting Session Facilitation

### Pre-Session Preparation

- [ ] Schedule 2 hours for the leadership team (off-site or distraction-free)
- [ ] Distribute the current V/TO, especially the 1-Year Plan and previous quarter's rocks
- [ ] Ask each leader to come with 5-10 potential rock ideas
- [ ] Review previous quarter's rock completion (what got done, what did not)
- [ ] Prepare a whiteboard or shared digital space for brainstorming

### 2-Hour Rock-Setting Agenda

| Time | Activity | Details |
|------|----------|---------|
| 0:00-0:15 | **Review V/TO** | Re-read the 1-Year Plan goals. Remind everyone what the company is working toward. |
| 0:15-0:30 | **Review Last Quarter** | Score each rock: Done or Not Done. Discuss what worked and what did not. Calculate completion rate. |
| 0:30-1:00 | **Brainstorm** | Each leader shares their rock ideas. Write all ideas on the board. No editing yet. Aim for 15-25 ideas. |
| 1:00-1:30 | **Narrow and Prioritize** | Group similar ideas. Eliminate duplicates. Vote on the top 7. Each leader gets 5 votes (dot voting). |
| 1:30-1:50 | **SMART Check** | For each selected rock, apply the SMART criteria. Rewrite until each rock passes the binary test. |
| 1:50-2:00 | **Assign Owners** | One owner per rock. Confirm capacity. Ensure no one has more than 7 total rocks. |

### Facilitation Tips

- **The Integrator facilitates.** They keep the session moving and break ties.
- **Visionary contributes ideas but does not dominate.** Their voice carries weight, so the facilitator must actively draw out others.
- **Force trade-offs.** If the team wants 10 rocks, ask: "Which 3 would you drop?" This is more productive than arguing for additions.
- **Avoid business-as-usual rocks.** If it would happen anyway without being a rock, it is not a rock. Rocks are the extras -- the initiatives that move the needle.

## Rock Examples by Department and Company Stage

### Early Stage ($1M-$5M revenue, 10-30 employees)

| Department | Rock Example |
|-----------|-------------|
| Sales | Close 3 enterprise accounts at $50K+ ACV each |
| Marketing | Launch content marketing engine: blog + newsletter + LinkedIn (3x/week) |
| Product | Ship v2.0 with top 5 customer-requested features |
| Operations | Document and train team on 3 core processes |
| Finance | Implement monthly financial reporting package |
| People | Hire VP of Sales and complete 90-day onboarding |

### Growth Stage ($5M-$20M revenue, 30-100 employees)

| Department | Rock Example |
|-----------|-------------|
| Sales | Build and launch partner channel generating 20% of pipeline |
| Marketing | Achieve 500 MQLs/month through paid and organic channels |
| Product | Launch self-serve onboarding reducing implementation time by 60% |
| Operations | Achieve 95% on-time delivery rate (currently 82%) |
| Finance | Complete Series A preparation: data room, financial model, pitch deck |
| People | Implement quarterly performance conversation process for all managers |

### Scale Stage ($20M-$50M revenue, 100-250 employees)

| Department | Rock Example |
|-----------|-------------|
| Sales | Open Southeast region: hire regional manager, 3 reps, achieve $500K pipeline |
| Marketing | Launch account-based marketing program targeting top 50 enterprise prospects |
| Product | Complete platform migration to new infrastructure (Phase 1 of 3) |
| Operations | Implement quality management system achieving ISO 9001 readiness |
| Finance | Deploy new ERP system and migrate all financial data |
| People | Launch leadership development program for 15 emerging leaders |

## Rock Tracking: Weekly Review Process

Rocks are reviewed every week in the Level 10 meeting. The review takes 5 minutes and follows a simple protocol.

### Weekly Rock Review Protocol

1. **Display the rock sheet** showing all company and individual rocks
2. **Go person by person.** Each leader states each rock and one word: "On track" or "Off track."
3. **No discussion during review.** Off-track rocks are noted.
4. **Off-track rocks drop to Issues List.** They will be IDS'd during the 60-minute IDS portion of the meeting.
5. **Total time: 5 minutes.** This is a status scan, not a progress report.

### Rock Tracking Template

| Rock | Owner | Status W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 | W9 | W10 | W11 | W12 | W13 | Done? |
|------|-------|-----------|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-------|
| Launch partner channel | Sarah | On | On | On | Off | On | On | On | On | On | On | On | On | On | Yes |
| Hire VP Sales | James | On | On | Off | Off | On | On | On | On | On | On | On | On | On | Yes |
| Ship v2.0 | Priya | On | On | On | On | On | On | Off | Off | Off | On | On | On | On | No |

## The 80% Completion Rate Target

The goal is to complete 80% or more of rocks each quarter. This is a team metric, not an individual one.

### What the Completion Rate Tells You

| Rate | Interpretation | Action |
|------|---------------|--------|
| **90-100%** | Rocks may be too easy | Set more ambitious rocks next quarter |
| **80-89%** | Healthy execution | Maintain the bar and celebrate |
| **60-79%** | Execution issues | IDS the root causes: too many rocks? Wrong rocks? Resource constraints? |
| **Below 60%** | Systemic problem | Leadership team needs to address fundamental issues: capacity, commitment, or rock quality |

### Improving Completion Rate

If the rate is below 80%, diagnose the problem:

- [ ] Were rocks written clearly (SMART)? If not, improve rock-writing discipline
- [ ] Were there too many rocks? If yes, reduce to 3-5 next quarter
- [ ] Did priorities shift mid-quarter? If yes, the team needs better discipline around saying no to new priorities
- [ ] Did one person miss all their rocks? If yes, it is a people issue (capacity or commitment)
- [ ] Did the whole team miss? If yes, it may be an organizational capacity issue

## Common Rock Mistakes

| Mistake | Why It Fails | Fix |
|---------|-------------|-----|
| **Too many rocks (>7)** | Diluted focus, everything moves slowly | Force the team to choose. Fewer rocks, more done. |
| **Too vague** | Cannot tell if it is done at quarter end | Apply the binary test. Rewrite until it passes. |
| **Business-as-usual** | Not moving the needle, would happen anyway | Ask: "Would this happen even if it were not a rock?" If yes, it is not a rock. |
| **No owner** | Shared accountability is no accountability | One name per rock. Period. |
| **Rock is really a to-do** | Too small for a 90-day priority | If it can be done in a week, put it on the to-do list, not the rock sheet. |
| **Rock is really a goal** | "Increase revenue 20%" is a goal, not a project | Rewrite as the project that achieves the goal: "Launch upsell program targeting top 50 accounts" |
| **Changing rocks mid-quarter** | Destroys the 90-day discipline | Rocks are locked once set. New urgent items become to-dos or wait for next quarter. |
| **Not tracking weekly** | Out of sight, out of mind | Review every rock in every Level 10 meeting |
| **No consequences for missed rocks** | Team learns that rocks are optional | IDS missed rocks. Identify why. Address the pattern. |

## Mid-Quarter Rock Check-In

At the halfway point of each quarter (around week 6-7), conduct a focused rock check-in:

### Mid-Quarter Check-In Agenda (30 minutes)

1. **Status review (10 min):** Each owner rates their rocks as on track, at risk, or off track
2. **At-risk rocks (15 min):** For each at-risk rock, discuss:
   - What is blocking progress?
   - What support is needed?
   - Is the rock still achievable by end of quarter?
   - If not, should we adjust scope or accept the miss?
3. **Commitments (5 min):** Each person states what they will do in the next 6 weeks to complete their rocks

### Mid-Quarter Decision Tree

```
Rock status at mid-quarter:
├── On track → Continue, no action needed
├── At risk → IDS the obstacle, get support, recommit
└── Off track → Three options:
    ├── 1. Recommit with adjusted approach (still achievable)
    ├── 2. Reduce scope to core deliverable (partial but meaningful)
    └── 3. Accept the miss and learn from it (do not carry forward automatically)
```

**Important:** Do not add new rocks mid-quarter. The 90-day discipline requires that priorities stay locked. If something truly urgent arises, it becomes a to-do, not a rock.

## Rock-Setting Worksheet

Use this worksheet for each rock before finalizing:

```
Rock Statement: ________________________________

SMART Check:
  [ ] Specific: Exactly what will be accomplished?
  [ ] Measurable: How will completion be verified?
  [ ] Achievable: Can it be done in 90 days?
  [ ] Realistic: Given current resources?
  [ ] Time-bound: Due by end of quarter?

Binary Test: On April 1, can someone definitively say this is DONE or NOT DONE?
  [ ] Yes → Rock is ready
  [ ] No → Rewrite

Owner: ________________________________
Supports which 1-Year Goal: ________________________________
Key milestones:
  Week 4: ________________________________
  Week 8: ________________________________
  Week 13: ________________________________
```

# Vision/Traction Organizer (V/TO) Complete Guide

The Vision/Traction Organizer is the single most important document in EOS. It captures your company's vision on two pages by answering eight critical questions. When the leadership team is aligned on the V/TO, every decision becomes clearer, every hire becomes easier, and every meeting becomes more productive. This guide walks through each question with exercises, templates, and facilitation tips.


## Table of Contents
1. [The Eight Questions](#the-eight-questions)
2. [Question 1: Core Values](#question-1-core-values)
3. [Question 2: Core Focus](#question-2-core-focus)
4. [Question 3: 10-Year Target](#question-3-10-year-target)
5. [Question 4: Marketing Strategy](#question-4-marketing-strategy)
6. [Question 5: 3-Year Picture](#question-5-3-year-picture)
7. [Question 6: 1-Year Plan](#question-6-1-year-plan)
8. [Question 7: Quarterly Rocks](#question-7-quarterly-rocks)
9. [Question 8: Issues List](#question-8-issues-list)
10. [Complete V/TO Template](#complete-vto-template)
11. [Filled-In V/TO Example: CloudSync (B2B SaaS, $4M ARR)](#filled-in-vto-example-cloudsync-b2b-saas-4m-arr)
12. [Facilitation Tips for V/TO Sessions](#facilitation-tips-for-vto-sessions)

---

## The Eight Questions

The V/TO is divided into two pages: the Vision side (questions 1-4) and the Traction side (questions 5-8). Vision defines where you are going. Traction defines how you will get there.

| Page | Questions | Purpose |
|------|-----------|---------|
| **Vision** | Core Values, Core Focus, 10-Year Target, Marketing Strategy | Long-term identity and direction |
| **Traction** | 3-Year Picture, 1-Year Plan, Quarterly Rocks, Issues List | Near-term execution and priorities |

## Question 1: Core Values

Core values are the defining characteristics of your organization. They are not aspirational slogans posted on a wall. They describe who you truly are at your best.

### Core Values Discovery Exercise

**Step 1: Generate a List (50+ Values)**

Have each leadership team member independently list the qualities they admire most in their best employees, past and present. Think about:
- What made that person exceptional?
- What traits do they share with other top performers?
- What behaviors do you celebrate and reward?

Combine all lists. You should have 40-60 qualities.

**Step 2: Group and Consolidate (15-20 Themes)**

Cluster similar values together. "Integrity," "honesty," and "transparency" might become one theme. Give each cluster a working label.

**Step 3: Debate and Narrow (3-7 Final Values)**

For each candidate value, ask:
- Is this truly a core value, or is it something we wish we were?
- Would we fire a high performer who consistently violated this value?
- Would we keep someone who embodies this value even if they underperformed for a quarter?
- Does this value differentiate us from competitors?

**Step 4: Define Each Value**

Write 2-3 bullet points under each value that describe observable behaviors.

| Core Value | Behavioral Indicators |
|-----------|----------------------|
| **Own It** | Takes responsibility without being asked. Admits mistakes quickly. Follows through on every commitment. |
| **Do the Right Thing** | Tells the truth even when it hurts. Puts the customer first. Makes ethical choices under pressure. |
| **Grow or Die** | Seeks feedback actively. Reads, learns, and improves quarterly. Embraces uncomfortable challenges. |

**Common Mistakes:**
- Too many values (more than 7 become impossible to remember)
- Aspirational values instead of actual values
- Generic values that could apply to any company ("excellence," "teamwork")
- Not using values in hiring, firing, and review decisions

## Question 2: Core Focus

Core Focus has two parts: your purpose/cause/passion and your niche. Together, they define what you are best at and why you exist.

### Finding Your Purpose/Cause/Passion

Ask the leadership team:
- Why does this company exist beyond making money?
- What would the world lose if we disappeared?
- What gets us out of bed on the hardest days?

This is not a mission statement. It is one sentence that captures your reason for being.

**Examples:**
- "To simplify small business." (Accounting SaaS)
- "To transform how people learn." (EdTech company)
- "To build things that matter." (Engineering firm)

### Finding Your Niche

Your niche is what you do better than anyone else. Ask:
- What can we be the best in the world at?
- Where do we consistently win against competitors?
- What do customers say is uniquely valuable about us?

**Examples:**
- "Cloud accounting for small businesses" (Niche within accounting)
- "Mobile-first corporate training" (Niche within EdTech)
- "Complex structural engineering in seismic zones" (Niche within engineering)

### Core Focus Template

```
Purpose/Cause/Passion: ________________________________
Niche: ________________________________
```

**Filter test:** Every new opportunity, product, or hire should pass through your Core Focus. If it doesn't align, say no.

## Question 3: 10-Year Target

The 10-Year Target is your Big, Hairy, Audacious Goal (BHAG). It should be specific enough to measure, bold enough to inspire, and clear enough that anyone in the company can understand it.

### BHAG Setting Process

**Step 1:** Have each leadership team member write their version independently.

**Step 2:** Share and discuss. Look for common themes.

**Step 3:** Agree on one target. It should:
- Be a single, clear number or milestone
- Feel achievable but ambitious (60-70% confidence)
- Be measurable with no ambiguity
- Create energy when stated out loud

**Examples by Company Type:**

| Company Type | 10-Year Target |
|-------------|---------------|
| SaaS Startup | $100M ARR |
| Professional Services | 500 employees across 10 offices |
| Manufacturing | Largest custom metal fabricator east of the Mississippi |
| Agency | Serve 1,000 brands generating $1B+ combined revenue |
| Healthcare | 50 clinics across 5 states |

**Common Mistakes:**
- Making it too easy (not inspiring)
- Making it too vague ("be the best")
- Having multiple targets (pick one)
- Changing it every year (it should be stable for a decade)

## Question 4: Marketing Strategy

The Marketing Strategy has four parts that define how you attract and win customers.

### Part A: Target Market

Define your ideal customer with precision:
- **Demographics:** Industry, size, revenue, location, title of buyer
- **Psychographics:** Attitudes, values, pain points, buying behavior
- **The List:** Name 10-20 companies that perfectly represent your target market

### Part B: Three Uniques

List three things that, taken together, differentiate you from every competitor. Each unique alone may not be distinctive. The combination must be.

| Company | Unique 1 | Unique 2 | Unique 3 |
|---------|----------|----------|----------|
| Accounting SaaS | Built for non-accountants | Same-day phone support | Automated tax prep |
| Engineering Firm | Seismic specialists | 48-hour turnaround quotes | In-house 3D modeling |
| Marketing Agency | Only B2B SaaS | Performance guarantees | Dedicated strategist |

### Part C: Proven Process

Name and visualize the steps a customer takes from first contact to long-term relationship. Give it a branded name.

**Example: "The Clarity Path"**
1. Discovery Call (30 min)
2. Strategic Assessment (delivered in 5 days)
3. Proposal and Agreement
4. Onboarding Sprint (first 30 days)
5. Quarterly Business Reviews
6. Annual Strategy Reset

### Part D: Guarantee

What promise can you make that removes risk for the buyer?

**Examples:**
- "Your first month free if you don't see ROI by day 30."
- "We'll redo any deliverable you're not satisfied with, no questions asked."
- "100% money-back guarantee for the first 90 days."

## Question 5: 3-Year Picture

Paint a vivid picture of what the company looks like in three years. Be specific enough that everyone can visualize it.

### 3-Year Picture Template

```
Date: ____________ (3 years from today)

Revenue: $____________
Profit: $____________ (______%)
Headcount: ____________
Number of Customers/Clients: ____________
Key Measurables:
  - ________________________________
  - ________________________________
  - ________________________________

What does the company look like?
  - ________________________________
  - ________________________________
  - ________________________________
  - ________________________________
  - ________________________________
```

**Example:** "By Dec 31, 2028: $15M revenue, $2.25M profit (15%), 85 people, 600 active accounts. Regional leader in 3 metros, two $5M+ product lines, NPS above 60, leadership team of 6 A-players, Best Places to Work recognition."

## Question 6: 1-Year Plan

The 1-Year Plan makes the 3-Year Picture actionable with specific targets for the next twelve months.

### 1-Year Plan Template

```
Date: ____________ (1 year from today)

Revenue: $____________
Profit: $____________ (______%)

Goals (3-7):
1. ________________________________
2. ________________________________
3. ________________________________
4. ________________________________
5. ________________________________

Budget: ________________________________
```

Every goal should be specific and measurable. "Improve marketing" is not a goal. "Generate 500 qualified leads per month by Q4" is a goal.

## Question 7: Quarterly Rocks

Rocks are the 3-7 most important priorities for the next 90 days. They bridge the gap between the 1-Year Plan and daily execution.

### Rock Integration with V/TO

Rocks should directly support 1-Year Plan goals. If a rock doesn't connect to a goal, question whether it belongs.

| 1-Year Goal | Q1 Rock | Q2 Rock |
|------------|---------|---------|
| Generate 500 leads/month | Launch new website and SEO strategy | Hire content marketing specialist |
| Reach $8M revenue | Close 3 enterprise deals | Launch upsell program for existing accounts |
| Build leadership team | Hire VP of Operations | Complete 90-day onboarding for all new leaders |

## Question 8: Issues List

The Issues List captures everything standing in the way of achieving your vision. It includes problems, ideas, and obstacles at the company level.

**Long-term issues** are strategic and may take quarters to resolve. **Short-term issues** are tactical and should be solved in the next Level 10 meeting.

## Complete V/TO Template

```
PAGE 1: VISION
  Core Values: 1.______ 2.______ 3.______ 4.______ 5.______
  Core Focus — Purpose: ________________ Niche: ________________
  10-Year Target: ________________
  Marketing Strategy — Target: ________________
    Three Uniques: 1.______ 2.______ 3.______
    Proven Process: ________________  Guarantee: ________________

PAGE 2: TRACTION
  3-Year Picture — Date:____ Revenue:$____ Profit:$____ Headcount:____
    What it looks like: ________________
  1-Year Plan — Date:____ Revenue:$____ Profit:$____
    Goals: 1.______ 2.______ 3.______ 4.______ 5.______
  Quarterly Rocks: 1.______(Owner) 2.______(Owner) 3.______(Owner)
    4.______(Owner) 5.______(Owner) 6.______(Owner) 7.______(Owner)
  Issues List: 1.______ 2.______ 3.______ 4.______ 5.______
```

## Filled-In V/TO Example: CloudSync (B2B SaaS, $4M ARR)

```
PAGE 1: VISION
  Core Values: 1. Own It  2. Radically Transparent  3. Ship Fast  4. Customers First  5. Stay Curious
  Core Focus — Purpose: To eliminate data silos for growing companies  Niche: Real-time data sync for mid-market SaaS
  10-Year Target: $100M ARR with 3,000 customers
  Marketing Strategy — Target: B2B SaaS companies, 50-500 employees, $5M-$50M revenue, VP Eng / CTO buyer
    Three Uniques: 1. Zero-downtime migrations  2. Sub-second sync latency  3. White-glove onboarding
    Proven Process: "The Sync Path" (Discovery → Audit → Migration → Go-Live → QBR)
    Guarantee: Full refund if data sync is not live within 30 days

PAGE 2: TRACTION
  3-Year Picture — Date: Dec 31, 2028  Revenue: $15M  Profit: $2.25M (15%)  Headcount: 85
    What it looks like: Regional leader in 3 metros, NPS 65+, 600 active accounts, two product lines above $5M, Best Places to Work
  1-Year Plan — Date: Dec 31, 2026  Revenue: $6.5M  Profit: $650K (10%)
    Goals: 1. 200 active accounts  2. Launch enterprise tier  3. Hire VP Sales  4. Achieve SOC 2 Type II  5. 95% gross retention
  Quarterly Rocks: 1. Close 15 new accounts (CRO)  2. Ship enterprise SSO (VP Eng)  3. Hire 3 SDRs (VP Sales)
    4. Launch partner program (CEO)  5. Reduce onboarding time to 14 days (CS Lead)  6. Publish SOC 2 report (CTO)
  Issues List: 1. Churn in SMB segment  2. Competitor launched free tier  3. Need senior backend engineer
    4. Support ticket volume growing 20% MoM  5. Pricing model under pressure from enterprise prospects
```

## Facilitation Tips for V/TO Sessions

### Before the Session

- [ ] Book a two-day off-site away from the office
- [ ] Send pre-work: each leader writes their answers to all eight questions independently
- [ ] Assign a facilitator (either an EOS Implementer or the Integrator)
- [ ] Set ground rules: phones off, laptops closed, all voices heard
- [ ] Prepare a large whiteboard or flip charts

### During the Session

- [ ] Spend Day 1 on Vision (questions 1-4), Day 2 on Traction (questions 5-8)
- [ ] Allow healthy debate but enforce time limits per question
- [ ] Use the "fist to five" technique for consensus (0 = strongly disagree, 5 = fully support)
- [ ] If the team cannot agree after 20 minutes, the Integrator makes the call
- [ ] Record every decision immediately on the V/TO document

### After the Session

- [ ] Clean up the V/TO within 48 hours and distribute to the leadership team
- [ ] Schedule a company-wide meeting to share the V/TO within 30 days
- [ ] Review the V/TO at every quarterly session
- [ ] Update it formally at the annual planning session
- [ ] Post it visibly in the office (or pin it in a shared digital workspace)

### Common Facilitation Pitfalls

| Pitfall | What Happens | How to Fix |
|---------|-------------|------------|
| Visionary dominates | Team agrees to avoid conflict | Facilitator calls on each person directly |
| Analysis paralysis | No decisions made | Time-box each question, Integrator breaks ties |
| Too abstract | V/TO reads like a philosophy paper | Force specific numbers and dates for every section |
| Rushed process | Leadership doesn't internalize | Spend the full two days, no shortcuts |
| No follow-through | V/TO sits in a drawer | Review quarterly, reference in every Level 10 meeting |