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.