Become a better CTO, faster.

Running a technology organisation is mostly ambiguous work. Should you build it or buy it? Is the platform team a real team or a bottleneck? What do you tell the board about technical debt, and what do you actually do about it on Monday? The answers exist, but they are scattered across half-remembered conversations, a decade of blog posts and whatever framework you happened to read last.

The Art of CTO turns that work into something repeatable: clear frameworks, 76 interactive tools that take you from a blank page to a defensible answer, and writing that takes a position rather than listing considerations. You should be able to arrive with a problem and leave with a decision you can defend.

The tagline is the whole thesis: building systems, leading people. Most CTO material does one or the other. The job is both at once.

Specifically: CTOs, technology executives, and senior technology leaders preparing for their first CTO role. If you are accountable for technology decisions that other people have to live with, this is aimed at you.

That focus is deliberate, and it is also a constraint. Material written for “engineering leaders” in general ends up written for nobody in particular — pitched to the newest reader in the room and useless to anyone with real scope. Everything here assumes you have the scope and are short on time.

The best free thing here is the tools. Every one of them is free and needs no account. Start with the 76 tools →

A CTO audience can smell generated filler at fifty paces, so here is the honest version rather than a disclaimer buried in the terms.

• Articles are drafted with AI and reviewed by a person before they publish. Nothing reaches the site as a draft. A human reads it, edits it, and releases it — or it stays unpublished. Every article that involved AI carries an AI-assisted badge, on the page, next to the byline.
• The Daily Sync is the one exception, and it says so. It is synthesised from the day’s sources and published automatically, so its badge reads “published automatically” rather than “reviewed by a human editor”. Its sources are linked inline so you can check the original.
• The tools are built, not generated. Each one is hand-written code with its logic stated on the page. Where a tool leans on reference figures rather than live data — the compensation benchmark, for one — it says so on the tool, with the as-of date, so you know whether you are looking at a starting point or a source.
• Numbers are counted or cited, never rounded up for effect. The tool count on this page is read from the tool registry at build time rather than typed in. It is a small thing, and it is the same discipline applied everywhere else.

If you find something wrong, tell us and it gets fixed and dated. Corrections go here →

Everything above is free and always will be. When a decision needs more than a framework can carry, there is a separate advisory practice — from fractional strategic input to acting CTO engagements, depending on what the stage needs.

Prefer it to come to you? The newsletter carries the week’s best of it, and the RSS feed carries everything.

Got a decision of your own worth writing up? Contributions are open →