The Operator's Notebook
A few rules I keep coming back to for running systems and the teams that run them.
I’ve spent most of my career as an operator — the person who turns a good idea into a thing that runs on a Tuesday when everyone’s tired. It’s unglamorous work and I’ve come to love it. Here are a few rules I keep returning to.
Make the system legible
If you can’t explain how the thing works on a whiteboard in five minutes, the thing is too complicated, or you don’t understand it yet. Usually both. Legibility is not a nice-to-have; it’s the precondition for anyone — including future you — being able to fix it at 2am.
Optimize for the boring day
Demos optimize for the best day. Operators optimize for the median one. The question isn’t can this work — it’s does this keep working when nobody’s watching and the intern is on call.
Trust is the real throughput
Every handoff between people is a place where work either accelerates or stalls. The teams that move fastest aren’t the ones with the best tools. They’re the ones where people don’t have to re-litigate trust on every decision.