Getting the team to actually use it. The hardest part isn't building it.

Cadences die a death by a thousand cuts

The thing that kills a cadence is rarely one big event. It's an accumulation of tiny concessions, each of which feels harmless in the moment.

Walk through the cuts, because naming them is half the defense. Treating attendance as optional. Tolerating tardiness. Letting scorecards show up not updated. Running a thin, weak issues list with nothing real on it. And don't underestimate the softer ones: a poorly facilitated meeting, the same tired issues rehashed week after week with no progress, and the co-founder dominating the conversation so everyone else checks out. Any one of these, once, is survivable. The problem is they compound — each concession makes the next one easier, and momentum bleeds away a little at a time until the cadence is dead and no one can quite say when it happened.

Rigor is the antidote

The only defense against death by a thousand cuts is to refuse the cuts — to treat the cadence as genuinely non-negotiable. Meetings are not optional. Scorecards not being updated is not acceptable. Lateness is never tolerated. This sounds rigid because it is, and the rigidity is the entire point: a cadence that bends to convenience teaches everyone that it can be bent.

Here's the bar, concretely. Across five years, the only legitimate reason to miss our weekly leadership meeting was a team member genuinely on vacation — and in that entire span, a leadership member missed maybe twice, total. That's not me bragging about attendance; it's the standard that kept the cadence alive. The moment these meetings become a nice-to-have, you break the momentum, and the slow death begins. You don't get a rigorous, high-trust cadence by being relaxed about it for the first year. You get there by being almost unreasonably strict from the start, until the strictness becomes simply how things are done.

It lives or dies with leadership

This is the non-negotiable underneath the non-negotiables: if leadership — especially the co-founders — aren't genuinely bought in, you have no chance. None. A cadence is a behavior the whole company takes its cues from, and it takes them from the top. The team watches what leadership actually does, not what it says the meeting is worth.

That's why the ritual matters so much, and why we essentially never moved the meeting — the only exception was a Monday holiday. Not for investor calls, not for a busy week, not for whatever felt urgent that Tuesday. Because the instant the CEO or COO takes the liberty to move it for something "more important," everyone else recalibrates accordingly, and the protection around the time is gone. Leadership commitment isn't a speech at the kickoff; it's showing up, on time, prepared, every single week, including the weeks it's inconvenient.

Value is earned, not announced

Rigor gets the cadence to survive; value is what makes the team actually want it. And value can't be declared in advance — it's earned, week by week, as the team builds a decision-making muscle and starts solving real business problems in the room. The first time a genuinely hard issue gets worked to a real resolution, people start to believe. Belief follows results, not the other way around.

One concrete practice that reinforced this for us: we graded the meetings — the team rated each one, including a candid read on the leader's own performance running it. That does two things. It keeps the meeting honestly improving instead of slowly degrading, and it signals that the cadence itself is held to a standard, the same way every number on the board is. A meeting that's allowed to get worse every week will lose the room; a meeting that's measured and tuned earns its place.

Lower the friction

A quiet killer of cadences is sheer overhead. If keeping the system current means wrestling stale spreadsheets, chasing people for updates, and untangling duplicate or wrong data every week, people will eventually stop — not because they don't value it, but because it's exhausting. A lot of keeping a cadence alive is just making it less work to maintain.

That's largely the integrator's job, and it's unglamorous: sending the reminders, clarifying issues before the meeting, removing duplicate data, and making sure the scorecards are actually accurate before anyone reads them out. Every bit of friction you remove makes it a little more likely the team keeps the thing current, and a cadence that's easy to keep current is a cadence that survives. The less the rhythm depends on heroics to maintain, the longer it lasts.

Give it 3–6 months to become DNA

Finally, the expectation almost nobody sets correctly: this takes time. A leadership team needs to run the cadence for three to six months before it really takes hold and becomes part of the company's DNA. The decision-making and problem-solving muscle has to be exercised, repeatedly, before it's robust — you have to keep showing up and having the meaningful, sometimes uncomfortable conversations, week after week, before any of it feels natural.

Most teams quit inside that window. Month two is exactly when the cadence feels like the most overhead and has delivered the least obvious payoff, and that's precisely when the thousand cuts start to look reasonable. The teams that make it are the ones whose leadership simply refused to let it die through the awkward early months — held the rigor, modeled the commitment, lowered the friction — until one day it stopped being a thing they were doing and became simply how the company runs. That's the whole game: survive long enough, with enough discipline, that the cadence becomes who you are.