The Technological Society
Source: https://archive.org/details/technologicalsoc0000ellu ↗
Ellul's central claim is that technique — the ensemble of means oriented toward efficiency — has become an autonomous system that shapes human ends rather than serving them.
The argument is extreme and deliberately uncomfortable: technology is not neutral, it is a totalising logic.
For product direction the book is a cold shower — it forces the question of whether "optimising" is always the right verb, and whether efficiency without purpose is just acceleration toward nothing.
Central argument
Ellul argues that 'technique' — not technology as hardware, but the totalising drive to find the one best method for every human activity — has become an autonomous, self-augmenting system that operates beyond human control or moral direction. Crucially, he contends that technique is not a neutral tool subordinate to human ends; it colonises those ends, redefining what counts as a good outcome in terms of measurable efficiency. The result is a civilisation that optimises relentlessly without being able to ask, from outside the system, what any of it is for.
Critique
Ellul's argument gains force from its totality, but that totality is also its principal weakness: by treating technique as a monolithic, self-determining logic, he leaves almost no analytical room for human agency, institutional resistance, or the historical cases where communities have selectively adopted or refused technical systems on their own terms. The determinism is so complete that the book struggles to explain variation — why some technologies diffuse and others do not, or why different societies have embedded the same tools with meaningfully different values. A reader sympathetic to the diagnosis may still find the framework too sealed to be practically generative.
Why it matters for product
For a product leader, the most pointed provocation is the possibility that the standard metric stack — activation rates, retention curves, engagement loops — does not measure product value so much as it constitutes it, quietly replacing the original human problem with whatever the instrumentation can optimise. Ellul's lens makes it worth auditing whether the discovery process is genuinely interrogating user needs or is itself a technique that systematically surfaces only the problems amenable to the solutions the team already knows how to build. The discomfort is productive: it pushes toward asking whether 'ship faster, learn faster' is a strategy or just acceleration dressed as one.