Cadence is the fourth element of VOOCS, the execution framework Russ Reeder built. It answers: what rhythm forces closure? Decisions drift because there is no forcing function, not because people are indecisive. Cadence is that forcing function: a Weekly Close that ends with decisions, and a Decision Log that keeps them. The verb is close it.
What breaks without cadence
Russ Reeder built Cadence, the fourth element of VOOCS, around a pattern he saw across nine PE-backed companies: decisions rarely fail in the meeting where they are made. They fail in the weeks after, when nothing forces anyone to close them and the question quietly reopens.
Without a cadence that demands closure, discussions become perpetual. "We're still analyzing" becomes the default, and meanwhile competitors ship.
If decisions keep reopening, you have a cadence problem. The fix is to install forcing functions, starting with one meeting a week that exists to close things.
What to build
- Weekly CloseNot a status update. Four questions, every week: What decisions closed? What's stuck? Who decides by when? What's the cost of waiting? The last one matters most, because it puts a price on "let's discuss it more."
- Decision LogEvery commitment from the Weekly Close, with its owner and date, so nothing slips between meetings and closed decisions stay closed.
How you know cadence is working
In my experience, you know Cadence is working when the Weekly Close runs without the advisor in the room and decisions get made at the right level. The Decision Log shows commitments closing on the dates they were given, the same question stops coming back every month, and "we're still analyzing" stops being an acceptable answer.
I've watched companies spend months analyzing a decision worth $200,000 while burning $50,000 per month in delay costs. The math was never made visible. Once it was, they decided in a week.
Where cadence fits in VOOCS
VOOCS runs in order: Vision, Outcomes, Ownership, Cadence, Systems. The mantra is the same five verbs: define it, measure it, own it, close it, scale it. Start with the element where the pain is, fix it, then move to the next.