n o ren
AI & Technology

Less Friction, More Chaos

When a team swapped manual code checks for an AI assistant, their bug count rose while release speed seemed to double.

Removing human bottlenecks feels like a win, but the hidden cost is the loss of “friction” that normally forces people to pause and double‑check. In physics, friction converts kinetic energy into heat, preventing a sled from careening uncontrolled; in work, deliberate friction—review loops, manual sign‑offs, even a moment of uncertainty—forces the brain to surface assumptions before they become baked‑in decisions.

AI tools excel at erasing that friction by instantly generating drafts, auto‑completing tickets, or auto‑routing approvals, so the workflow accelerates while the mental pause evaporates. The result is a cascade: faster outputs carry forward unchecked premises, leading to subtle defects that compound downstream, and a growing reliance on the tool’s surface suggestions rather than deeper reasoning.

An engineering group that integrated an AI code‑completion assistant into their pull‑request pipeline found that reviewers began to skim instead of probing, and the same code that once required a two‑hour manual audit now sailed through in minutes, only for a production outage to surface weeks later because a hidden dependency had been silently introduced. The paradox is that the very speed that AI promises can undermine the quality guardrails that kept the system stable, turning a productivity boost into a hidden reliability risk.

AI that removes manual friction also removes the moment of deliberate scrutiny.
Speed gains are only real if they don’t trade away the safety net of a thoughtful pause.

Ignoring the loss of friction means hidden bugs can proliferate, eventually causing costly outages or brand damage.

Teams that surrender their mental pause to AI risk eroding their own problem‑solving muscles, making future projects harder to rescue.

1
Open the most recent AI‑generated pull request, locate the line where the assistant inserted code, and count how many reviewer comments ask for a deeper explanation of that insertion.
2
In your task board, flag any tickets that moved from “in progress” to “done” in under an hour without a logged reviewer note, and note if they later required a hot‑fix.

The concept traces back to ergonomics research on “controlled speed” where designers deliberately insert delays to catch errors before they propagate. In software, the “review latency” acts as a cognitive buffer, giving engineers time to surface implicit assumptions. When AI shortcuts that latency, the buffer evaporates, and errors that would have been caught early now travel farther before detection.

The downside isn’t just technical; it reshapes culture. Teams may begin to equate “fast” with “good,” rewarding speed over rigor, which can shift hiring criteria toward rapid output rather than deep analytical skill, creating a feedback loop that entrenches the friction loss.