Discussion about this post

User's avatar
Jason Averbook's avatar

We've never had a clean answer for how domain expertise moves from generation to generation without the apprenticeship layer — and entry-level roles, as frustrating as they were for the people in them, were doing that work quietly in the background.

The 346% number tells you something important: organizations treated AI deployment as a task swap, not a workflow redesign. So now you have humans absorbing both the original cognitive load and the AI's failure modes. That's not transformation. That's addition disguised as subtraction.

The harder question underneath yours: if we cut the people carrying the knowledge AND we didn't build the systems to capture it first, what exactly is the AI learning from in five years? We may be automating the surface while hollowing out the foundation.

Pawel Jozefiak's avatar

The 346% task time increase stat hit hard because I've seen a version of this myself.

I run AI agents for content, automation, code. On paper my output tripled. In practice I spent evenings reviewing agent work, weekends debugging edge cases, mornings clearing notification queues from overnight runs. The cognitive load didn't shrink, it shapeshifted. Your point about automating on top of work instead of transforming it is the real diagnosis.

I ended up building a wellbeing system into my agent setup (https://thoughts.jock.pl/p/ai-productivity-paradox-wellbeing-agent-age-2026) because without it the agents just kept producing and I kept reviewing.

5 more comments...

No posts

Ready for more?