A rational conversation on where AI is actually going | Benedict Evans
TL;DR
AI represents a transformative shift comparable to the internet or mobile, but we remain in its infancy (like 1997), with adoption spread unevenly across industries and the real challenge being integration and judgment rather than mere task automation.
🌍 Scale and Timeline of Disruption 2 insights
AI matches internet/mobile impact, not industrial revolution scale
Evans argues AI is fundamentally transformative like smartphones or the web, but not categorically larger, placing us currently in a "1997 internet" phase where most applications remain unbuilt and unreliable.
Massive adoption gap between tech insiders and general public
While some tech workers have abandoned Google for AI clusters, survey data shows even among teenagers, only 15-20% are daily active users, with 60% not using AI tools at all.
đź’Ľ Labor Markets and Automation Reality 3 insights
Historical pattern suggests job transformation, not elimination
Evans counters apocalyptic job loss predictions by noting that automation historically eliminates specific tasks while creating new roles that didn't previously exist, evidenced by AI labs themselves increasing headcount.
The hard part of work is judgment, not task execution
Using the spreadsheet analogy, Evans explains that automating tasks (like VisiCalc for accountants or IDEs for developers) typically increases output rather than reducing employment, because the valuable work lies in deciding what to build or analyze, not the execution.
Anti-AI sentiment offers moral superiority but no practical advantage
Dismissing AI as evil may feel satisfying, but Evans argues that practical success requires diving in to understand what the tools can actually do today.
🏗️ Enterprise Implementation Challenges 2 insights
AI labs investing heavily in human consultants
Despite predictions that AI would replace consultants, leading labs like OpenAI and Anthropic are acquiring professional services firms to help enterprises integrate AI, recognizing that implementation requires dedicated project teams.
Companies lack internal capacity for workflow redesign
Organizations have no spare staff to analyze which workflows can be automated or to integrate vertical systems, necessitating external consultants like Accenture or Bain to manage the transformation.
Bottom Line
Organizations should actively experiment with current AI tools to understand their specific applications rather than dismissing the technology or waiting for perfect automation, as the value lies in augmenting judgment-heavy work rather than replacing human expertise entirely.
More from Lenny's Podcast
View all
The AI paradox: More automation, more humans, more work | Dan Shipper
Dan Shipper argues that AI will not eliminate jobs but instead bifurcate work into delegated agent tasks and deep creative work within AI-native environments, requiring more human oversight, not less.
Why we’re at the beginning of the AI hardware boom | Caitlin Kalinowski (ex–OpenAI, Meta, Apple)
Caitlin Kalinowski argues that as AI software capabilities saturate, the next inevitable frontier is physical AI—robotics and manufacturing—leveraging decades of VR/AR sensor technology, though hardware's brutal constraints around limited iterations, supply chains, and safety pose formidable barriers to scaling.
How to build a company that withstands any era | Eric Ries, Lean Startup author
Eric Ries argues that standard corporate governance structures create a 'force of corruption' that statistically guarantees 80% of venture-backed founders lose control within three years of IPO, and explains how embedding structural safeguards—like Anthropic's independent safety board—can protect companies from the organizational decay that destroys even successful enterprises.
Why cultivating agency matters more than cultivating skills in the AI era | Max Schoening (Notion)
Max Schoening argues that as AI democratizes technical skills, agency—the belief that you can change the world—has become more valuable than specific capabilities, while product roles are merging as designers and PMs increasingly prototype and build directly in code.