Why this is in the vault
Part III of "The CFO Operating System" turns last week's Four Es typology into an actual 5-step operating rhythm (buckets → inventory → cadence → batch → block) with a concrete numeric guardrail — only ~50% of time on the fixed "Everyday" bucket — and a deliberately quarterly-not-weekly 1:1 cadence that independently lands on a position RDCO already holds.
Mapping against Ray Data Co
The sharpest hit: the author deliberately runs 1:1s with direct reports quarterly rather than weekly once a report is established, arguing fixed-cadence check-ins are an inefficient leadership default; he tightens to weekly only for new hires (3-6 months) and is explicit that quarterly only works if he is genuinely available otherwise — which independently confirms [[feedback_channels_are_bidirectional]]'s existing stance that RDCO channels run on no scheduled "1:1" rituals, questions asked inline as they arise. Two different domains (CFO org design vs. an AI-COO comms model) converging on the same anti-ritual argument, each conditioned on real availability rather than ritual alone, is worth banking as corroboration, not coincidence.
Secondary mapping: the 5-step rhythm itself is a vocabulary upgrade for how RDCO's own cadence is already organized, continuing the Four Es throughline the Part II note flagged. Define buckets, inventory the everyday, set cadence, batch, block maps onto the existing cron skill set (morning-prep, check-board, open-threads-check as the "Everyday" bucket; /improve and self-review as protected "Evolution" work). The piece's one genuinely new number is a guardrail neither Part I nor Part II supplied: cap Everyday at roughly 50% of total capacity, reserving the rest for Events/Emergencies/Evolution — a concrete value to check RDCO's cron/skill load against if that audit ever gets run, though no such audit is proposed here.
The "AI-assisted self-audit" idea (feed your own calendar/email/notes to an AI to reconstruct your actual operating rhythm) is notable mainly as a capability description: it is literally the kind of synthesis task Ray is built to do. But it describes the founder's personal time allocation, which is advisor territory, not something to pitch unprompted.
The core argument
Opens with Eliyahu Goldratt's The Goal and its Theory of Constraints (optimize the system, not the parts; find and protect the bottleneck; don't chase 100% utilization everywhere) plus an Elon Musk clip on constraint-focused prioritization, then imports the same logic onto a CFO's own attention: "The greatest constraint in your personal operating system, as CFO, is your own attention." The fix is a 5-step operating rhythm. Define buckets: group all responsibilities into 4-7 areas rather than tracking tasks individually. Inventory your Everyday: list every recurring inbound/outbound obligation per bucket. Set the cadence: match frequency and format to each obligation — including a deliberate break from convention on 1:1s (quarterly, not weekly, is the default; tightened only for new hires). Batch ruthlessly: group similar work into blocks rather than scattering it (the author's own pattern: a 2-day monthly review block, a fixed Tuesday-AM weekly slot). Block it out: calendar-protect the rhythm so it survives contact with the week. Acknowledging the idealism, he reframes the rhythm as a "default operating state, not a prison" that absorbs disruption rather than guaranteeing against it, and closes with his own ~30-minute "Sunday reset" ritual (rebuilding tasks into Do Now / Do Soon / Do Later) as the lightweight meta-process that keeps the rhythm honest. Previews Week 4 on information and decision flow.
⚠️ Sponsorship
Sponsor: Campfire (ERP, enterprise resource planning/close automation) — same disclosed sponsor as Parts I and II, continuing the pattern that this series runs on a single sponsor rather than rotating through the broader CFO Secrets pool (Zip, Pulley, Stuut, Una, Ledge, Summation, Nominal, CloudZero, Aleph, Numeric, Airwallex). This is the author's standing, openly-disclosed investor/user relationship (first flagged 2026-05-11), not a clean arm's-length third-party ad — treat the framing ("Campfire have answers to the tough implementation questions you can take into the boardroom") accordingly. Appears twice: once as a mid-issue sponsored block built around ERP-implementation-risk setup copy, once in the closing "Thank you to our sponsor" footer.
Related
- [[2026-10-10-secret-cfo-four-es-cfo-operating-system-ii]]
- [[2026-10-03-secret-cfo-altitude-sickness-cfo-operating-system-i]]
- [[feedback_channels_are_bidirectional]]
- [[feedback_targeting_system_prioritization_filter]]