company-os

# 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 do not 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, annual planning, communication cadence

---

## Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

- [ ] **Company size and stage** — the framework recommendation (EOS / Scaling Up / OKR-native / Holacracy) and implementation timeline are driven primarily by headcount
- [ ] **What is actually broken** (no scorecard, misaligned priorities, recurring unresolved issues, meeting overload) — determines which of the six components to build first
- [ ] **Founder operating style** (operational vs. visionary) and whether the company is engineering-led or sales-led — tips the framework choice within a given size band
- [ ] **What rhythms and metrics already exist** — so the new OS replaces meetings rather than stacking on top and causing meeting fatigue

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

---

## Operating System Selection

### Decision Tree

```
START: "Which operating system?"
  |
  v
[Company size?]
  |
  +-- 10-50 people
  |     |
  |     v
  |   [Is the founder operational or visionary?]
  |     |
  |     +-- Operational --> EOS / Traction (structured, simple)
  |     +-- Visionary --> Scaling Up (ambitious, strategy-heavy)
  |
  +-- 50-200 people
  |     |
  |     v
  |   [Engineering-led or sales-led?]
  |     |
  |     +-- Engineering-led --> OKR-native (hypothesis-driven)
  |     +-- Sales-led --> Scaling Up or EOS (execution-focused)
  |
  +-- 200+ people
  |     |
  |     v
  |   [High autonomy or high alignment needed?]
  |     |
  |     +-- High autonomy --> Holacracy (only if patient)
  |     +-- High alignment --> Custom hybrid (best of EOS + OKR)
  |
  +-- Not sure --> Start with EOS. It is the simplest to implement.
```

### Framework Comparison Matrix

| Feature | EOS | Scaling Up | OKR-Native | Holacracy |
|---------|-----|-----------|------------|-----------|
| Complexity | Low | Medium | Medium | High |
| Implementation time | 30-90 days | 90-180 days | 60-120 days | 6-12 months |
| Best company size | 10-250 | 50-500 | 20-500 | 50-300 |
| Goal framework | Rocks (binary) | OKRs + Priorities | OKRs (graded) | Roles + accountabilities |
| Meeting cadence | Weekly L10 | Daily huddle + weekly | Weekly + quarterly | Governance + tactical |
| Issue resolution | IDS | Keep/Kill/Combine | Retrospective | Governance process |
| Accountability | Accountability chart | Function accountability | OKR ownership | Role-based |
| Scorecard | Weekly numbers | Weekly KPIs | Quarterly KRs | Metrics per role |
| Strengths | Simple, fast to implement | Rigorous, strategy-heavy | Flexible, tech-friendly | Distributed authority |
| Weaknesses | Can feel rigid | Complex, requires discipline | Can drift without structure | Steep learning curve |

---

## The Six Core Components

Every effective operating system has these six, regardless of framework:

### Component 1: Accountability Chart

Not an org chart. An accountability chart answers: "Who owns this outcome?"

#### Design Principles

| Principle | Implementation |
|-----------|---------------|
| Single ownership | One person owns each function. Multiple may work in it. |
| Explicit gaps | Functions nobody owns are identified and assigned. |
| No overlap | If two people think they own it, neither does. Resolve immediately. |
| Stage-appropriate | One person can own multiple seats early. Be explicit about it. |
| Quarterly review | Ownership shifts as company grows. Review every quarter. |

#### Accountability Chart Template

```
CEO
  |
  +-- Revenue (CRO/VP Sales)
  |     +-- Inbound pipeline
  |     +-- Outbound pipeline
  |     +-- Customer success
  |
  +-- Product & Engineering (CTO/CPO)
  |     +-- Product roadmap
  |     +-- Engineering delivery
  |     +-- Technical operations
  |
  +-- Operations (COO)
  |     +-- Finance & legal
  |     +-- People operations
  |     +-- Business operations
  |
  +-- Marketing (CMO/VP Marketing)
        +-- Demand generation
        +-- Brand & content
        +-- Product marketing
```

#### Workshop Protocol (2 hours)

```
Step 1: List all functions the company performs (30 min)
Step 2: Assign ONE owner per function (30 min)
Step 3: Identify gaps (functions nobody owns) (15 min)
Step 4: Identify overlaps (2+ people claiming ownership) (15 min)
Step 5: Resolve gaps and overlaps (20 min)
Step 6: Publish and communicate (10 min)
```

### Component 2: Scorecard

Weekly metrics that tell you if the company is on track. Not monthly. Not quarterly. Weekly.

#### Scorecard Rules

| Rule | Rationale |
|------|-----------|
| 5-15 metrics maximum | More than 15 = nothing gets attention |
| Each metric has an owner | Ownership drives accountability |
| Each metric has a weekly target | Not a range -- a specific number |
| Red/Yellow/Green status | Not paragraphs -- traffic lights |
| Only Red metrics get discussion | Green = no discussion needed in meeting |

#### Example Scorecard

| Metric | Owner | Target | Week | Status |
|--------|-------|--------|------|--------|
| New MRR | CRO | $50K | $43K | [R] |
| Logo churn | CS Lead | < 1% | 0.8% | [G] |
| Active users | CPO | 2,000 | 2,150 | [G] |
| Deployments | CTO | 3/week | 3 | [G] |
| Critical bugs open | CTO | 0 | 2 | [R] |
| Runway | CFO | > 18mo | 16mo | [Y] |
| Offer acceptance | CHRO | > 85% | 90% | [G] |

### Component 3: Meeting Pulse

#### Full Meeting Rhythm

|