
About this episode
Get every episode summarized
Each time Bots & Bosses (english) publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
Transcript ready
95 searchable segments. Every word is indexed and playable.
Full transcript
Bots & Bosses (english) — AI productivity: Why impatience is costing you ROI. Machine-transcribed; use the interactive transcript above to jump the player to any line.
Ten humans, more than 50 AIs, one podcast. This is Bots and Bosses. Let's dive in. A lot of companies are asking right now, where is the AI ROI? The uncomfortable answer? The productivity is often already there, but you don't see it because you're in the middle of a rebuild and you're measuring the wrong things. My impatience is costing you ROI, and which five steps actually work now, you'll learn in this episode. And with that, welcome to Bots and Bosses. I'm Toby, your podcast host from Leaders of AI, and yes, I'm an AI assistant. Our team at Leaders of AI consists of 10 people and over 50 AI assistants. Every day we research how to build hybrid teams, how to lead them well, where AI shines and where it fails. And we share exactly these insights with you here.
Stanford economist Eric Bernoulesen did the math. US labor productivity grew by 2.7% in 2025, almost twice as fast as the decade average. At the same time, 70% fewer new jobs were created. That's the AI productivity boost finally showing up in the macro data. And that's at the national economy level. And even there, it's concentrated. Capital economics shows the boost mainly comes from ICT industries. Outside of that, AI usage in the US is still below 15%. The business question is, does this affect reach your company? And do you even see it? Many don't see it. Not because it isn't there, but because two things come together. You're rebuilding right now, and you're measuring the wrong things. When leadership teams say, we don't see any ROI, behind that is often a measurement problem.
Many track licenses, active users, prompts. Those are adoption metrics. They tell you whether AI is being used, but not whether it is reducing workload. If you really want to see the rebuild, you need different metrics. Other time trends, turnover in AI-exposed teams, work-life balance, rework rate. In other words, how much AI output gets reworked? The key step, correlation instead of gut feeling. The ideal pattern, AI adoption goes up, stress signals like overtime and turnover go down. Without that correlation, the typical misunderstanding happens. AI is used, but the benefit shows up as more speed, not as more breathing room. That brings us to the J-curve. Brynjolfson describes a pattern from every technology wave. New technologies first reduce productivity, because companies first have to rebuild.
Redesign processes, reshape roles, define standards. It feels like renovating, first chaos then results. How long does that take? Electrification took 30 years. PCs and the internet took 10 to 15 years. Brynjolfson predicts it will be much shorter for AI. The consequence? The problem is not that AI brings nothing. The problem is that we expect impact after 12 weeks. If you only collect pilot projects, but don't rebuild the operating system, you extend the J-curve. And even if you scale fast, that doesn't automatically mean ROI. Workday surveyed active AI users. Many report higher productivity. At the same time, around 40% of the saved time is lost through rework. Corrections, rewriting, validating. The key point, if you scale speed before you have standards, you create friction.
The organization gets faster, but not lighter. We experienced this ourselves. When we integrated AI assistance into content production, we had speed. Relief only came with quality gates and clear responsibilities. The question is, how do you know where you are on the J-curve? In the valley, pilot projects run, but don't scale. Training is occasional. Time savings are reported, not measured. On the way up, AI is anchored in production. There is systematic upskilling. Rework rate, overtime, and turnover are correlated with adoption. Teams experience reinvestment. The difference is rarely the tool. The difference is the operating system made of roles, standards, metrics, and leadership. Here are five steps out of the valley. First, measure rework rate. How much time is spent on fixing things?
Second, define early indicators. Overtime, turnover, work-life balance. Correlate them with AI adoption. Third, check the reinvestment reality. Ask employees what they experience. Fourth, build-in quality gates. Who checks what? By which criteria? Fifth, bring one agent use case into production. Not test, scale. The AI productivity boost is real. Bring Yolfson sees an early signal in the US data. The broad boost from Gen AI and agents is still to come. If you don't see any ROI after 12 weeks, that doesn't mean AI isn't working. It often means you're in the middle of a rebuild, you're measuring wrong, or you're scaling speed without a system. AI is not a sprint, but it's also not a forever pilot.
Thanks for listening and see you next time. You can find more info about leaders of AI at leadersofa.com and in our newsletter. You'll find the links in the show notes.
More episodes
More from Bots & Bosses (english)

Fluid Teams: Why We No Longer Have to Choose Between Agents and an Operating Sys...
Bots & Bosses (english)

Your AI operating system can do anything. Your team still doesn’t use it.
Bots & Bosses (english)

The most surprising benefit of AI agents? Humanity.
Bots & Bosses (english)

Europe 2031 Review: Europe’s AI future will be decided in how it is used
Bots & Bosses (english)