Jacques Ellul The Technological Society

Why Your Entire Workflow Feels Inescapable Now

You've probably noticed something odd about how you work these days. You didn't choose the tools that organize your week. You didn't select the algorithms that surface your content. You didn't even pick most of the platforms you use. They arrived around you like weather, and now you're just working inside them. Jacques Ellul understood this before any of us had a smartphone, and he wrote about it in what most people just call Jacques Ellul The Technological Society — though the actual title is "La Technique ou l'enjeu du siècle," published in 1954. Ellul's argument is simpler than people make it sound. He wasn't saying technology is bad. He was saying technology has become self-augmenting and autonomous. It no longer serves human ends — human ends now serve technology. The system drives itself toward maximum efficiency, and everything else gets rerouted around it. What he called "la technique" wasn't just machines or digital tools. It was the totality of methods that achieve a predetermined result with maximum efficiency across every sphere of life. The word technique in French is broader than the English translation usually allows. It covers administrative procedures, pedagogical methods, software frameworks, corporate workflows, anything that can be optimized. Once a domain becomes technical, it stops being a choice and starts being a requirement. Not because anyone forced you, but because the alternative becomes invisible.

What Beginners Miss About Ellul's Argument

Most people read Ellul and think he's predicting some dystopian future where machines enslave humanity. That's not what he's saying. The automation happened quietly, decades ago, and we're just now feeling the shape of it. His real insight is about technical rationality — the mindset where the question is never "should we do this?" but only "can we do this efficiently?" Once that frame takes over, moral and political questions get filtered out automatically. They become noise. You don't notice because the questions that get asked are always the ones technology can answer. Here's a practical example I ran into directly. I was advising a mid-size logistics company on their operational setup. They wanted to implement a new routing optimization system. Standard enough request. But when I dug into what the system actually optimized for, it turned out the algorithm prioritized route density over driver shift boundaries, compliance breaks, and even basic customer time windows. It produced mathematically optimal routes that no human dispatcher would ever approve. The system was doing exactly what it was designed to do. Nobody had asked if it should be designed that way. The efficiency logic had filled the room before anyone raised a question about outcomes. I spent three weeks redefining the constraint set before the system became usable, and even then, management pushed back hard because the "optimal" scores looked worse. That's Ellul in practice. The technique decides what counts as a valid problem.

How to Actually Apply This Thinking

You don't need to read everything Ellul wrote to use his framework. Start by mapping where technical rationality has replaced judgment in your own environment. Look for moments where someone says "the data says" and the conversation stops. Those are technical rationality closing a decision loop. The method is to treat that moment as an intervention point, not a conclusion. Ask what the optimization function is actually measuring, what's being excluded from the calculation, and who benefits from the current framing. This isn't about Luddism. Ellul himself was careful about that. The point is recognition first. Once you see the system operating, you can work within it deliberately rather than being operated by it unconsciously. It changes how you approach tool selection, how you structure team decisions, and how you evaluate claims that something is "just the way things work now."

Where This Framework Falls Short

There are legitimate limits to Ellul's analysis that you should be aware of. His model doesn't account well for resistance, adaptation, or the ways people routinely bend technical systems toward their own ends. Workers find workarounds. Teams develop informal practices that contradict official procedures. Users hack tools into shapes the designers never intended. Ellul treated technique as almost monolithic, and that glosses over the friction that exists in practice. If you apply his framework rigidly, you'll miss the very spaces where human agency actually operates. There's also a gap regarding power. Ellul talks about technique as if it has its own will, but technique doesn't emerge from nowhere. It's built, funded, and deployed by institutions with specific interests. Blaming "the technological society" can accidentally absolve the people who made the choices. A more useful lens combines Ellul's structural analysis with attention to institutional incentives and accountability. If you want to go further after the main book, his later multi-volume work "La Technique et le Temps" expands the argument into philosophy of time and embodiment, but it's denser and less directly applicable. For practical purposes, start with the 1954 text, read it straight through without skimming, and then return to the chapters on propaganda and economics with your own work context in mind. You'll see the patterns immediately.

Resources for Jacques Ellul The Technological Society

The original French edition is available through academic publishers, but the standard English translation by Charles Kivel and Arthur Koestler was published by Gramercy Books. Some libraries carry the Vintage edition as well. If you want the extended analysis, the later volumes on "La Technique et le Temps" are available through Stanford University Press. I'd recommend reading the primary text before any secondary summaries. Ellul's writing is dense but precise, and interpreters often smooth over the nuances that matter most. The main thing to take away is that technique isn't a collection of tools. It's a logic that reorganizes everything it touches. Once you've seen that distinction, you won't unsee it.