At 50 people, the operating model that ran the company at 20 is obsolete. Not gradually obsolete — abruptly. The founding team can no longer maintain a shared mental model of what's happening. The weekly all-hands stops being sufficient. The CEO starts to feel like she's running the organization by phone instead of building it.
This is the moment most companies reach for a framework: OKRs, EOS, Hoshin Kanri. The framework is often the right move. The mistake is implementing the framework without the operating system below it.
Here's what the operating system looks like.
The five decisions that build the model
A strategy operating model for a 50-person company is the sum of five explicit choices. Each one sounds simple. Each one has to be made deliberately or it defaults to the wrong thing.
Decision 1: What is our goal syntax, and who owns it?
Choose one framework for setting and tracking goals — OKRs, KPIs, OGSM, EOS Rocks, SMART goals. Not two. One. The framework matters less than the consistency.
Then name the person who owns the goal system. Not "leadership." A person. This is usually the COO, the Chief of Staff, or, in a company without either, the CEO. Their job: make sure every goal has a named single owner, an update cadence, and a connection to the work layer.
Decision 2: How do we express the strategy in three priorities?
The annual strategy results in exactly three strategic priorities for the next twelve months. Not five. Not eight. Three. For each priority:
- The named outcome (what "done" looks like at the end of the year)
- The single owner (who drives it to completion)
- The bandwidth assigned (which specific people, and what percentage of their week)
- The lead indicator (what we watch weekly to know if it's on track)
If you can't write three priorities without mentioning bandwidth, it's because the bandwidth doesn't exist. That's the most important thing to learn from the exercise.
Decision 3: How does the work connect to the goals?
Every initiative — every work stream that consumes meaningful senior capacity — links to one of the three strategic priorities. If an initiative doesn't link to a priority, it has to be reclassified: either it becomes a fourth priority (which means one of the three gives up capacity) or it's moved to an operational layer that gets a fixed bandwidth cap.
The connection is made at the initiative level, not at the task level. Don't tag tasks. Tag initiatives — the three-to-eight-week directed efforts that have a hypothesis and an owner.
Decision 4: What is the operating cadence?
The cadence is the rhythm by which the organization surfaces, discusses, and decides. At 50 people, three rhythms are non-optional:
Weekly: A one-hour leadership team meeting. Not status updates — the system provides those. Agenda: what decisions are pending, what's stalled and needs intervention, what changed this week that changes the plan.
Monthly: A two-hour strategy review. Agenda: review each priority's lead indicator, surface initiatives that are stalled or drifting, make one or two explicit prioritization decisions. The output is always a decision, not just an update.
Quarterly: A half-day or full-day QBR. Agenda: did we close or move our three priorities, what did we learn, what do the next three priorities look like. The output is the next quarter's three priorities with owners and bandwidth.
Decision 5: What is the single system of record?
One system holds the goals, the initiatives, the owners, the status, and the risk. Not three systems with an integration. One.
The system should be trustworthy enough that the COO can answer, on any day, these three questions without a meeting: (1) What are our three strategic priorities? (2) What work is currently moving each of them? (3) Which priorities are on track and which are at risk?
If the answer requires three tools and a Slack conversation, the system of record isn't doing its job.
The model in practice
Here's what it looks like in week six of the operating cadence:
The COO opens the system Monday morning. Priority 1 (net revenue retention to 110%) has three active initiatives — two on track, one stalled because the engineer it depends on is at 130% allocation. She flags the over-allocation. The initiative owner gets a notification. The weekly leadership meeting on Tuesday opens with: "We have an over-allocation on Priority 1 — do we add capacity from Priority 3, delay the initiative, or descope it?" The team decides in fifteen minutes. The system is updated. The decision is logged.
No status meeting. No Friday status deck. No Sunday evening reconstruction. One decision, made on Tuesday, from a system that surfaced it on Monday.
That's not a goal framework. That's an operating model.
The Vindaris position
A 50-person company that sets three real priorities — backed by named owners, real bandwidth, and traceable work — outperforms a 50-person company that sets twelve goals on a dashboard. The framework is the easy part. The operating model below it — the cadence, the system of record, the ownership discipline — is what makes strategy executable.