Company Operating System — 90-Day Implementation Guide

Don't implement everything at once. The fastest path to failure is trying to launch the full operating system in week one. Build incrementally. Let the team experience wins before adding complexity.

Before You Start

Prerequisites

Leadership alignment (non-negotiable): Every member of the leadership team must understand why you're doing this and commit to running the system. One holdout destroys the whole model. If the CFO skips the L10 meetings, the system won't work.

Current state audit:

• What meetings currently exist? Which can be replaced?
• Who owns which functions today? (Even informally)
• What metrics are being tracked? (Even inconsistently)

Assign an OS owner: One person is responsible for the implementation and ongoing maintenance of the operating system. Usually the COO or CEO (at smaller companies). This is not a committee job.

Week 1–2: Accountability Chart + Scorecard

Accountability Chart Workshop (Week 1)

Duration: 2–3 hours, full leadership team

Step 1 — List all functions (30 min) On a whiteboard, list every function the company performs:

• Sales (inbound, outbound, partnerships)
• Marketing (content, paid, brand)
• Product (roadmap, design, research)
• Engineering (frontend, backend, devops)
• Customer success (onboarding, support, retention)
• Finance (accounting, FP&A, legal)
• People (recruiting, HR, culture)
• Operations (processes, tools, facilities)

Step 2 — Assign owners (45 min) For each function: "Who is the one person ultimately accountable?" Write their name. Rules: One name only. No joint ownership. One person can own multiple functions at small scale.

Step 3 — Identify gaps and overlaps (30 min)

• Gaps: Functions with no owner → Who should own them? Or do we need a hire?
• Overlaps: Two people said they own the same thing → Resolve now, not later.

Step 4 — Publish and socialize (Week 2) Share with the full company. Explain what an accountability chart is and isn't. "This is about clarity, not hierarchy. It tells everyone who to go to for each function."

Output: A documented accountability chart. Use a simple tool (Miro, Google Slides, Ninety.io).

Scorecard Design (Week 2)

Duration: 90 minutes, leadership team

Step 1 — List candidate metrics (30 min) Each leader lists 3–5 metrics they already track or wish they tracked. No filtering yet.

Step 2 — Filter to 5–15 (30 min) Criteria: Is it measurable weekly? Does it tell us if the company is healthy? Does one person own it? Drop: metrics that are monthly only, metrics without a clear owner, metrics that measure activity not outcomes.

Step 3 — Set weekly targets (20 min) For each metric: what's the weekly target? Not a range — a number. Red/yellow/green thresholds.

Step 4 — Assign owners (10 min) Every metric has one owner who is responsible for reporting it weekly.

Output: A scorecard document. 5–15 metrics, owner, target, weekly tracking column.

First scorecard run: Week 2 or 3. It won't be perfect. That's fine.

Week 3–4: Meeting Pulse (Start With L10)

Don't start all the meetings at once. Start with the weekly L10. Replace existing leadership syncs.

L10 Meeting Setup

Schedule: Same day, same time, every week. Non-negotiable attendance. Duration: 90 minutes. No more, no less. Facilitator: Rotate or assign to COO/CEO. The facilitator keeps time and follows the agenda.

Fixed agenda:

1. Good news (5 min) — One personal, one business from each person. No skipping.
2. Scorecard review (5 min) — Traffic light only. Red items go to the issues list.
3. Rock review (5 min) — Each person: "on track" or "off track." No justification needed at this step.
4. Customer/employee headlines (5 min) — One sentence each. No reports.
5. Issues (60 min) — IDS process. Prioritize the top 3–5 issues. Solve them.
6. To-do review (5 min) — Review last week's commitments (done/not done). No excuses, just data.
7. Conclude (5 min) — Rate the meeting 1–10. What would make next week better?

First L10 meeting: It will feel awkward. Run through the agenda anyway. The team needs the repetition to internalize it. By week 4, it should feel natural.

Issues List Setup

Create a shared document (Notion, Google Docs, or dedicated tool):

• Issue title
• Priority (High / Medium / Low)
• Status (Open / In progress / Solved)
• Owner (once assigned)
• Due date

At the first L10, generate the issues list by asking: "What's getting in our way right now?" Expect 10–20 items on the first pass.

Week 5–8: Rocks and Quarterly Planning

Quarterly Planning Session (end of Week 5 or start of Week 6)

Duration: 4–8 hours (or 2 × 4-hour days for larger teams) Who: Full leadership team

Session structure:

Part 1: Review previous quarter (60–90 min)

• What rocks were completed? What were dropped?
• What did we learn?
• What changed in the market or company?

Part 2: Confirm or update company direction (60 min)

• Is the 1-year goal still valid?
• Any major strategy shifts needed?
• Update the V/TO or OPSP if using EOS or Scaling Up.

Part 3: Set company rocks (90 min)

• Brainstorm: What are the 3–7 most important things to accomplish this quarter?
• Prioritize. Be ruthless. 3 rocks done > 7 rocks started.
• Each rock: clear owner, clear definition of done, 90-day timeline.

Part 4: Set individual rocks (60 min)

• Each leader sets their 3–7 rocks (aligned with company rocks where possible)
• Share with group: dependencies? Conflicts? Overloaded people?

Part 5: Communicate (Week 6)

• Share company rocks with the full organization within 1 week
• Each team sets their own rocks, cascaded from company rocks (3–5 per team)

Rock template:

Rock: [What you'll accomplish]
Owner: [One person]
Due date: [Specific date within the quarter]
Definition of done: [How we'll know it's complete]
Dependencies: [What else needs to happen first]

Week 9–12: Issue Resolution Mastery + Communication Cadence

By now the L10 should be running smoothly. Weeks 9–12 focus on deepening IDS skills and establishing the broader communication cadence.

IDS Practice

The issue resolution process often degrades in weeks 5–8. Common problems:

• Issues discussed but never solved (no clear action item)
• Same issues recurring (root cause not addressed)
• Too many issues, not enough resolution (prioritization failing)

IDS calibration exercise (Week 9): In the next L10, after each issue is "solved," ask:

• "Is this actually solved, or are we postponing it?"
• "What's the specific action? Who owns it? When is it due?"
• "Is this the real issue, or a symptom of something deeper?"

Communication Cadence Setup

Build out the full communication calendar:

Company all-hands template:

1. State of the company (financial health, key metrics) — 10 min
2. Quarterly rocks: what we committed to, where we stand — 10 min
3. Wins and recognitions — 5 min
4. What's coming next quarter — 10 min
5. Q&A — 15–25 min

Post-90 Days: Refinement and Optimization

Month 4 retrospective

After the first full quarter, run a retrospective on the operating system itself:

• What's working? What isn't?
• Which meetings should continue as-is? Which need adjustment?
• Is the scorecard measuring the right things?
• Are rocks the right size and specificity?
• What should we add next?

Scorecard evolution

By month 4, you'll know which metrics matter most. Add 2–3 that are missing. Remove metrics that nobody uses for decisions.

L10 health check

Rate your L10 meetings over the first quarter:

• Average rating < 7: The agenda isn't being followed or issues aren't being resolved. Diagnose.
• Average rating 7–8: Normal. Keep building discipline.
• Average rating > 8: The team is engaged. Start extending the system to department level.

Department L10s (Month 4+)

Once leadership L10 is running well, cascade the meeting structure:

• Each department runs their own weekly L10
• Department rocks cascade from company rocks
• Issues that cross departments are escalated to leadership L10

Year 1 annual planning

End of year 1: run a full-day annual planning session.

• Review the year: what did we accomplish? What did we miss? What did we learn?
• Update 3-year vision (has it changed?)
• Set next year's annual goals
• Set Q1 rocks
• Celebrate. Seriously — mark the milestone.

Implementation Anti-Patterns

Skipping the accountability chart: Without ownership clarity, every other system breaks down. Do this first.

Building a perfect scorecard before starting: Start with 5 imperfect metrics. Improve over time.

Not replacing existing meetings: Adding L10 on top of 3 existing meetings creates meeting overload. Cancel the redundant ones.

Leader non-participation: If one leader consistently skips or is disengaged, the system won't work. Address this directly — it's a culture issue, not a calendar issue.

Changing the L10 agenda: The agenda works because of repetition. Resist the urge to customize it for the first 6 months.

Rocks without accountability: If nobody checks rocks at the L10 ("on track / off track"), they become wish lists. The weekly review is what makes them real.

Operating System Comparison

Side-by-side analysis of the major company operating frameworks.

Overview

1. EOS — Entrepreneurial Operating System

Book: Traction by Gino Wickman

Core principles

EOS is built on Six Components:

1. Vision — Where are you going? (V/TO: Vision/Traction Organizer)
2. People — Right people, right seats
3. Data — Scorecard with weekly metrics
4. Issues — Surface and resolve with IDS
5. Process — Document core processes
6. Traction — Rocks + meeting pulse (L10)

Signature tools

• V/TO (Vision/Traction Organizer): 2-page strategy doc. Core values, core focus, 10-year target, 3-year picture, 1-year plan, quarterly rocks, issues.
• Accountability Chart: Who owns what function (not org chart)
• L10 meeting: Weekly 90-minute leadership sync (Level 10 = aim for 10/10)
• Rocks: 90-day priority commitments (3–7 per person)
• IDS: Identify, Discuss, Solve (issue resolution, max 15 min per issue)

Strengths

• Operationally focused. If your problem is execution chaos, EOS addresses it directly.
• Accessible. The book is practical. You can DIY it without a coach.
• Community. Large network of implementers, tools (Ninety.io, EOS Worldwide), and practitioners.
• Simple enough to actually use. No complex methodology. Most teams are functional within 6 months.

Limitations

• Strategic depth is shallow. The V/TO is good for direction but doesn't replace real strategy work.
• Doesn't scale beyond ~250. Designed for entrepreneurial companies. Gets cumbersome at enterprise scale.
• Assumes a cohesive leadership team. If trust is broken at the top, EOS won't fix it.
• Facilitator dependency. Many companies benefit from an EOS Implementer (external coach), which adds cost.

Best fit

• 10–150 person companies
• Founder-led, operational dysfunction
• Teams that can't stay on the same page
• Companies with recurring issues that never get resolved
• First real "operating system" for a company that's been running on vibes

Not ideal if

• You need sophisticated strategic planning
• You're > 250 people and already have ops infrastructure
• Your team resists structured methodology

2. Scaling Up (Rockefeller Habits 2.0)

Book: Scaling Up by Verne Harnish

Core principles

Built on four Decisions:

1. People — Core values, talent management, Topgrading
2. Strategy — One-Page Strategic Plan (OPSP), 7 Strata of Strategy
3. Execution — Priorities (rocks), meeting rhythm, critical numbers
4. Cash — Power of One, Cash Acceleration Strategies (CAS)

Signature tools

• One-Page Strategic Plan (OPSP): Annual and quarterly goals on one page. More strategic than EOS's V/TO.
• 7 Strata of Strategy: Competitive positioning, core customer, brand promise, X-factor (10x advantage), profit per X, BHAG, critical numbers.
• Meeting rhythm: Daily (5–15 min), weekly, monthly, quarterly, annual — with specific templates.
• Critical number: One metric that, if improved, fixes everything else.
• Cash acceleration: CAS system for improving working capital and cash conversion cycle.

Strengths

• Stronger strategic framework than EOS. The 7 strata and OPSP force real strategic thinking.
• Cash focus. Unique among frameworks — explicitly addresses cash flow management.
• Scales further. Better suited for 100–1000 person companies than EOS.
• Works for ambitious growth companies. Designed for companies that want to scale significantly.

Limitations

• More complex than EOS. Harder to DIY. Benefits heavily from a certified Scaling Up coach.
• Overwhelming at first. The full framework has many components. Teams often implement partially.
• Less prescriptive on meetings. EOS's L10 is very specific. Scaling Up's meeting rhythm requires more customization.

Best fit

• Series A to Series C companies
• Companies with strong growth ambition
• Leadership teams that want strategic rigor, not just operational clarity
• Companies already past initial chaos, ready for more sophisticated frameworks

Not ideal if

• You're pre-product-market-fit
• You need quick operational wins
• Your team doesn't have the bandwidth for the learning curve

3. OKR-Native (Google Style)

Books: Measure What Matters by John Doerr; Radical Focus by Christina Wodtke

Core principles

OKRs = Objectives + Key Results

• Objectives: Qualitative, inspiring direction. "What are we trying to achieve?"
• Key Results: Quantitative, measurable outcomes. "How will we know we achieved it?"
• Not tasks. KRs measure outcomes, not activities.

Cascade: Company OKRs → Department OKRs → Team OKRs → Individual OKRs

Cadence: Quarterly OKR cycles. Weekly check-ins. Annual reflection.

Scoring: 0.0–1.0. Target is 0.7. Consistently hitting 1.0 = OKRs aren't ambitious enough.

Strengths

• Aligns the whole company. When done well, every team can trace their work to company-level objectives.
• Encourages ambition. Moonshot OKRs are explicit. "Roofshot" vs "moonshot" OKRs.
• Widely understood in tech. Many hires will already know OKRs.
• No framework cost. No implementer required. Tooling is free or cheap (Linear, Notion, Lattice).

Limitations

• Hard to do well. Most companies run "OKR theater" — tasks dressed up as key results.
• Missing the HOW. OKRs define what to achieve but not how to operate. You still need meeting rhythm, accountability structure, and issue resolution.
• Misalignment risk. If not cascaded properly, teams run disconnected OKRs that feel like alignment but aren't.
• No operational backbone. OKRs are a goal-setting system, not a full operating system.

Best fit

• Tech companies with strong product/engineering culture
• Companies where hypothesis-driven work is already the norm
• Organizations that value autonomy and bottom-up goal setting
• As the goal-setting layer inside a broader operating system

Not ideal if

• Teams lack discipline to hold each other accountable
• You need more than just goal alignment (issue resolution, meeting structure)
• Leaders don't model OKR behavior themselves

4. Holacracy

Book: Holacracy by Brian Robertson

Core principles

Holacracy replaces the traditional management hierarchy with a system of distributed authority.

• Circles: Semi-autonomous units with defined purposes (like teams, but self-governing)
• Roles: People fill roles (not job descriptions). One person can hold multiple roles in different circles.
• Governance meetings: Roles and accountabilities are defined and evolved by the circle, not management
• Tactical meetings: Operational coordination within circles
• The Constitution: A legal document that all members ratify, replacing traditional management authority

Strengths

• Maximum autonomy. People closest to the work define how it gets done.
• Removes management as a bottleneck. Decisions happen at the circle level.
• Adapts to complexity. Circle structure evolves organically as the work changes.

Limitations

• Enormous learning curve. 2–4 years to full adoption. Many companies abandon it.
• High meeting overhead. Governance meetings add significant time.
• Doesn't eliminate politics. Just moves them to governance meetings.
• Requires full commitment. Partial Holacracy doesn't work. You either do it or you don't.
• Not for crisis mode. When speed matters, distributed governance slows you down.

When it works

• Organizations with deep belief in autonomy and self-management
• Non-profit or mission-driven organizations where consensus matters
• Companies with patient leadership willing to invest years in implementation

When it doesn't work

• Startups needing speed and clarity
• Companies with strong founder personalities who struggle to relinquish control
• Organizations that need to move fast or course-correct frequently

5. Custom Hybrid

When to build a hybrid

None of the above frameworks fits perfectly because:

• EOS lacks strategic depth
• Scaling Up is complex to implement
• OKRs don't provide operational backbone
• Holacracy is too slow to implement

The solution: take the best components of each.

Common hybrid patterns

EOS backbone + OKR goal-setting:

• EOS provides: accountability chart, L10 meeting, IDS, meeting pulse
• OKRs provide: goal-setting with ambition, cascade, and alignment checks
• Works well for: tech companies that want operational rigor with flexibility

Scaling Up strategy + EOS execution:

• Scaling Up provides: OPSP, 7 strata, cash management
• EOS provides: L10, rocks, IDS
• Works well for: ambitious growth companies that want both strategy and execution discipline

OKRs + custom meeting rhythm:

• OKRs provide: goal cascade
• Custom meetings: weekly team syncs, monthly department reviews, quarterly all-hands
• Works well for: companies that already have strong culture but need goal alignment

Hybrid design principles

1. Pick one goal-setting system. Don't mix OKRs and Rocks — they're both 90-day priority systems and will create confusion.
2. Be explicit about what you're taking from where. "We use EOS for meetings and Scaling Up for strategy" is a clear hybrid. "We do a bit of everything" is chaos.
3. Document your version. Your operating system should have a name and a one-page description of what it includes.
4. Evolve intentionally. Change one component at a time. Don't overhaul the whole system when one part isn't working.

Framework Selection Decision Tree

Is your company < 50 people and in operational chaos?
  YES → Start with EOS. It's the simplest path to order.
  NO → Continue.

Does strategic positioning and cash flow need significant work?
  YES → Consider Scaling Up.
  NO → Continue.

Is your company tech-native with strong product/engineering culture?
  YES → OKR-native with a custom meeting rhythm.
  NO → Continue.

Do you have 2+ years and full leadership commitment to radical organizational change?
  YES → Consider Holacracy (with caution).
  NO → Build a custom hybrid from EOS + OKRs.