Inevitable: Understanding the 12 Technological Forces That Will Shape Our Future — Twelve Forces, Six Worth Your Time

So it's 11:30 PM on a Tuesday, I've just survived a gnarly incident review for a cascading failure in one of our storage services, and I'm lying in bed doom-scrolling when I remember I never wrote up my thoughts on this one. Kevin Kelly's Inevitable has been sitting in my "finished" queue for two weeks now, and honestly? My feelings are... complicated.

TL;DR: Worth your commute, but at 1.75x. This is basically a Wired magazine feature series stretched to book length - sometimes brilliantly, sometimes painfully.

The Co-Founder of Wired Wrote a Wired Article. For 11 Hours.

Let me give Kelly credit where it's due. The guy co-founded Wired magazine, he's been thinking about technology trajectories longer than I've been alive, and his core thesis is genuinely useful: there are 12 "forces" (cognifying, flowing, screening, accessing, sharing, filtering, remixing, tracking, interacting, and a few more) that are already in motion and will define the next few decades. The framework itself? Pretty solid. When Kelly talks about "cognifying" - basically AI getting embedded into everything - he was writing this in 2016 and a lot of what he predicted about cheap AI-as-a-utility has already happened. The man called it on AI being less "Terminator" and more "electricity" years before ChatGPT made that comparison mainstream.

The chapter on "flowing" - how ownership gives way to access, how everything becomes a stream rather than a product - clicked for me in a way that changed how I think about our team's architecture decisions at work. Seriously. Kelly frames it as: the internet is a giant copying machine, and the economy shifts toward things that can't be copied (immediacy, personalization, interpretation). That mental model is basically microservices philosophy applied to economics. I kept pausing to text Kevin about it. (He did not care. He was watching basketball.)

But here's the thing. There are 12 forces. TWELVE. And Kelly gives each one roughly equal page time. Some chapters - cognifying, filtering, tracking - are packed with genuine insight. Others feel like he's padding. The "screening" chapter (everything becomes a screen) felt obvious even in 2016, and listening to it now in 2024 it's like... yes, Kevin. I am aware screens exist. I'm looking at six of them right now.

George Newbern: The Reliable Default Config

George Newbern narrates this and he's... fine? He's clear, professional, keeps good pace. For a nonfiction book about technology trends, you don't need Ray Porter-level gravitas (though imagine Ray reading the AI chapter - chef's kiss). Newbern handles the prose-heavy sections without making you zone out, which is harder than it sounds for a business book. He's got that Earphones Award for a reason - the man reads clean.

But there's no personality injection here. No wry emphasis on Kelly's more provocative claims, no tonal shift when the material gets genuinely weird (and it does get weird - Kelly's section on VR and "interacting" borders on psychedelic). It's a straight read. Which means at 6 AM on the Caltrain, surrounded by other engineers in their noise-canceling cocoons, I occasionally drifted. Not Newbern's fault entirely - it's the material cycling between "whoa" and "yeah, I know."

The 2016 Problem (And Why It Still Mostly Works)

Here's what surprised me: for a book that's now 8+ years old and predicting "the next 30 years," a shocking amount still holds up. Kelly's take on AI augmentation over replacement, the shift to platform economies, the inevitability of total tracking and surveillance (he's weirdly okay with this, which - uncomfortable) - all of it aged better than 90% of tech prediction books. He even talks about decentralized systems and filtering algorithms in ways that feel prescient given what happened with social media and crypto since publication.

What hasn't aged well: his breathless optimism. Kelly frames almost everything as net-positive, and post-2020 that reads as naive. The tracking chapter basically says "yes, everything will monitor you, but you'll get cool personalized services!" Reader. I work in tech. The personalized services are ads. The cool thing is ads.

Also, the book has a structural problem that bugs the engineer in me: Kelly acknowledges these 12 forces overlap and are "codependent" but then treats them as mostly separate chapters. It's like documenting a distributed system by describing each microservice in isolation without really mapping the interaction patterns. The dependencies ARE the interesting part, and he only gestures at them.

Who Gets the ROI

Perfect for: train, gym. Skip for: bedtime (you'll drift during the weaker chapters).

If you're in tech, a lot of this will feel like stuff you've absorbed osmotically from Twitter threads and conference talks - but Kelly's framework for organizing it is genuinely valuable. If you're NOT in tech, this is probably one of the better "here's what's coming" primers, even dated. Business folks making strategic decisions will get the most out of this.

I finished this in about 4 commutes at 1.75x and honestly, at 1x it would've been painful. The ROI on this audiobook is solid if you speed it up - maybe 6 of the 12 chapters deliver real insight, and you can mentally skim the rest. Hidden Potential had a similar hit rate for me - genuinely transformative in stretches, filler in others, and best consumed at a pace that lets you fast-forward through the parts where the author is clearly just filling pages.

The Commit Message

Kevin Kelly wrote the book I wish every non-technical PM at my company would read - and also the book that made me argue with my phone on the train about surveillance capitalism. It's uneven, it's aging, it's too optimistic, and it could've been - say it with me - a blog post series. But the good chapters? Genuinely reframed how I think about where technology is headed. And the core thesis - that these forces are inevitable so you should understand them rather than fight them - is an engineer's pragmatism applied to futurism. I respect it even when I disagree with it.