The Operating Cadence
The operating cadence. How a leadership team actually runs the week.
Most advice on SaaS metrics tells you what to measure. Almost none tells you how to actually run on them — the weekly rhythm of a scorecard, a tight meeting, and owned action that turns a dashboard into a company that moves. This series is that operating system, drawn from sixteen years of running a weekly cadence (and an EOS-style L10) at a bootstrapped SaaS: how to build the scorecard, run the meeting, hold the line on accountability, read signal from noise, and make the whole thing stick past month two.
Why weekly beats monthly
The case for the weekly rhythm
The honest alternative to a weekly cadence isn't a tidy monthly review — it's Slack chaos. Why knowing sooner is the whole game, why the L10 replaces meetings instead of adding one, and why the week — not the day, not the month — is the natural unit of leadership accountability.
Read the article →
Building your scorecard
The 10–15 numbers that matter
How to choose the handful of numbers worth looking at every single week — and why a scorecard with fifty metrics is far worse than one with twelve. The art is in what you leave off.
Read the article →
Leading vs lagging indicators
Manage the inputs, not the outcomes
You can't manage revenue weekly — but you can manage the activities that produce it. The single most important distinction on any scorecard, with concrete leading-indicator examples by function.
Read the article →
Every metric needs a goal
A number without a target is just data
Why every line on the scorecard needs a weekly goal, how to set ones that are real rather than aspirational, and what the red and green are actually there to do.
Read the article →
Running the weekly meeting
The 90 minutes that run the company
The agenda and flow of a tight weekly leadership meeting — what to cover, in what order, how long it should take, and how to keep it from drifting into a status update or a rabbit hole.
Read the article →
Rocks, issues, and to-dos
Turning numbers into action
The machinery that converts an off-track metric into an owned action — so the scorecard changes what the team does, not just what it can see.
Read the article →
One owner per number
Accountability the scorecard enforces
Why every metric needs a single name next to it, and how the weekly rhythm turns ownership from a value on the wall into a habit the team actually lives.
Read the article →
Solve issues, don't just discuss them
Identify, discuss, solve
How disciplined teams actually work an issues list to resolution — instead of rehashing the same complaints, meeting after meeting, with nothing ever closing.
Read the article →
Reading the scorecard
Signal vs noise
Week-to-week variance versus a real trend — when a red is a fire and when it's just Tuesday. How to read the board without overreacting to every wobble or ignoring the slow drift.
Read the article →
Getting the team to actually use it
Why cadences die, and how to keep yours alive
The hardest part isn't building the cadence — it's making it stick past month two. The honest reasons cadences fizzle out, and what keeps one running for years.
Read the article →
The cadence failures we lived through
The anti-patterns, from experience
The status-update meeting nobody listens to, the founders taking all the air time, the false control of too many metrics, accurate data on the wrong metric, and the quiet failure of weak goals — the failure modes we lived through, and the fixes that worked.
Read the article →
From weekly to quarterly to annual
The full operating system
How thirteen weeks of scorecard evidence feed the QBR, what annual planning actually produces, the State of the Company meeting that broadcasts it all back down, and why the quarterly-annual rhythm beats set-and-forget goals every time.
Read the article →
This is the cadence Upbeat was built to run.
Everything in this series — the scorecard, the weekly meeting, the owned actions, signal over noise — is exactly what Upbeat puts in front of your leadership team every Monday, so the rhythm runs itself instead of living in a spreadsheet someone forgets to update.
Become a design partner →