The seventh sneeze is the one that rings the bell. The first six are just the wind-up, a series of increasingly violent convulsions that feel like they’re trying to turn you inside out. But the seventh… that one is different. It’s a full-system reset. For a second, the world goes white and silent, replaced by a high-frequency hum inside your own skull. When my vision cleared, the light was still red. Of course it was.
I was sitting in a perfectly engineered traffic jam. Not a chaotic, post-accident snarl, but a neat, orderly, and deeply infuriating procession of stops and starts. This intersection was upgraded last year with an adaptive signaling system, a marvel of modern efficiency that cost the city a cool $272,232. It promised to analyze traffic flow in real-time, optimizing the movement of every vehicle with predictive grace. What it actually did was create a strange, pulsing rhythm of movement that felt profoundly, primally wrong. We’d lurch forward for 12 seconds, then stop for 42. Green lights would appear for cross-traffic that wasn’t there, while our lane sat, engines humming with pointless potential.
And I used to be one of the people building the life rafts, which, it turns out, were made of lead.
My friend, Liam G.H., is a traffic pattern analyst. Or he was. Now he calls himself a “flow psychologist,” a title he invented after having a nervous breakdown in a grocery store self-checkout line. For years, Liam’s entire professional life was dedicated to shaving seconds off commutes. He’d build complex models showing how adjusting a signal’s timing by 2 seconds could increase vehicle throughput by 22%. He was a wizard of the aggregate, a master of the statistical win. He showed me a projection once where his new algorithm for the city’s central corridor would save a cumulative 1,322 hours of commute time per day. We celebrated that number. We thought we were making the world better.
Projected Daily Savings
(Liam’s algorithm on paper)
We were wrong. We were measuring the machine, not the person inside it. Liam’s algorithm worked on paper. It did, in fact, move more cars. But it did so by creating patterns that no human could internalize. The old, dumb timers were predictable. You knew that the light on Elm Street was long, so you could relax for a moment. You knew the one on Oak was short, so you stayed alert. There was a rhythm, a cadence to the city. Liam’s system replaced that cadence with chaos. It was optimized for cars, but it was deeply hostile to drivers.
The Machine
(Algorithms, Metrics, Systems)
The Person
(Experience, Feelings, Humanity)
This is a mistake I have made more than once. I once argued passionately for a project management system at a previous job. It was beautiful. It had Gantt charts, resource allocation modules, and automated dependency tracking. It promised to boost productivity by 32%. We implemented it. And productivity went down. Why? Because everyone spent two hours a day updating the damn system that was supposed to be saving them time. We were so focused on the metric-the percentage of tasks marked “complete”-that we forgot the goal: doing good work. We optimized the process and suffocated the purpose.
Productivity Promise vs. Reality
Expected Boost
+32%
Actual Result
↓ Significant
“Productivity went down.”
It’s a subtle form of madness. You see it everywhere. The automated phone menu that forces you through 12 options to reach a human, supposedly to “route your call more efficiently.” The social media feed that shows you what its algorithm thinks you want to see, leaving you feeling empty and agitated after 42 minutes of scrolling. The problem is that these systems define “efficiency” in the narrowest possible terms. Fastest. Most. Cheapest.
Liam told me the breaking point was the intersection by the old paper mill. His system was a masterpiece of technical achievement there. It juggled traffic from two main arteries, a factory entrance, and a school zone. His model showed a 42% reduction in average wait time. But it also, perplexingly, showed a 12% increase in minor accidents. Fender-benders. Abrupt stops. The kind of collisions born not of high speed, but of high anxiety. The system was so unpredictable-accelerate now, slam on the brakes, turn, no wait, stop-that it was fraying people’s nerves to the breaking point. The cognitive load was immense. Drivers were so busy trying to anticipate the algorithm’s next move that they stopped anticipating each other’s. A small increase in accidents might seem statistically acceptable for the city planners looking at the numbers, but it’s a life-altering event for the person who suddenly needs to find a Schaumburg IL personal injury lawyer because a computer decided to save another lane 2 seconds.
Reduction
Increase
We’ve all been trained to worship at the altar of the metric. We want the five-minute abs, the app that finds the absolute fastest route, the stock-trading bot that executes in milliseconds. But the fastest route isn’t always the best one. Sometimes the scenic route, the one with predictable lights and less traffic, is the one that gets you to your destination feeling human. The one that doesn’t add 22 points to your blood pressure. I find myself doing this now, deliberately choosing the “inefficient” path. I’ll take the street with the old, dumb, reliable traffic lights over the “smart” one that gives me anxiety attacks.
This isn’t just about traffic, of course. That’s just the most obvious, physically-present example of this digital cage we’re building for ourselves. The tangent that always comes to mind is my new coffee maker. It can connect to WiFi. It has 22 different brew settings, from “Delicate” to “Robust Gold.” My old one had one button. You pushed it. Coffee came out. This new one requires me to navigate three menus on a tiny LCD screen, and half the time it tells me there’s a firmware update. The coffee is maybe 2% better. But the experience of making it is 132% worse. We’ve optimized the coffee but ruined the morning.
Liam is working on a new theory now. He calls it “Cognitive Efficiency.” The goal is not to minimize time, but to minimize mental strain. An intersection is cognitively efficient not when it moves the most cars, but when it requires the least amount of complex decision-making from the drivers. A cognitively efficient system feels smooth, predictable, and fair. It might even be a few seconds slower on paper, but the humans navigating it will be calmer, safer, and less likely to lay on their horn for 22 seconds straight.
He’s onto something. The next frontier isn’t about making things faster or smarter. It’s about making them wiser. It’s about remembering that at the end of every optimized process is a human being who just wants to get through their day without having a nervous system meltdown. We’ve become so obsessed with the numbers on the screen that we’ve forgotten the feeling in our gut. The goal shouldn’t be a perfectly optimized system. It should be a system that gracefully accommodates the beautifully inefficient, unpredictable, and sometimes sneezing creatures it’s supposed to serve.
The light in front of me finally turned green. I drove through the intersection, ignoring the GPS voice screaming at me to take a faster route. I took the long way home. It took an extra 12 minutes, and it was the most peaceful drive I’d had all week.