Bureaucracy
Source: https://archive.org/details/economyandsociet00webe ↗
The foundational analysis of bureaucracy as a technology of coordination, not a pejorative.
Weber described an ideal type: hierarchical authority, written rules, specialised roles, impersonal procedures — a machine for making decisions predictably at scale.
Every org chart, every process document, every compliance framework descends from this analysis.
The insight that bureaucracy is rational precisely because it depersonalises power is uncomfortable but necessary: most contemporary critiques of "bureaucracy" attack symptoms without understanding the problem it was designed to solve.
For product people working inside large organisations, Weber explains the machinery they inhabit.
Read the bureaucracy chapters, not the full thousand-page treatise.
Central argument
Weber argues that bureaucracy is not a dysfunction but the most technically efficient form of organisation ever devised: its defining features — hierarchical authority, written rules, specialised roles, and impersonal procedures — are precisely what make large-scale coordination rational and predictable. The key thesis is that bureaucracy depersonalises power, replacing arbitrary rule by individuals with rule by office, which is both its strength and its irreversibility. Once established, bureaucratic structures are nearly impossible to dismantle because they serve the interests of those who administer them and the organisations that depend on their stability.
Critique
Weber's ideal type is descriptive and structural, but it largely brackets the question of what bureaucracies are for — it analyses the machinery without interrogating whether the goals the machinery pursues are legitimate or adaptive. This is a significant blind spot: an organisation can be perfectly bureaucratic in Weber's sense and still optimise for its own perpetuation rather than its stated purpose, a failure mode Weber's framework cannot easily diagnose. The model also underweights informal power, culture, and the ways real organisations deviate from the ideal type in ways that matter enormously in practice.
Why it matters for product
For a CPO inside a large organisation, Weber explains why process accumulates with such apparent logic — every compliance layer, every approval gate, every RACI matrix is a rational local response to a coordination problem, which means attacking them as irrational bureaucracy usually fails. The more productive intervention is Weber's own: treat structure as a design problem, not a moral one — ask what coordination problem each layer was built to solve, and whether that problem still exists at the same scale or urgency. This reframe also disciplines how product leaders design their own team structures: specialised roles and written procedures are not the enemy of speed, but their design determines whether the machinery serves the product or the machinery serves itself.