All work

An operating cadence for a 20-person startup

Operating Cadence, 4 min read

Numbers on the weekly scorecard
8 to 12
The problem
A 20-person startup where goals get set once a year, metrics get looked at when something breaks, and every meeting is a status update.
My role
Wrote the cadence, based on the operating system I've run at MaidThis since late 2024, translated into startup terms.
Result
One page a founder could adopt on Monday. Every number has an owner and a meeting where it's reviewed, and every issue leaves with a name and a date.

Skills OKRs and cadence, process design

Context

Chief of Staff and BizOps roles usually own this. The company has a plan and a team. What it lacks is a rhythm that connects the two, so decisions get made in Slack threads and the plan is a slide nobody opens after January. I’ve run a version of this since 2024 using EOS, the operating system most small businesses use. This is that system in the words a startup uses.

The cadence

RhythmMeetingWhoLengthInputsOutputs
WeeklyMetrics review and leadership syncFounders and function leads (5 to 7 people)60 min, same day and time every weekScorecard: 8 to 12 numbers, each with an owner and a target, filled in before the meeting. Rock check-in: on track or off. Issues list.Every off-target number and every open issue leaves with one owner and a date. Decisions logged in one place.
WeeklyTeam-level sync (one per function)Each lead with their team30 minThe function’s slice of the scorecard. Blockers.Blockers escalated to the leadership issues list, not solved in a side channel.
MonthlyClose and investor updateFounder, finance owner, ops90 min for the review, update written the same weekBooks closed by the 10th. Cash, burn, runway, revenue vs plan, hiring plan vs actual.One-page investor update: highlights, key numbers, lowlights, asks. The lowlights section is not optional.
QuarterlyGoal setting and reforecastLeadership team, offsite or a full dayHalf day to full dayLast quarter’s goals scored, the annual plan, updated forecast.3 to 5 company OKRs for the quarter, each with one owner. Each function’s OKRs that ladder up. Reforecast cash and hiring.
AnnualPlanningLeadership team, 2 days2 daysStrategy, market, the 3-year picture.Annual plan: the 3 to 7 things that have to be true by December, the budget, the headcount plan.

The rules that make it work

  1. Same time every week, no cancellations. When a meeting keeps getting moved, people stop treating it as important. If the founder can’t make it, it runs without them.
  2. Numbers are filled in before the meeting, not during. The meeting is for what’s off, not for reading the sheet aloud.
  3. Every issue leaves with an owner and a date. The owner is one person, not a group.
  4. Separate the review from the fix. Identify the issue, discuss it, decide. If a fix needs more than a few minutes, it becomes an owned task and the meeting moves on.
  5. The scorecard has 8 to 12 numbers, not 40. If a number hasn’t changed a decision in a quarter, cut it.
  6. Lowlights go in the investor update. Investors find out about problems eventually, and it’s better if they hear it from you with a plan attached.

Where it comes from: EOS to startup words

I didn’t invent any of this. It’s EOS, which I’ve run at MaidThis for two years, translated.

EOS term (what I run)Startup termHow it worked for me
ScorecardWeekly KPI dashboardSales, recurring revenue, churn, gross profit, CAC, channel ROI, hiring funnel. Found the 40% applicant leak and the LSA cost problem from this sheet.
RocksQuarterly OKRs3 to 5 per quarter, one owner each. Scored on the last meeting of the quarter.
L10 meetingWeekly leadership syncSame agenda every week, 90 minutes for us. The one meeting I never skip, even remotely.
IDS (identify, discuss, solve)Issue triage and decision logWhere a sales agent sitting on leads for two weeks became a response-time metric with an owner.
Accountability chartOrg chart with one DRI per functionOps, recruiting, sales, management. One name on each box, even when two of the boxes are me.
V/TO (vision and traction organizer)Strategy doc and annual planWhere the yearly headcount plan and the commercial line decision came from.

What I’d watch for

  • Too many meetings, too few decisions. If the weekly sync becomes a status readout, cut the readout and keep only the off-target items.
  • Metrics nobody owns. A number with no name attached stops getting looked at within a month.
  • Rocks that don’t change. If the same goal carries over three quarters in a row, look at what’s blocking it before setting it again.