company-os

---
name: company-os
description: Use when setting up company operations, selecting a management framework (EOS, Scaling Up, OKRs), designing meeting rhythms, building accountability systems, or running quarterly rock planning.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# Company Operating System

The operating system is the collection of tools, rhythms, and agreements that determine how the company functions. Every company has one — most just don't know what it is. Making it explicit makes it improvable.

## Keywords
operating system, EOS, Entrepreneurial Operating System, Scaling Up, Rockefeller Habits, OKR, Holacracy, L10 meeting, rocks, scorecard, accountability chart, issues list, IDS, meeting pulse, quarterly planning, weekly scorecard, management framework, company rhythm, traction, Gino Wickman, Verne Harnish

## Why This Matters
Most operational dysfunction isn't a people problem — it's a system problem. Recurring weekly issues signal no issue resolution system. Pointless meetings signal no structured meeting pulse. Nobody knowing who owns what signals no accountability chart. Slipping quarterly goals signal rocks that aren't real commitments. Fix the system; the people will operate better inside it.

## The Six Core Components

### 1. Accountability Chart
Not an org chart — it answers "who owns this outcome?" One person owns each function; multiple people may work in it, but ownership means the buck stops with one person.

```
CEO
├── Sales (CRO/VP Sales)
│   ├── Inbound pipeline
│   └── Outbound pipeline
├── Product & Engineering (CTO/CPO)
│   ├── Product roadmap
│   └── Engineering delivery
├── Operations (COO)
│   ├── Customer success
│   └── Finance & Legal
└── People (CHRO/VP People)
    ├── Recruiting
    └── People operations
```

**Rules:** no shared ownership ("Alice and Bob both own it" means nobody owns it); one person can hold multiple seats early on, just be explicit; revisit quarterly as the company scales.

**Build it in a workshop:** list every function the company performs, assign one owner per function with no exceptions, identify gaps and overlaps, publish and keep updated.

### 2. Scorecard
Weekly metrics that tell you if the company is on track — not monthly, not quarterly.

**Rules:** 5–15 metrics maximum (more than 15 and nothing gets attention); each metric has an owner and a specific weekly target, not a range; red/yellow/green status, not paragraphs; discussed at the weekly leadership meeting, and only red metrics get discussion time.

**Example scorecard:**

| Metric | Owner | Target | This Week | Status |
|--------|-------|--------|-----------|--------|
| New MRR | CRO | €50K | €43K | 🔴 |
| Churn | CS Lead | < 1% | 0.8% | 🟢 |
| Active users | CPO | 2,000 | 2,150 | 🟢 |
| Deployments | CTO | 3/week | 3 | 🟢 |
| Open critical bugs | CTO | 0 | 2 | 🔴 |
| Runway | CFO | > 18mo | 16mo | 🟡 |

**Anti-pattern:** measuring everything. Tracking 40 KPIs means you're watching, not managing.

### 3. Meeting Pulse
The rhythm that keeps the company alive — not optional.

| Meeting | Frequency | Duration | Who | Purpose |
|---------|-----------|----------|-----|---------|
| Daily standup | Daily | 15 min | Each team | Blockers only |
| L10 / Leadership sync | Weekly | 90 min | Leadership team | Scorecard + issues |
| Department review | Monthly | 60 min | Dept + leadership | OKR progress |
| Quarterly planning | Quarterly | 1–2 days | Leadership | Set rocks, review strategy |
| Annual planning | Annual | 2–3 days | Leadership | 1-year + 3-year vision |

**The L10 meeting (weekly leadership sync), named for the goal of a 10/10 meeting, fixed agenda:** good news, 5 min (personal + business) → scorecard review, 5 min (red items only) → rock review, 5 min (on/off track) → customer/employee headlines, 5 min → issues list, 60 min (IDS, see below) → to-dos review, 5 min (last week's commitments) → conclude, 5 min (rate 1–10, what would make it a 10 next time).

### 4. Issue Resolution (IDS)
The core problem-solving loop — maximum 15 minutes per issue. **Identify, Discuss, Solve:**
- **Identify:** the actual issue in one sentence — the root cause, not the symptom.
- **Discuss:** relevant facts and perspectives, time-boxed; stop once discussion starts repeating.
- **Solve:** one owner, one action, one due date, written on the to-do list.

**Anti-patterns:** "let's take this offline" (most offline items never get resolved); discussing without deciding; revisiting decided issues (once solved it leaves the list — reopen only with new information).

**The Issues List:** a running, prioritized list of unresolved issues, owned by the leadership team, reviewed and pruned weekly. If an issue has sat 3+ meetings without discussion, it's either not real or too scary to address — both deserve attention.

### 5. Rocks (90-Day Priorities)
The 3–7 most important things each person must accomplish in the next 90 days — not the job description, the things that move the company forward. 90 days is long enough for meaningful progress, short enough to stay real.

**Rules:** 3–7 rocks per person maximum (more and none get done); 3–7 company-level rocks for the leadership team; each rock is binary, done or not done, no "60% complete"; set at quarterly planning, reviewed weekly.

**Bad rock:** "Improve our sales process." **Good rock:** "Implement Salesforce CRM with full pipeline stages and weekly reporting by March 31." A to-do takes one action; a rock takes 90 days of consistent work.

### 6. Communication Cadence
Who gets what information, when, and how.

| Audience | What | When | Format |
|----------|------|------|--------|
| All employees | Company update | Monthly | Written + Q&A |
| All employees | Quarterly results + next priorities | Quarterly | All-hands |
| Leadership team | Scorecard | Weekly | Dashboard |
| Board | Company performance | Monthly | Board memo |
| Investors | Key metrics + narrative | Monthly or quarterly | Investor update |
| Customers | Product updates | Per release | Release notes |

**Default rule:** if deciding whether to share something internally, share it. The cost of under-communication always exceeds the cost of over-communication inside a company.

## Operating System Selection

| If you are... | Consider... |
|---------------|-------------|
| 10–250 person company, founder-led, operational chaos | EOS / Traction |
| Ambitious growth company, need rigorous strategy cascade | Scaling Up |
| Tech company, engineering culture, hypothesis-driven | OKR-native |
| Decentralized, flat, high autonomy | Holacracy (only if patient) |
| None of the above quite fit | Custom hybrid |

## Implementation Roadmap
Don't implement everything at once. Quick start, first 30 days: build the accountability chart (one 2-hour workshop); define 5–10 weekly scorecard metrics (1-hour leadership alignment); start the weekly L10 meeting with no prep, just start. These three alone improve coordination more than most companies achieve in a year.

## Common Failure Modes
- **Partial implementation:** "We do OKRs but skip the weekly check-in" — half an operating system is worse than none, it creates theater without accountability.
- **Meeting fatigue:** adding the full rhythm on top of existing meetings — start by replacing meetings, not adding them.
- **Metric overload:** starting with 30 KPIs because "they all matter" — start with 5, add once the cadence is established.
- **Rock inflation:** 12 rocks per person because "everything is a priority" — hard limit is 7.
- **Leader non-compliance:** leadership skipping the L10 or ignoring IDS — the operating system mirrors the respect leadership gives it.
- **Annual planning without quarterly review:** quarterly is the minimum review cycle for any meaningful goal.

## Integration with C-Suite

| C-Suite Role | OS Dependency |
|-------------|---------------|
| CEO | Sets vision that feeds the 1-year plan and rocks |
| COO | Owns the meeting pulse and issue resolution cadence |
| CFO | Owns the financial metrics in the scorecard |
| CTO | Owns engineering rocks and tech scorecard metrics |
| CHRO | Owns people metrics (attrition, hiring velocity) in scorecard |
| Culture lead | Culture rituals plug into the meeting pulse |
| Strategy lead | Validates team rocks cascade from company rocks |

## Key Questions
- If I asked five different team leads what the company's top 3 priorities are this quarter, would they give the same answers?
- What was the most important issue raised in last week's leadership meeting? Resolved or still open?
- Name a metric that would tell us by Friday whether this week was a good week. Do we track it?
- Who owns customer churn? Can you name that person without hesitation?
- When was the accountability chart last updated?