On 29 November 1814, the owner of The Times walked into a room of printers preparing the day's hand presses. He showed them a copy already printed and announced: "The Times is already printed — by steam."

The newspaper itself described the new machine as "a system of machinery almost organic." And then: "little more remains for man to do, than to attend upon, and watch this unconscious agent."

I recently read News Machines by Dallas Liddle — an academic history of how Victorian newspapers evolved from folded sheets into what contemporaries called "the daily miracle." His argument is structural: as demand outpaced production capacity, newspaper organisations built complex systems to keep growing. Each mechanism solved a bottleneck. Each solution created dependencies. And at some point, the decisions about what journalism should look like stopped being editorial choices and became systemic necessities.

The infrastructure was not serving the editors. The editors were serving the infrastructure.

Anyone directing digital products has felt this. The roadmap discussion that feels strategic but is really determined by accumulated technical debt. The feature that ships because the architecture made it the path of least resistance. The org chart that was meant to reflect the product but now the product reflects the org chart.

The most useful reading for product directors is not product management literature. It is history, economics, and the social sciences — works that analyse how systems acquire agency over the people who built them. Liddle's dynamics are not Victorian. They are structural.

Good history makes the familiar strange. And for anyone making decisions inside systems that quietly make decisions for them, that estrangement is a professional necessity.