Weaving the Web
Source: https://www.harpercollins.com/products/weaving-the-web-tim-berners-leemark-fischetti ↗
The story of the World Wide Web told by its creator.
The most relevant thing is not the technology but Berners-Lee's insistence that there was no grand plan — only a problem to solve (sharing information between CERN researchers) and a spirit of openness.
The web was not designed top-down; it was woven. Berners-Lee actively resisted centralising and privatising the protocol.
Essential reading for the narrative thread that the deepest transformations often arise without a plan, driven by necessity and curiosity — and that keeping them open is itself a design choice.
Central argument
Berners-Lee argues that the World Wide Web succeeded not because of a master plan but because it was designed around radical openness: no central authority, no proprietary lock-in, and no single point of control. He contends that the key technical decisions — using open protocols, making the spec freely available, resisting pressure to commercialize the standard — were themselves moral and political choices, not merely engineering ones. The web's power came from what it allowed anyone to do without asking permission, and Berners-Lee frames defending that openness as an ongoing obligation, not a historical footnote.
Critique
Berners-Lee's account is inevitably autobiographical, which creates a blind spot around the institutional scaffolding — CERN's resources, the existing internet infrastructure, the academic culture of the early 1990s — that made his particular form of openness possible and that most builders simply do not have access to. His argument that openness is the default-correct design choice can feel under-examined when confronted with the actual web that emerged: one dominated by a handful of platforms whose network effects achieved the centralization he sought to prevent, suggesting that open protocols alone are insufficient without governance mechanisms he doesn't fully theorize.
Why it matters for product
For a CPO, the most actionable provocation in this book is that the architecture of a system encodes a theory of power: deciding who needs permission to build on or extend your product is not a technical question but a strategic and ethical one that determines long-term ecosystem dynamics. Berners-Lee's resistance to privatizing the protocol is a concrete precedent for thinking about API openness, data portability, and platform governance — choices that are often deferred as secondary to feature delivery but that structurally shape what the product can become. Teams that treat interoperability as a compliance checkbox rather than a design principle tend to optimize for short-term retention while foreclosing the network effects that compounding platforms are built on.