Latency Kills Curiosity

“Taking a five-minute break every thirty-five minutes is part of the reason W2 employees are inefficient. Contractors don’t bill you for that. They only bill you when they’re working.”

A manager said this to me, out loud, about the Pomodoro technique. A researched, documented productivity method that exists because sustained focus without breaks degrades performance. Whether intended or not, this statement communicated that his position was that rest is waste, and the proof was that contractors don’t charge for it (they do, obviously, they just fold it into their rate — but the belief was sincere).

I carried that belief — that doing anything other than work while at work was a moral failing — for longer than I should have. That the inability to sustain eight continuous hours of output meant something was wrong with me, not the expectation.

It took a very long time to understand that this wasn’t a discipline problem. It was a systemic one.

The three-second rule and its cousins

There’s a well-documented principle in web performance: if your page takes more than three seconds to load, roughly half your visitors leave. They don’t complain. They don’t file a bug report. They just go somewhere else. The curiosity that brought them to your page evaporates before the content arrives.

This site scores 100 on Google’s PageSpeed Insights. That’s deliberate. Not because I’m chasing a number (well, ok, maybe a little), but because I believe that the space between “I want to see this” and “I can see this” should be as close to zero as possible; every millisecond of friction is a tax on the visitor’s willingness to engage.

The same principle operates at every other scale. It just moves slower, so the damage is harder to see.

When the latency is your calendar

In a work environment, latency looks like this: you have an idea. Maybe it’s a better way to handle a deployment pipeline, or a pattern you noticed in client data, or a fix for a years-old page builder quirk, or a tool that could save the team hours per week. But there’s no time to explore it. The sprint is full. The backlog is groaning. There’s a client call in twenty minutes and you haven’t prepped.

So the idea goes into a notebook. Or a sticky note. Or the back of your head, which is already holding forty other things it can’t afford to drop.

A week later, the idea is gone. Not because it was bad, but because the environment provided zero space between “I’m curious about this” and “I can explore this.” The latency was too high, and curiosity bounced.

Multiply that by months. By years. What you get isn’t laziness or disengagement; it’s something sinister and quieter and more corrosive: curiosity that’s stopped aiming at the work. Stagnation. Rote repetition. Work that technically gets done, but without intent or clarity. The lights are on, the engine is running, but nobody’s driving.

Curiosity doesn’t disappear, it redirects.

The person who can’t explore within their work starts exploring outside of it. They get distracted more easily. They disengage from tasks that used to hold their attention. They start to resent the work itself, not because the work changed, but because it became the barrier between them and the thing their brain actually wants to do.

This looks like a performance problem from the outside. From the inside, it feels like suffocation.

The risk isn’t that people stop working. The risk is that they stop caring about the work. And once that happens, the quality degrades in ways that are invisible until something breaks.

When the latency drops

When I give myself permission to wander — to follow a tangent, to explore something adjacent to the task, to take the five-minute break that a manager once told me was proof of inefficiency — the quality of my work goes up. Measurably.

Connections form between domains that seemed unrelated. Solutions appear for problems I wasn’t actively working on. The tension and stress of sustained “action mode” drains away enough that the next focused session is sharper, faster, and more intentional.

This isn’t a productivity hack or a wellness platitude. It’s architecture. The same way a well-designed system has buffer capacity and graceful degradation paths, a well-designed work pattern has margin for the brain to do its background processing. Remove the margin and the system still runs, but it runs brittle. One unexpected load and something cracks.

Tangential exploration is a feature

The instinct in most organizations is to treat tangential exploration as waste. If you’re not directly producing output against a defined task, you’re not working. This is the same logic that produces the Pomodoro comment — the belief that every minute not spent in direct production is a minute lost.

It’s also the logic that produces teams who can execute tasks but can’t solve problems. Who can follow a sprint plan but can’t tell you if the plan is aimed at the right target. Who deliver exactly what was asked for and nothing that was needed.

Allowing space for exploration during work isn’t a perk or a concession. It’s how you get people who think instead of people who comply. And the difference between those two outcomes is the difference between a team that hits a problem and already has context, and a team that hits a problem and has to stop everything to figure out what’s happening.

The footer line

At the bottom of this site, there’s a line: “This site is intentionally over-engineered for speed, because latency kills curiosity.”

When I wrote it, I was thinking about page speed; about not wanting a slow load time to be the reason someone didn’t read a case study or explore the blog. That concept felt important enough to build the entire site around.

I didn’t have the language for the rest of it yet. But the feeling was already there, had been for decades. That every system I’ve ever struggled against — the slow page, the packed calendar, the expectation of continuous output, the manager who thought breaks were waste — was all the same problem.

Friction between a person and the thing they want to explore. Latency. And enough of it kills the curiosity that makes good work possible.