What Is a CTO Operating Rhythm?

By Gareth Price · Last updated

A survival system, not a productivity system

In short: A CTO operating rhythm is a set of recurring activities at daily, weekly, monthly, quarterly and annual cadences that gives the CTO role the structure it lacks. In Gareth Price’s Applied Alchemy every activity has a trigger for when to delegate it and a warning sign that it is being neglected, so the urgent cannot consume the important.

Five Loops, Each With a Trigger and a Warning Sign

Chapter 14 sets out the rhythm as loops at five frequencies:

  • Daily, small enough for an index card: a morning launch, one 90-minute deep work block, a CEO check-in, triage and capture, and a shutdown ritual.

  • Weekly: one-to-ones with every direct report, an architecture review, an incident review, an engineering leadership meeting, a recruiting pipeline review, a written status update and a Friday review.

  • Monthly: a technical debt review, a team health check, skip-level conversations, an advisory conversation and an engineering all-hands.

  • Quarterly: goal review, architecture review, a technology strategy refresh, board preparation and a personal energy audit.

  • Annual: an organisational assessment, a technology roadmap refresh, the budget negotiation, and career development and succession planning.

The rhythm accumulates as the company grows. A Coder-stage CTO runs a subset. A Strategist-stage CTO runs the full set, with most operational cadences handed to a VP of Engineering. A delegation ledger records, for each activity, the stage or team size at which it moves from "you do it" to "you ensure it happens". Some activities never move: the CEO relationship, technology strategy, advisory conversations and the shutdown ritual.

Why It Matters

The CTO role has no natural structure. Engineers have tickets. Sales has a pipeline. Product has a roadmap. The CTO has everything, all at once, with nothing external saying what comes next. They also live across Paul Graham’s two schedules, where "a single meeting can blow a whole afternoon."[1]

If you do not decide what you are doing with your time, other people’s urgencies decide for you. The rhythm makes that decision once, in advance, rather than fifty times a day under pressure. Its most important daily element is Cal Newport’s shutdown ritual, which deals with the way unfinished tasks dominate attention.[2]

Example: A Rhythm Built as a Prosthetic

Chapter 14 opens with the author’s own story. Diagnosed with inattentive ADHD at thirty-four, he had spent his career building compensatory systems without knowing what they compensated for: obsessive lists, time-blocked calendars, notes on everything. The rhythm in the book is the system he built, broke and rebuilt over a decade as a startup CTO.

The book is clear that this is not only for ADHD readers. The role is hostile to executive function whatever your neurology. A CTO without ADHD may need three daily steps where another needs five. The principle is the same.

How to Start This Week

  1. Write the daily five on an index card and tape it to your monitor.

  2. Run the shutdown ritual every working day at the same time. Scan every task list, check the next three days, write tomorrow’s three outcomes, note one thing that went well, say a closing phrase aloud, and close the laptop.

  3. Block one 90-minute deep work session in your sharpest hours. No Slack, no email.

  4. On Friday, send your first weekly status update to the CEO and peer executives. Will Larson’s "5-15" format takes fifteen minutes to write and five to read.[3]

  5. Start a delegation ledger. For each activity you run, write the trigger that will hand it off, and mark the ones you will never delegate.

Operating Rhythm vs Time Management

Time management fits tasks into hours. An operating rhythm decides in advance which recurring activities happen at which cadence, who owns each one at each stage, and what tells you one has slipped. It is not a rigid calendar; a startup system that assumes predictable weeks will be abandoned by Thursday. It changes as you move through the four stages. And it is increasingly shared with AI. The book’s rule for that split: automate the assembly, assist the analysis, protect the relationships. The one-to-one, the strategic bet and the board narrative stay human.

Go deeper: Chapter 14: The Operating Rhythm, with the printable tables in Appendix F: The Operating Rhythm — Quick Reference and what happens without it in Chapter 15: Burnout and Isolation. See also What Is the Maker-to-Multiplier Shift? and What Are the Four Stages of a Startup CTO?

Frequently Asked Questions

  1. What is a CTO operating rhythm?

    A CTO operating rhythm is a set of recurring activities at daily, weekly, monthly, quarterly and annual cadences that gives the CTO role the structure it lacks. In Applied Alchemy each activity has a trigger for when to delegate it and a warning sign that you are neglecting it, so the urgent cannot crowd out the important.

  2. What should a CTO’s daily routine include?

    Five things that fit on an index card: a 15-minute morning launch before email or Slack, one deep work block of at least 90 minutes, a short CEO check-in, triage and capture of every input into a system, and a 15-minute shutdown ritual at the same time each day. The shutdown ritual is the most important of the five and the one most likely to be skipped.

  3. What is a shutdown ritual?

    A shutdown ritual is a 15-minute end-of-day routine, from Cal Newport, that closes the open loops your brain would otherwise chew on at night. Scan every task list, check the next three days, write tomorrow’s three outcomes, note one thing that went well, say a closing phrase aloud and shut the laptop.

  4. What should a CTO delegate first?

    Delegate by triggers you decided in advance, not by mood. Applied Alchemy suggests handing first-pass triage to an executive assistant at about 15 engineers, most one-to-ones to a VP of Engineering once one is hired, and incident reviews once a VP of Engineering or SRE lead can run them. Some things are never delegated: the CEO relationship, technology strategy, advisory conversations and the shutdown ritual.

  5. Can AI run a CTO’s operating rhythm?

    Partly. The book estimates that about 40% of the rhythm can be automated and another 35% assisted, leaving 25% that must stay human. Its rule is to automate the assembly, assist the analysis and protect the relationships: AI can draft the weekly update or prepare a one-to-one, but it should not conduct the one-to-one, make strategic bets or own the board narrative.

References

1. Graham, P. (2009, July). Maker’s schedule, manager’s schedule. paulgraham.com. https://paulgraham.com/makersschedule.html
2. Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing. Shutdown ritual: https://calnewport.com/drastically-reduce-stress-with-a-work-shutdown-ritual/
3. Larson, W. (2023, January). Meetings for an effective eng organization. Irrational Exuberance (lethain.com). https://lethain.com/eng-org-meetings/ — Chapter from The Engineering Executive’s Primer (O’Reilly, 2024). Six core meetings; 5-15 update format; skip-level budget of 1–2 hours/week.