Open Standards and the Digital Age
Russell traces the history of technical standards from the telegraph era through the internet, showing that "openness" has never been a stable or self-evident concept.
What counted as open in AT&T's world was closed in the IETF's, and what the W3C calls open today would puzzle engineers from the 1960s.
The book reconstructs the institutional battles — IEEE, ISO, IETF, corporate consortia — that gave the word its shifting political charge.
Russell demonstrates that standards are not neutral technical artifacts but sites of power where market structure, ideology, and engineering culture collide.
For anyone building products on top of open protocols or open-source ecosystems, this book supplies the history behind the language you already use.
It is the best single volume on why "open" means something different to everyone who invokes it.
Central argument
Russell argues that 'openness' in technical standards has never carried a fixed meaning but has been continuously redefined through institutional conflict among bodies like the IEEE, ISO, IETF, and corporate consortia. What AT&T considered open in the telegraph and telephony era was experienced as closure by the engineers who built the internet, and the W3C's conception of openness again differs from both. Standards are therefore not neutral coordination mechanisms but contested political artifacts where market power, engineering ideology, and organizational interests collide to determine who controls the infrastructure of communication.
Critique
The book's focus on North American and Western European institutions — AT&T, IEEE, IETF, W3C — risks presenting a particular geopolitical lane of standards history as if it were the whole story. By 2014, bodies like China's MIIT and the dynamics around competing national standards (TD-SCDMA, WAPI) were already significant, and the absence of that dimension leaves the analysis of power in standards-setting incomplete. A reader could reasonably ask whether the political charge Russell attributes to 'openness' looks the same when the institutional actors are not Anglo-American.
Why it matters for product
A CPO building on open protocols or open-source ecosystems — deciding, say, whether to contribute to a standard, fork a library, or join a consortium — is making a political choice about market structure, not just a technical one; Russell's history makes that power dimension legible and therefore manageable. More concretely, when internal stakeholders or partners invoke 'open' to justify an API strategy, a data-sharing arrangement, or a platform governance model, understanding that the word is a site of contested authority rather than a shared definition helps a product leader spot whose interests are actually being served before the architecture is locked in.