The Operating Cadence
Your weekly meeting is not a cadence. This is three touches a week and five numbers that will tell you — bluntly, and sooner than you want — whether the rhythm is holding or just occupying calendar space. Built around the diagnostics rather than the agenda, because the agenda was never the part that failed.
Excel (.xlsx), nine sheets, and a 15-page PDF. No email, no signup, no drip sequence.

The difference between a meeting and a cadence
Almost every team has the meeting. Far fewer have a cadence, and the difference is only ever where the record ends up. A meeting produces conversation and a sincere intention to update the board afterwards. A cadence produces an updated board, because the updating happens in the room while everyone is still there to argue with it.
That sounds like a technicality until you notice what it protects. If the board is current, Monday starts from what is true. If it is three days stale, Monday starts by rebuilding context out of memory — which is exactly how a business ends up depending on whoever has been there longest and remembers the most. That is not culture. That is a single point of failure with a personality.
The three touches
Expose the truth
15 minutesFind out what is actually stuck before the week builds on top of it. This is not a status round. Nobody reports what went well.
What to ask
- What is actually stuck right now?
- What is going to be stuck by Friday if nothing changes?
- What moved since Friday, and what did not?
Where it breaks: Everyone says “on track.” That is almost never true — it means people are reporting status rather than surfacing risk, politely. The second question is the fix: asking what will be stuck by Friday gives someone permission to name a problem that has not fully arrived yet, which is the only point at which it is still cheap.
Resolve the block
15 minutesMidweek is when a block is still cheap to clear. By Friday it has already taken the week off you.
What to ask
- What is still stuck from Monday?
- What decision is it actually waiting on?
- Who is unblocking it, and by what date?
Where it breaks: The touch turns into a working session and runs forty minutes while four uninvolved people watch. Cadence surfaces and assigns; it does not solve. If something needs solving it gets a name, a date, and its own slot — otherwise everyone learns that this meeting wastes their time, and they are right.
Record the outcome
10 minutesThe step everyone skips, and the only one that compounds. Skip it and Monday starts by rebuilding context instead of using it.
What to ask
- What actually shipped or closed?
- What did we learn that changes next week?
- What carries over, and why specifically?
Where it breaks: “Why specifically” is doing all the work in that last question. “Ran out of time” is not a reason, it is a summary. If an item carries three weeks running and the reason is different every time, the item is wrong — not the week.
The five numbers that tell you it is working
A cadence can look immaculate and be theatre. Everyone attends, nobody lies outright, and the work still slips a week at a time. These are the signals that catch it before the quarter does. The workbook computes all five off your board and flags them against thresholds you can tune.
| Signal | Flags at | What it means when it is off |
|---|---|---|
| Carryover rate | Above 40% | Share of live work already older than a week. Past 40% your weekly plan is fiction and everyone in the room knows it. Halve what you commit to for three weeks and let people feel what finishing is like. |
| Oldest block | Older than 7 days | A block that survives a week is not a block. It is a decision nobody wants to make, wearing a block for cover. Escalate it to whoever can actually decide, or kill the item. A third option is not available. |
| Blocked with no date | Anything above zero | The fastest thing here to fix and the most revealing that it needed fixing. A block with no unblock-by date is a block nobody has agreed to own. |
| Record lag | More than 2 days | Days between something finishing in reality and the board finding out. This is the number that decides whether you have an operating view or a newsletter. Under a day, or it is decoration. |
| Days silent | More than 14 days | Untouched for a fortnight. Nobody paused these. They died, and they are still taking up room in everyone’s head. Abandoning things on purpose is allowed — abandoning them by accident is what costs you. |
Six ways this dies
None of these are discipline problems, which is why telling people to try harder has never once fixed them. Each is the rhythm being used for something it was not built to do, and every one is survivable the moment somebody names it out loud.
| Symptom | What it actually means | The fix |
|---|---|---|
| Nothing is ever blocked | Everyone is being polite. Status is getting reported; risk is not. | Ask what will be stuck by Friday, not what is stuck now. Future problems are far easier to admit than present ones. |
| The same item is blocked three weeks running | It is not blocked. It is dead, and nobody wants to be the one to say so. | Force it to a decision with a named person and a date, or delete it. A third week is a choice you are making. |
| The touch always runs long | You are doing project management in a slot built for surfacing, and boring four people to do it. | Surface and assign in the touch. Solve somewhere else, with only the people involved. |
| The board gets updated after the meeting | The mechanism is broken. You have a meeting with homework, and homework does not get done. | Update live, in the room, or do not hold the touch at all. This is the one rule with no exceptions. |
| High carryover, but everything is “on track” | The estimates are fiction and the room has quietly agreed not to mention it. | Cut the weekly commitment in half for three weeks. Nothing rebuilds honesty faster than finishing things. |
| Only the founder talks | This is a status report to the founder wearing a cadence costume. | The founder answers last, or skips it for a month. The rhythm has to survive without them — that is the entire point of building one. |
The first four weeks
Starting all three touches at once is the most reliable way to kill this in a fortnight. Adoption is the constraint, not the design. Add one at a time and let each become boring before the next arrives.
Week 1
Monday only
Just surface. Fix nothing, assign nothing. Expect it to be ugly and let it be — the first honest list is the whole deliverable.
Week 2
Add Friday
Start recording outcomes. Still no Wednesday. Two touches is enough to feel a loop close for the first time.
Week 3
Add Wednesday
Now the loop is complete. This is the week people start clearing blocks before the touch, which is the behaviour you were actually buying.
Week 4
Start measuring
Your first honest carryover number. It will be worse than you expect. That is a baseline, not a verdict.
When to loosen it
Three touches is a starting position, not a personality. A cadence that never loosens is overhead with good manners, and people stop showing up to good manners. Earn your way down — and be willing to go straight back up.
- Carryover under 25% for four straight weeks and no block has gone undated.
- Average record lag a day or less for six weeks and nothing has gone silent.
- The moment carryover clears 40% two weeks running. Loosening is reversible, and treating it that way is what stops it becoming a status symbol.
What is in the workbook
- Start Here
- The legend, the colour convention, and the one rule the whole thing rests on. Two minutes.
- Discovery
- Twenty questions, once, before you start: the outcome, the non-goals, who decides what, the binding constraint, and where the record actually lives today. Each one carries the reason we ask it, so it orients you rather than reading like an intake form. It also works out what your recurring meetings cost in person-hours a year, which is usually the number that ends the debate.
- Board
- One row per item in flight. You fill nine columns; five more calculate weeks carried, block age, record lag, days silent, and a plain-language flag naming the worst thing about that row.
- Health
- Reads the Board and returns nine signals, each with an OK or a CHECK against your thresholds. This is your Wednesday agenda, computed rather than remembered.
- Trend
- Five numbers off Health, once a week, pasted as values. It tells you whether last week was better or worse and on which axis. One week is noise. Four weeks is a shape.
- Thresholds
- The numbers Health judges against, each with the reasoning written beside it. Tune them once you know your own baseline — but loosening every threshold until nothing flags is not tuning, it is turning the smoke alarm off.
- Weekly Log
- One row per touch. Thirty seconds to fill in, and it is the reason next Monday is fast.
- Decision Log
- What was decided, by whom, why, and what would make you revisit it. The sheet that stops the same block resurfacing in three weeks wearing a new name.
- Snapshot
- The one you send back to us. Most of it fills itself in.
It ships with four example rows so Health has something to chew on and you can see what a flag looks like before your own numbers start doing it to you. Delete them before you start.
After four weeks, send it back
The last sheet is Snapshot. Nine of its values fill themselves in — six off your board (carryover, oldest block, record lag, blocked with no date, items silent, items flagged) and three off your Discovery sheet (what you said good looks like, the binding constraint, what your meetings cost). Three boxes ask what no spreadsheet can work out: who runs it, what is still not working, and what you want to be true in ninety days.
Fill those in and email the file to connect@cnnctd.work. We read it before we talk, so the first conversation starts from your real numbers instead of an hour spent reconstructing them out loud. You will also have already done the part most discovery calls are secretly for.
And if the numbers say your cadence is holding, we will tell you so and go away. That happens more than you would expect. We would rather lose the call than sell you a system you have already built.
This is the operating half of Discipline Stacking. The reasoning behind keeping the record current in the same pass as the work is Closed-Loop PM.
The other two
Three tools, three failures that feel identical from the inside — the vague sense that everything takes longer than it should. Worth knowing which one you actually have, because the fixes have nothing in common.
The Founder Dependency Audit
How much of the business runs through one person, and how long you could vanish before anybody outside noticed.
Workbook and field guide →
Measures ForesightThe RAID Log
Whether anything that goes wrong was ever anticipated, or every problem arrives as a surprise and gets handled well.
Workbook and field guide →
All three are free, ungated, and listed at the toolkit index.

This is free because the artifact was never the hard part.
Running it for eight weeks when it is inconvenient is the hard part. So is being the person who reads the carryover number out loud when it says 60%. If you want someone in the room while that becomes normal — and while nobody much enjoys it — that is the work we do.