Tuning Your Operating Cadence
Set review rhythm by two signals: too fast if no progress, too slow if content is stale
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 87%
The purpose of a cadence is to be predictable so teams know what they're marching toward, but the interval must be tuned to the work. This framework gives two diagnostic signals for whether your review cadence is wrong and a guard against the common mistake of assuming more frequent checks make things go faster. It frees you to depart from the default quarterly rhythm.
Origin
Claire Hughes Johnson's operating lesson from Stripe, where quarterly business reviews were re-tuned to six-week reviews for fast-moving new product areas.
Core principles
- 01The point is to have a cadence, because predictability lets teams set goals and know when they report out
- 02Cadence interval should fit the work, not a default calendar quarter
- 03More frequent checks can slow velocity by creating overhead
- 04Give people time to actually work between reviews
- 05A separate strategy cadence prevents the metrics review from becoming a de facto strategy review
How to run it
- 1
Establish a predictable cadence
Set a regular review rhythm so teams know what they're marching toward and when they'll report out, and can set goals to make progress in that window.
Pro tip Predictability itself is the value; it lets teams plan backward from the reporting moment.
- 2
Check the too-fast signal
If little to no progress is being made between reviews, the cadence is too fast; you're reviewing before there's anything new to review.
Pro tip New product areas in heavy development often need faster cycles; mature areas can go slower.
Watch out Frequent checks feel productive but can add overhead that actually slows real velocity.
- 3
Check the too-slow signal
If the content you're reviewing feels stale, 'we already knew this' or 'we already did that,' the cadence is too slow.
Pro tip Watch for the metrics review quietly becoming the strategy review because strategy isn't discussed often enough on its own.
Watch out When you finally reach the strategy review and it feels like you already had the meeting, your cadences are out of sync.
- 4
Re-tune the interval
Change the cadence to fit, e.g. move quarterly business reviews to every six weeks for fast-moving areas, or run six-month planning instead of annual.
Pro tip Don't feel restricted by what other companies do; play with the timeframe.
Watch out Don't add frequency reflexively; be wary of slowing velocity by creating prep overhead.
In the wild
At Stripe, quarterly business reviews were too infrequent for new product areas still in development that were getting lots of feedback and launching frequently. The team simply said they're not quarterly anymore, they're every-six-week business reviews.
→ Matching the review interval to the pace of the work kept the content fresh and useful.
To avoid wasting prep time, Stripe pushed to review metrics on live, web-accessible dashboards by screen-share rather than special presentations. Even so, versions of the over-prep problem persisted, addressed by 'spin the wheel' random selection of who presents so no one over-prepares.
→ Reduced prep overhead and enforced good real-time dashboards, though the discipline required ongoing reinforcement.
Common mistakes
Assuming more frequent checks make things run faster
Adding review frequency creates prep overhead and can slow velocity; leaders fool themselves that more checks equals more speed.
Letting the metrics review absorb strategy
When strategy isn't reviewed on its own cadence, teams discuss it through the data in metrics reviews, so the actual strategy review feels stale and redundant.
Is it for you?
Best for
Operators and leaders setting review and planning rhythms for teams of varying maturity
Not ideal for
Very early teams in one room where formal review cadences would be premature overhead
From the transcript
“change your Cadence the point is to have one because then it's predictable for teams”
“it's probably too fast if not enough progress is being made in between whatever your review”
“it's probably too slow if the content you're reviewing seems stale”
“the metrics review becomes the strategy review because you don't you're not talking about the strategy often enough”
“don't fool yourself that thinking having more frequent checks on things is going to actually make things run faster”
From the episode
Lessons from scaling Stripe
Claire Hughes Johnson (former COO of Stripe)