The Cult of Velocity

I was stacking 232 weathered stones the other day, ones I’d pulled from the foundation of an old wall we decided to repair instead of replacing entirely. My core frustration-the reason I ended up deleting a whole draft of an angry email to a colleague-is the absolute cult of speed we’ve built around everything, especially decisions that actually need gravity and friction. It’s a collective, manic belief that if something isn’t accelerated, digitized, and streamlined, it is inherently lazy, inherently flawed. We are terrified of the lag time, and so we optimize away the necessary viscosity.

I kept trying to set the stones too fast, rushing the mortar because I had allocated 42 minutes to the task, not the three hours it actually demanded. Every time I rushed, the mortar bled, the balance shifted, and I had to knock the whole section down, losing time, losing material, losing patience. The true cost of optimization isn’t the marginal time saved; it’s the structural debt incurred by skipping the required processing pause. We have convinced ourselves that complexity is solved by velocity, when in fact, complexity demands slowness to reveal its true shape.

Friction as a Feature, Not a Bug

My contrarian angle here is simple, painful, and deeply unpopular: The highest performing systems are often those which have intentional, built-in friction. Not friction generated by pointless bureaucracy, but friction built for necessary processing. This looks like time allocated purely for quiet thinking, time reserved for redundant structural integrity checks, or time spent arguing against the easy solution. We treat these delays like bugs, but they are features designed to save us from catastrophic efficiency.

When you move too fast, the surface looks great, but the sub-structure is riddled with weak points, waiting for the first real stress test to crumble. You never see the rot coming because the speed masked the smell. We never appreciate the structural integrity of what we stand on-the literal, physical foundation-until the seams split and the water starts coming up.

That is the viscosity I’m talking about-the knowledge that requires a certain density of attention. I look at that level of specificity and realize my own worst mistake this year wasn’t over-planning; it was trying to compress a multi-phase learning process into a single, aggressively efficient sprint. I valued velocity over viscosity, and I paid for it.

The Keeper and the Clockwork

June keeps the light burning at a remote spot, responsible for ancient Fresnel lenses and clockwork. The system is inherently analog and demands constant, slow maintenance. She resists ‘modernization’ because the purpose defines the pace. Try to rush the rotation, and the focus blurs, the glass cracks, the bearings seize. That’s the deeper meaning: purpose defines pace. If your purpose is profound (like guiding ships through fog), your pace cannot be reckless.

June pointed out what happens when polishing brass reflectors: “You can’t cheat brass. If you rush it, you leave micro-scratches. Those scratches don’t matter today, or tomorrow. But they compound the light’s diffusion over 2 years. They steal strength imperceptibly, until suddenly, the reach is 2 miles shorter than it should be. And that 2 miles is the difference between life and death for someone out there.”

That hit me hard. We are so busy creating frictionless paths that we forget friction is often the element that refines the surface. The pressure of friction creates heat, but it is also the agent of polish. We are polishing away the friction in our processes, thinking we are making things easier, but we are actually just making them duller and less resilient.

The True Cost of Rushing the Crash

When I first started out, I swore by the mantra of ‘fail fast.’ I still think that’s useful, but it misses a critical component: sometimes you need to ‘fail slow’ to understand the true causal chain of failure. Rushing through the crash merely teaches you that you crashed. Slowing down the incident review-forcing 42 deep questions instead of 2-teaches you *why* the axle sheared. Why are we so desperate to get back to ‘doing’ that we refuse to ‘process’ the damage?

I was furious at the clients for being ‘difficult’ when, in reality, I was furious at myself for prioritizing my own efficient timetable over their complex needs. This is where I started writing that angry email, blaming external factors, then stopped. That externalized rage was just covering up the internal contradiction. We’ve engineered the pause out of existence.

The Physics of Stability

What we mistake for inefficiency is often integrity maintenance. Think about the processes in nature that yield the most valuable results-geological formation, barrel-aging, the complex evolution of an organism. None of it is fast. It is all defined by immense patience and the slow, consistent application of pressure and time.

My goal now isn’t speed; it’s finding the minimum viable speed-the rotational velocity that maximizes stability while achieving the necessary output. Anything faster is self-sabotage dressed up as ambition.

If we truly want extraordinary outcomes, we must stop chasing frictionless processes. We need to look for where the necessary friction points are-the places where resistance yields refinement-and protect them fiercely. If the decision takes 2 days to fully set, let it take 2 days. Don’t rush the curing. If you cheat the cure time, the result will always be brittle.

The Final Question

What structure in your life are you currently weakening by prioritizing speed over stability?