Operating cadence
Domain 03 of the eight in the NBOP standard. This page explains what the domain is and how it fails. It does not say how much the domain is worth, because that has not been decided yet and will not be decided here.
Its number in the published standard, which is an order rather than a ranking.
The standard is at version 0.9. The weight of this domain is not set.
Domains you need personal accountability in to be eligible. This is one of the eight.
The standard an assessment is built from, readable in full, permanently.
What the standard says
The meeting, review, and planning rhythm that keeps an organisation aligned. Designing cadence proportionate to the size and volatility of the business rather than importing a framework wholesale.
That is the whole of the published entry. Everything below expands it and is not itself the standard. Where the two ever disagree, the standard is the document that governs.
What this domain is
Operating cadence is the rhythm at which the business looks at itself and decides something. It is not the calendar, and it is not the meeting list. It is the loop: how often the organisation observes its own state, how often it decides, and therefore how long a bad decision can run before the next look catches it.
That last number is the one that makes cadence an operations problem rather than a scheduling one. A quarterly review sets a maximum error duration of a quarter. If the business can lose a quarter, that is fine. If it cannot, no amount of meeting quality will help.
What it looks like when it is working
- The interval matches the volatility. A business whose numbers move weekly is not reviewed monthly.
- Every recurring meeting has a decision right attached to it and a named person who holds it.
- Meetings end with something changed, and it is written down where the people affected will see it.
- There is a visible route for a decision that cannot wait for the next cycle, and it is used rarely enough to still mean something.
How it fails
The common failure is cadence imported wholesale. A twelve person company runs quarterly objectives, a fortnightly ceremony and a monthly business review, inherits the meeting load of an organisation ten times its size, and gets the alignment of neither.
The second is a cadence that reviews without deciding. The rhythm is real, attendance is good, the pack is produced, and nothing is ever settled inside the room, so the same item returns to the same meeting for a year.
Why competent operators miss it
Because every ceremony is individually defensible. Each one has a sponsor who can explain why it exists and what it protects. The cost only appears in aggregate, in hours that never appear on any budget line, and nobody owns the aggregate. Removing a meeting requires an argument against a named person; adding one requires nothing.
What accountability here actually means
Eligibility for NBOP-CP asks for personal accountability in at least four of the eight domains. Personal is the operative word. Having worked somewhere that did this well is not accountability, and neither is having been consulted. The test is whether the decision was yours to make and yours to answer for.
For this domain, that looks like at least one of the following.
- You set an interval and defended it against a framework somebody wanted to import.
- You have removed a recurring meeting.
- You have changed a review cycle because the business changed, and can say what changed.
What NBOP does not claim about this domain yet
Not how much it is worth. The weight of each domain is being set by a job task analysis of practising operators, rating tasks on criticality and on frequency, and the weights are derived from those paired ratings rather than from editorial preference. Until that closes, the standard states equal provisional weighting and says so on its face.
Not what an assessment will ask about it. The examination blueprint follows the analysis. Publishing an item count now would mean inventing one and quietly changing it later.
Not that this description is finished. Version 0.9 is a draft and is expected to change materially before ratification. If you hold operational responsibility and think this domain is described wrongly, that is the input worth having.
The eight domains
Each governs a different part of how an operation is run. They are numbered for reference, not for importance.
Set the weight of this domain
The weighting is decided by operators rating the work, not by NBOP deciding what matters.
The analysis is open now. It takes about twenty minutes, because every task is rated twice, and the results are published in aggregate including the findings that contradict the current draft. If you have held operational responsibility, your rating counts toward the weight this domain ends up carrying.