Where this comes from.
Runboard is one idea about the CTO job, distilled from years of running real technical organisations — not theory from a whiteboard.
What Runboard is
Runboard is an operating model for technical leaders. It rejects the idea that the job is a checklist, and replaces it with a single thesis: velocity in a direction is the outcome, not the job. The team supplies the speed; your work is the balance and the structure that keep it pointed the right way and moving faster than the problems can pile up — and the measurement that tells you it’s working.
Everything here is that one idea, worked through: the manifesto for the why, the framework for the shape, and three engines for the how.
Drawn from a working practice
Runboard isn’t invented. It’s the distilled pattern that kept showing up across a working fractional-CTO practice — the same handful of weak spots, the same handful of cures, in company after company. That practice is 2 Lines Software, the fractional-CTO work of John Carpenter.
The practice is the origin, not the subject. Runboard is the general operating model the pattern points to — not a case study of one firm.
What’s left when you strip the client specifics is the part that generalises: the structure of the problem, and the moves that reliably fix it.
What the name means
the operating verb, and the centre of the Build / Run / Plan grammar.
the dashboard you steer by, the measurement made literal. It’s also the board you answer to.
the conviction that AI’s highest-leverage use in a technical organisation is measurement: making it cheap to see.
It points at where this is going, too. Today Runboard is the methodology — the thinking, the writing, the framework. The name also names the destination: an actual board for running your technical organisation, the readiness-and-velocity dashboard the framework prescribes. Thinking first, instrument later.