← The Vetta library

Opinion · From the founder

The five ways we broke our own cadence — and the fixes that worked

Advice about weekly operating rhythms usually comes packaged as success stories. This is the other list. Over sixteen years of running a weekly cadence, we found most of the ways to quietly break one — while still technically holding the meeting every week. Every failure below looked, from the inside, like doing it right. If your cadence feels like it's working but the business isn't moving, check this list first.

1. The status-update meeting

The most common failure wears the costume of diligence: everyone reports, in turn, what they did last week. It feels productive and informative. It is neither — status is what the scorecard is for, delivered in ten minutes of numbers. When the meeting becomes serial reporting, the people not speaking check out, no decisions get made, and the hour evaporates with everyone "informed" and nothing changed. The fix: a hard rule that the meeting exists to solve, not report. Reporting is compressed into the scorecard and goal readouts; the bulk of the hour goes to the ranked issues list. If nobody can remember a decision the meeting made last month, you're holding a status meeting with extra steps.

2. The founder monologue

I say this as a founder: the fastest way to kill the room is to fill it. When the founder talks first and most — reacting to every number, opining on every issue — the team learns the meeting is a performance for an audience of one, and stops bringing real problems to it. The silence that follows isn't alignment; it's self-protection. The fix: structural, not aspirational. Someone other than the founder facilitates. Owners read their own numbers. On issues, the founder speaks last — deliberately — and the issues list is ranked by the room, not the loudest voice. A cadence where the founder speaks last surfaces roughly twice the problems, which is the entire point of having one.

3. The false control of too many metrics

A scorecard that starts at twelve numbers has a way of becoming thirty — every incident adds a metric, none ever leaves. It feels like rigor; more instruments, more control. What it actually buys is a readout too long to discuss, owners who skim their own lines, and a board where everything is measured and nothing is watched. The fix: a hard cap and a one-in-one-out rule. Ten to fifteen numbers, each fighting for its seat every quarter. The discipline isn't what you measure — it's what you decline to measure weekly so the numbers that matter still get read like they matter.

4. Accurate data on the wrong metric

The sneakiest one. The number is clean, the tracking is solid, the owner is diligent — and the metric doesn't drive anything. We once tracked an activity number for two quarters, hit goal most weeks, and watched the outcome it supposedly fed stay flat, because the real constraint was elsewhere. Precision had made the number credible; credibility exempted it from scrutiny. The fix: the pairing test. Every weekly input metric must name the outcome it predicts, and when input runs green while outcome runs flat, that divergence is an automatic issue. Measurement quality is not metric quality.

5. Goals too weak to fail

The quietest failure: targets set where they're already met. Every line green, every week, all quarter. It photographs beautifully and steers nothing — a goal that can't go red isn't a goal, it's décor. Weak goals usually creep in innocently, set once in an optimistic January and never revisited as the business grew past them. The fix: goals get re-derived every quarter from what the plan actually requires, not from last year's comfort. A healthy board runs some red. All-green for a month straight isn't excellence — it's a calibration problem, and it goes on the issues list like any other.

The pattern underneath

All five failures share a shape: the ritual survives while the function dies. The meeting still happens, the board still updates, and the mechanism that turns numbers into decisions has quietly stopped. Which is why the single best health metric for a cadence isn't attendance or streak length — it's the rating the team gives the meeting, out loud, every week. Teams don't rate theater a nine. When the score sags, one of the five is usually why.

Where Vetta fits: half these failures are habits, and half are things software can refuse to allow — Vetta enforces one owner per number, keeps the readout timed, ranks the issues list, tracks goal freshness, and asks the room for its rating every single week. The habits are still yours. See how it works. (A confession: the war stories here are compressed; the fuller versions live in sixteen years of Tuesday meetings.)

Related

The ritual is easy. The function is the work.

Vetta is built to keep the function alive — owned numbers, ranked issues, timed segments, and a rating that tells you the truth.