Designing your business's operating system

A business operating system (BOS) is the collection of recurring meetings, written documents, scorecards, and decision cadences that let a business run on rails instead of on heroics. Without one, every week is improvised. With one, the business compounds.

Why every real operator cares

The #1 reason founders hit a ceiling is they can't scale themselves. A personal brain isn't a system. An operating system is, and it's what lets the business grow past the founder's daily involvement.

The five components

1. Meetings, the rhythm. Weekly, monthly, quarterly.
2. Scorecards, the numbers that say how it's going.
3. Accountability chart, who owns what.
4. Documents. SOPs, wikis, decision logs.
5. Decision protocols, how disagreements get resolved, how commitments get made.

Miss any one and the others start leaking.

Meeting rhythm (the backbone)

• Daily standup. 10 min, team-level. "What I did, what I'm doing, what's blocked."
• Weekly team meeting (L10 / WBR). 60-90 min. Scorecard review, issue list, to-dos. See Weekly business review.
• Biweekly 1:1s, manager + direct report, 30-45 min. Not status updates, growth, blockers, feedback.
• Monthly business review, leadership. KPIs vs, plan, budget, resource allocation.
• Quarterly planning. 1 day offsite. Set next quarter's rocks/OKRs.
• Annual planning. 2-3 days. Longer horizon, strategic bets.

Scorecards (the nervous system)

Every seat has a scorecard. 5-7 measurable numbers per team that tell you if the work is working. Reviewed weekly. No discussion, just read the number. Green, yellow, red.

Without scorecards, you argue about feelings. With them, you argue about reality.

Accountability chart (not an org chart)

An accountability chart is a clear mapping of seats to functions. Each seat has 3-7 "accountabilities", the actual things that seat owns. One name per seat. One seat per function.

Most orgs have 3 people all kind-of responsible for marketing, which means nobody is. The accountability chart forces clarity.

Documents (the institutional memory)

• SOPs, how we do this (see SOPs)
• Decision logs, what we decided and why (see Decision logs)
• Company wiki, policies, benefits, culture
• Strategic memo, annual refresh of "what are we doing and why"

Decision protocols

Who makes which decisions? Without this, everything escalates to the founder. Define:

• Decisions owned by individual contributors
• Decisions requiring manager approval
• Decisions requiring leadership sign-off
• Decisions requiring board-level approval

Write it down. Tape it to the wall.

The rollout

1. Start with the weekly team meeting. Just that. Get good at it.
2. Add scorecards once weekly is locked in.
3. Add the accountability chart third.
4. SOPs and decision logs accumulate naturally over 6-12 months.
5. Quarterly planning emerges after you can see a quarter clearly.

Trying to install the whole system at once collapses. Build it one layer at a time.

Frameworks that work

EOS/Traction, Scaling Up, Amazon's S-Team operating model, Bridgewater's principles, each is a published operating system. Pick one, modify, commit. Don't Frankenstein three of them.