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
OpenAI Codex lead on the new shape of product work | Andrew Ambrosino
OpenAI Codex lead Andrew Ambrosino explains how AI has inverted product development, making implementation so abundant that taste and curation—not coding—are now the primary bottlenecks, while Codex scales to 5 million weekly users and 90% internal adoption at OpenAI.
Building the most AI-pilled engineering team in the world | Fiona Fung (Anthropic)
Fiona Fung, leader of Claude Code and Co-work at Anthropic, reveals how her engineers now ship 8x more code than in 2021, fundamentally shifting the engineering bottleneck from writing to verification and requiring new AI-native management techniques to maintain quality at scale.
The hidden pattern behind successful products | Mark Pincus (FarmVille, Words with Friends, & more)
Mark Pincus shares his "Proven Better New" framework for building hit consumer products, arguing that founders should copy proven elements, make incremental improvements that 10/10 users love, and treat truly novel features as high-risk experiments—contrary to the instinct to prioritize innovation over familiarity.
Father of the iPod and iPhone on building taste, judgment, and creativity in the AI era
Tony Fadell shares lessons from building the iPod and iPhone, arguing that creating category-defining products requires resisting AI-driven cognitive surrender, embracing opinion-based decision-making for 1.0 versions, and micromanaging critical details while maintaining ruthless focus on customer pain points and storytelling.