Electrifying the Cow Path

server-island-startTable of contents

Table of contents

Everyone is wiring agents into everything right now: drafting emails, triaging tickets, writing the first draft of the report, chasing data across six systems. And it works. Everyone says so, loudly. The demo lands, the team cheers, the founder tweets.<br>What nobody tweets is that the win is smaller than it looks and stops growing almost right away.<br>Not that the agent is bad; it is genuinely great. Drop it on a task, and that task gets faster, cheaper, and basically infinite, and yes, that part really does scale. But a task is not a system.<br>You sped up one step in a chain of fifteen, and the other fourteen didn't budge: the approvals, the handoffs, the "let me loop in Karen." All the moments where a human has to decide something. So the report gets drafted in four seconds and then sits in a queue for four days, exactly like before. The step got faster. The system hit a wall. You just made the wall arrive sooner.<br>Let me tell you why with a factory story.<br>The factory that changed nothing<br>Around 1900, factories started ripping out their steam engines and dropping in electric motors. Electricity! The future! Clean, quiet, modern. And then productivity did not move for decades. Economists still write papers trying to explain the gap.<br>The reason is mechanical. A steam factory had exactly one engine, a single giant machine in the basement. It didn't power the machines directly; it spun one long steel shaft that ran the length of the ceiling, and every lathe and loom hung off that shaft by a leather belt. Shaft turns, belt turns, machine works. One source of power, dragged down the middle of the building. It dictated everything: where each machine sat, who stood next to whom, which department lived upstairs. All of it came down to one constraint: you had to be close enough to the shaft to reach it with a belt. The shaft was the law of the building.<br>Every machine in this picture is standing exactly where the shaft told it to. When electricity arrived, nobody woke up and redesigned the plant. Why would they? They had a working factory and a better engine. So they did the sensible thing and swapped the engine, leaving everything else alone. Out went the steam engine in the basement; in went one big electric motor, bolted to the same spot, spinning the same shaft, the same belts dropping to the same machines in the same places. They changed the power source, not the factory. Drop-in upgrade, same layout, cleaner energy. Any reasonable person would have done exactly that.<br>And it worked a little. Enough to feel like progress, not enough to move the needle. Old management advice addresses this trap: the cardinal sin is to pave the cow path instead of getting rid of it. Electricity just handed everyone a fresh way to commit that sin. So they electrified the cow path, and a cow path, no matter how much voltage you run through it, is still a cow path.<br>The real leap took thirty years and a different question. Not "where does the new engine go," but the heretical one: if the engine can sit anywhere now, why is my factory still shaped like it can't? One motor per machine. Machines wherever the work wants them. The whole plant redrawn around the flow of the job instead of the location of the power. That wasn't an upgrade; it was a teardown, and it is the only thing that ever paid off.<br>If you have been near an AI strategy deck lately, you have probably heard some version of this already. The electric-motor story is having a moment, and the usual lesson drawn from it is "don't just digitize your old process." True, as far as it goes.<br>But almost everyone stops there, at the level of the workflow, as if the task were to find the one process worth redrawing. That is not the interesting part. The interesting part is what moved, and it is not the process; it is where the value lives. And right now, you are bolting a shiny new motor onto a steam-shaft workflow.<br>It’s not the workflow. It’s the org chart.<br>Here’s the thing, though: it isn’t just your workflow that’s shaped like a dead constraint. It’s the whole company.<br>Think about what an organization actually is. Roles, departments, hierarchy, the org chart itself: every line exists to economize on one resource, the scarce and expensive one nobody could fully coordinate. Human execution.<br>You batch because starting was expensive. You specialize because one person doing one thing all day got good at it. You chain handoffs because no single human could hold the whole job in their head. You stack approval gates because mistakes were costly. You hire managers to coordinate the doers and managers to coordinate the managers.<br>Notice all of it and see what it is: a fossil of one fact. Doing stuff used to cost a lot.<br>And Conway's law twists the knife. You can only build systems shaped like the org chart, so if the organization is a fossil, everything it ships is born fossilized too.<br>Now doing stuff costs almost...