The Watchmaker's Worn Screw and the Integrity of a Non-Interchangeable Part

The pursuit of productivity is often a pursuit of interchangeability. We seek the universal app, the one-size-fits-all framework, the modular workflow where a broken component can be swapped out with an identical, off-the-shelf replacement. This is the logic of efficiency. It is also, I've come to suspect, the logic of a fragile system.

Consider the opposite: the worn screw in an old wristwatch. It's a tiny, specific piece of brass, its threads polished to a unique fit by decades of gentle vibration against its plate. A modern replacement, even from the same manufacturer, would be theoretically identical. Yet the watchmaker knows it is not. That new screw is a stranger to its hole; it will seat differently, alter the microscopic tensions of the assembly, and the watch—though technically 'repaired'—may never again keep time with its former, settled character. The correct, counterintuitive repair is often to leave the worn original precisely where it is.

The Friction of Familiarity

We are told to optimize our tools, to ruthlessly eliminate friction. But what if some friction is not an enemy of work, but its signature? That stubborn, slightly awkward text editor you’ve used for years, whose quirks you’ve internalized? That physical notebook with its particular grain of paper that your pen catches on? That cluttered, non-standard folder structure on your desktop that you can navigate blindfolded? These are your worn screws.

Replacing them with the 'optimal' alternative incurs a hidden tax: the cognitive load of re-learning, the subtle disorientation of a new landscape, the loss of the deep, unconscious familiarity that allows thought to flow directly into action. The time saved by a marginally faster tool is often spent tenfold in the mental overhead of adopting it. The worn part, by contrast, has become an extension of your intention. Its resistance is known, its give is calculated, and work proceeds within a trusted, if imperfect, environment.

This isn't an argument against improvement, but a plea for discernment. Before you swap out a component of your workflow in the name of productivity, ask: has it worn into its role? Has its specific friction become a form of feedback? The goal is not a pristine, generic machine, but a coherent, personal instrument. Its value lies not in every part being new and perfect, but in the whole telling time accurately—in getting the real work done—through a history of subtle adjustments and accepted wear.

The integrity of the system often depends on the integrity of the original, shaped part. Our workflows are not factories assembling widgets; they are more like the quiet, precise mechanisms of a watch, where every part bears the mark of its specific duty. Sometimes, the most productive thing you can do is leave well enough alone, and let the worn screw hold the works together, just as it has always done.

Notes & further reading

A few pages I came back to while writing this: