The Operations Bridge

Point fifteen. One of the more uncomfortable things I’ve come to believe: AI is an amplifier, and amplifiers don’t care whether what they’re amplifying is any good.

Speed is not the same as improvement

I’ve written before about the difference between busyness and flow — how a plant can look productive while value sits still. AI makes this trap easier to fall into, because it produces the visible signs of progress so convincingly. Lots of output, fast. But if the underlying process was confused about what it was trying to accomplish, you now have confused output at higher volume. That’s not improvement. That’s the same problem with better production values.

Amplification cuts both ways

Point a strong tool at a clear, well-understood process and it’s genuinely transformative — the good parts get faster and more consistent. Point that same tool at a vague or broken process and it faithfully scales the vagueness. The tool is neutral. It amplifies whatever discipline, or lack of discipline, you already had. Which means the return you get from AI is largely decided before you ever turn it on.

Fix the process first, then accelerate it

This is the same lesson benchmarking trips teach the hard way: you can’t copy a solution without the context that made it work. Before you accelerate a workflow with AI, it’s worth asking whether the workflow itself is one you’d be proud to make ten times faster. If the answer is no, the tool isn’t your first move. The process is.

A question for leaders

Pick the process you’re most tempted to throw AI at. Now ask: if this ran ten times faster tomorrow, would that be ten times better, or just ten times more of a mess? Your honest answer tells you whether to reach for the tool or the whiteboard first.