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

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

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

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

Example Scorecard

Component 3: Meeting Pulse

Full Meeting Rhythm

L10 Meeting Agenda (Weekly Leadership)

Component 4: Issue Resolution (IDS)

Maximum 15 minutes per issue. This is the core problem-solving loop.

IDENTIFY: What is the actual issue? (One sentence, root cause, not symptom)
  |
DISCUSS: Relevant facts + perspectives. Time-boxed.
  |       When discussion starts repeating, STOP.
  |
SOLVE: One owner. One action. One due date. Written down.

IDS Anti-Patterns

Component 5: Rocks (90-Day Priorities)

Rock Rules

Good vs. Bad Rocks

Component 6: Communication Cadence

Default rule: If deciding whether to share internally, share it. Under-communication always costs more than over-communication.

Implementation Roadmap

30-Day Quick Start

These four alone improve coordination more than most companies achieve in a year.

90-Day Full Implementation

Common Failure Modes

Red Flags

• Five team leads give different answers when asked "What are the top 3 company priorities?" -- alignment failure
• Same issue on the issues list for 4+ weeks -- avoidance or structural problem
• No weekly scorecard exists -- flying blind
• Rocks set but never reviewed weekly -- goals without accountability
• Accountability chart has not been updated in 6+ months -- reality has drifted
• Meetings consistently end without decisions -- meeting design problem
• Communication is all top-down, never bottom-up -- feedback loop broken

Integration with C-Suite

ceo-advisor

coo-advisor

cfo-advisor

cto-advisor

chro-advisor

culture-architect

strategic-alignment

change-management

Output Artifacts

Tool Reference

scorecard_builder.py

Builds and tracks weekly company scorecards with RAG status, trend analysis, and IDS-ready issue lists for L10 meetings.

# Run with demo data
python scripts/scorecard_builder.py

# From JSON with metrics and rocks
python scripts/scorecard_builder.py --input scorecard.json

# JSON output
python scripts/scorecard_builder.py --json

rocks_tracker.py

Tracks 90-day company and individual rocks with binary status, blocker identification, and owner accountability.

# Run with demo data
python scripts/rocks_tracker.py

# Specify quarter
python scripts/rocks_tracker.py --quarter Q2

# From JSON
python scripts/rocks_tracker.py --input rocks.json

# JSON output
python scripts/rocks_tracker.py --json

meeting_pulse_designer.py

Designs company meeting rhythms, validates meeting load, identifies redundancies and gaps, and generates L10 agenda templates.

# Run with demo meetings
python scripts/meeting_pulse_designer.py

# Specify team size
python scripts/meeting_pulse_designer.py --team-size 50

# From JSON with current meetings
python scripts/meeting_pulse_designer.py --input meetings.json

# JSON output
python scripts/meeting_pulse_designer.py --json

Troubleshooting

Success Criteria

• Weekly L10 meeting happens every week with 90%+ leadership attendance (no exceptions for 12+ consecutive weeks)
• Scorecard reviewed weekly with red metrics discussed using IDS format (zero red metrics ignored)
• 70%+ of quarterly rocks completed as binary done/not-done by end of quarter
• Issues list: average issue resolved within 2 meetings (no issue lingers 4+ weeks)
• All team leads can articulate top 3 company priorities identically (tested quarterly)
• Meeting hours per person per week below 10 hours (measured via meeting_pulse_designer.py)
• Accountability chart reviewed and updated quarterly with zero unowned functions

Scope & Limitations

In Scope: Operating system selection (EOS, Scaling Up, OKR, Holacracy), accountability charts, weekly scorecards, meeting pulse design, IDS issue resolution, 90-day rocks, communication cadence, implementation roadmap.

Out of Scope: OKR software configuration, project management tool setup, Agile/Scrum methodology, sprint planning, product backlog management, HR policy development.

Limitations: Scorecard builder calculates RAG from provided data but cannot source live metrics from business systems. Rocks tracker uses manual status updates -- it cannot automatically detect completion. Meeting pulse designer provides recommendations based on team size and meeting inventory but cannot account for company-specific cultural norms. Framework comparison is directional -- actual implementation success depends on leadership commitment.

Integration Points

ceo-advisor

coo-advisor

cfo-advisor

cto-advisor

chro-advisor

culture-architect

strategic-alignment

change-management

chief-of-staff