The Watchmaker's Oil and the Peril of the Over-Lubricated Gear
I once watched a master watchmaker at his bench, a man whose hands moved with a quiet, deliberate economy. He was reassembling a complex movement, a tiny universe of spinning wheels and oscillating balances. His most delicate tool wasn't a screwdriver or a pair of tweezers, but a fine needle dipped in a minuscule pot of oil. The application was the entire ritual. A single, almost invisible droplet, placed with absolute precision on the tip of a pivot point.
He explained that a novice’s greatest error is the belief that if a little oil reduces friction, then more oil must be better. It is a catastrophic miscalculation. Excess oil doesn’t lubricate; it migrates. It creeps onto the pallet fork, gums up the escape wheel, and soils the delicate hairspring. The very substance meant to ensure smooth operation becomes a viscous trap, attracting dust and grinding the mechanism to a sluggish halt. The watch, drowning in intended kindness, stops dead.
I see this same principle at work in our own attempts to build productive systems. We are the novices, desperately oiling the gears of our day. We layer on new apps to manage our old apps. We adopt complex methodologies, each with its own taxonomy and rule set, hoping the friction of starting will disappear. We create sprawling, color-coded calendars for what should be a simple meeting. We add more. We believe the solution to the feeling of being overwhelmed must be another layer of something—another tool, another hack, another notification.
But like the watchmaker’s oil, our well-intentioned additions often become the problem itself. The friction we sought to eliminate is replaced by the drag of over-complication. The system, meant to free us, demands its own maintenance. We spend more time updating our task manager than doing the tasks. We jump between tabs, contexts, and platforms, our mental gears gummed up by the very stuff we applied to make them run smoothly.
The watchmaker’s lesson is one of radical minimalism and precision. It asks: what is the absolute minimum effective application? Where is the genuine pivot point of friction in this project, and what is the single, precise drop of effort or tooling that will ease it—and nothing more? It is the courage to use a simple text file instead of a sprawling database. It is the discipline to have one trusted list, not seven. It is the understanding that the goal is not a frictionless life, but a machine that runs cleanly on the barest essential lubricant of structure. Apply your effort like the watchmaker’s oil: sparingly, precisely, and only where it is truly needed. Any more, and you risk stopping the very thing you’re trying to keep in motion.
Notes & further reading
A few pages I came back to while writing this: