The Conductor's Unmetronomed Phrase: On the Forgotten Virtue of a Human-Hasty Response

We worship at the altar of smoothness. Our performance gospels preach a world of fluid, unbroken transitions, of content that settles like dust in a sunbeam—gracefully, predictably, and above all, without a jitter. We chase a perfect, machined experience, where every pixel arrives on a schedule defined by a Core Web Vitals spreadsheet. But in our zeal to eliminate every stutter and shift, have we quietly exorcised something more vital: the feeling of a page that’s alive to our intent? I want to argue for the counterintuitive, almost heretical value of a certain kind of haste—a human-hasty response that feels direct and immediate, even if it’s technically less perfect.

The Tyranny of the Settled Frame

Consider the ubiquitous advice around Cumulative Layout Shift (CLS). The goal is zero. Zero movement after the page begins to load. This has led to an orthodoxy of defensive sizing, of allocating space for everything that might come, of treating the viewport as a static canvas to be filled with absolute precision. The result is often a page that feels pre-ordained, a museum exhibit behind glass. It’s stable, yes. But it can also feel inert, as if our click or tap was merely a request to view a pre-rendered diorama, not an action that sparked a live reaction.

Now, imagine a different interaction. You tap a button to filter a list. Instead of a 300ms delay while JavaScript fetches data, calculates a transition, and smoothly animates the old items out and the new ones in—a process that feels orchestrated and distant—the old list vanishes instantly and the new one appears, perhaps with a slight, raw repositioning of surrounding elements. It’s not ‘smooth’ by our current metrics. It might even trigger a tiny, measurable layout shift. But the feeling is one of direct consequence. The page reacted to you with the digital equivalent of a reflex, not a choreographed ballet. It felt fast because it was eager, not because it was efficient.

This is the human-hasty response. It prioritizes perceptual immediacy over compositional perfection. It’s the slight scroll-jerk when new content is appended inline because you asked for it, signaling ‘here it is, now.’ It’s the form field that highlights the moment your finger makes contact, not after the browser’s touch-event delay cycle completes. This haste has a texture. It feels less like waiting for a machine to compute an optimal path and more like pulling a lever and seeing a mechanism engage directly, with all its satisfying, immediate clunks and shifts.

Our craft has become so focused on eliminating the negative perception of delay (jank) that we risk eliminating any perception of action at all. We’ve conflated ‘good’ with ‘undetectable.’ But humans don’t just perceive smoothness; we perceive agency. A response that is slightly ragged but immediate can reinforce our sense of control far more than a perfectly buffered one that feels mediated and computational. It’s the difference between turning a steering wheel connected directly to the wheels versus one that feeds your input through a computer that chooses the ‘optimal’ turning curve. One feels connected; the other, however smooth, feels processed.

This isn’t a call for regression, for abandoning our hard-won stability gains. It is, however, a plea to broaden our definition of performance. Beyond the metrics of stability and speed, we must consider the metric of responsiveness—not in the RUM sense, but in the emotional, tactile sense. Sometimes, the most performant feeling isn’t a perfectly settled frame. It’s the quick, imperfect, and wonderfully direct twitch of a page that seems to be listening, and answering, in real time.

Notes & further reading

A few pages I came back to while writing this: