The Cobbler's Awl and the Clarity of the Single Point

There’s a quiet violence to the cobbler’s awl. It’s not the blunt force of a hammer or the broad sweep of a sander. It’s a tool of intention, designed to do one thing with devastating precision: pierce. Before thread can bind leather, the awl must first make a path. It concentrates immense pressure onto a tip no wider than a pin, creating a clean, deliberate hole where none existed. The entire strength of the arm is focused into that one, perfect puncture.

Our modern workflows are the antithesis of the awl. We are the hammer, trying to flatten a dozen tasks at once, or the sander, rubbing frantically at a dozen rough edges until we’ve created a fine dust of half-finished efforts. We call this ‘multitasking,’ but it’s really just a state of constant, diffuse pressure. Nothing gets pierced. Nothing gets properly joined. We end the day with a pile of superficially touched work, all of it still in pieces.

I’ve started practicing what I call the 'Single Point' technique, and it begins not with a tool, but with a question. When the fog of the day’s demands rolls in, I look at my list and ask: What is the one thing that, if pierced completely, will make everything else easier or unnecessary? This isn't about the most urgent task, or the loudest one. It’s about finding the critical pivot, the piece of leather that, once punctured, will accept the thread that binds the whole project together.

The Anatomy of the Puncture

Applying the technique is simple, but it requires a stillness we often resist. First, you must stop. Put down the hammer and the sander. Look at the material in front of you—the report, the codebase, the design brief. Identify the single point of maximum leverage. It might be the central argument of the report’s introduction, the core function of the code, or the primary user flow of the design.

Then, you lean in. You apply all your focus, all your mental pressure, onto that one point. You close every other tab, mute every notification, and for a predetermined span—say, forty-five minutes—you do nothing but push. You write that introductory paragraph until it’s unassailable. You build that core function until it runs flawlessly. You map that user flow until it’s intuitive. You don’t smooth the edges. You don’t fix the spelling in the appendix. You pierce.

The result is a clean hole. A tangible breach in the resistance of the work. From that one clean puncture, the rest of the stitching becomes possible. The thread of your progress has a clear path to follow. What felt like a sprawling, shapeless project now has a defined starting point and a logical next step. The clarity is immense.

This isn’t a call to work on only one project a day, but to work on one point at a time. You might puncture three or four different projects in a day, but each will have received the full, undiluted force of your attention. At day’s end, you’re not left with a blur of activity, but with a series of deliberate, meaningful holes—the unmistakable marks of real progress, one sharp point at a time.

Notes & further reading

A few pages I came back to while writing this: