The Potter's Centering: On Finding the Still Point Before the Spin

There is a moment on the potter’s wheel, before any vessel can be formed, that is more critical than any other. It is the moment of centering. A lump of clay is slapped onto the spinning wheel, and the potter’s wet hands must wrestle the chaotic, wobbling mass into perfect, silent alignment with the axis of the wheel. Until this is achieved, nothing of value can be built. Any attempt to pull the clay upward into a wall will result only in a shuddering, unbalanced mess. The foundation is everything.

We talk endlessly about the spin in our world—the relentless churn of data, the constant rotation of deployments, the dizzying speed of user requests. Our dashboards are a blur of graphs and metrics, all spinning out from a central point we assume is stable. But how often do we stop to ensure that central point is truly centered? We are so quick to build our services upward, to add features and complexity, that we forget the first and most vital step: finding the still point.

The Wobble in the Wheel

In pottery, a wobble is immediately apparent. It is a physical, visceral tremor in the hands. In our systems, the wobble is more insidious. It is the two-millisecond latency blip we dismiss as a network hiccup. It is the third-party API that returns a slightly malformed JSON object 0.1% of the time. It is the cache that populates almost, but not quite, instantaneously. We see these not as a fundamental lack of center, but as noise to be filtered out. We build our health checks to tolerate the wobble, to stay green as long as the service is technically ‘up’.

But the potter knows that a wobble, no matter how small, is a fatal flaw in the foundation. A pot thrown off-center will likely explode in the kiln; the stresses become unbearable under heat. Our services are no different. The small, uncentered irregularities are the very things that magnify under the fire of peak load or a partial network failure, leading to catastrophic and unexpected collapse. We mistake a passing green check for a centered system.

The true health check, then, is not a binary question of ‘up’ or ‘down.’ It is the potter’s question: ‘Is it centered?’ It is a measure of alignment, consistency, and predictable behavior under spin. It is the quest for that silent, humming core from which all else can be reliably formed. This requires a different kind of attention. It demands we look past the mere presence of a heartbeat and listen for its rhythm. It asks for observability tools not to alert us to a crash, but to show us the subtle, high-frequency vibrations that precede one.

Before we add another feature, another microservice, another line of code, we should first place our hands on the spinning core of what we have. Our job is not just to keep the wheel turning, but to feel for the wobble—and to have the patience to stop, add water, and re-center the entire mass until it runs true. Only from that perfect, quiet stillness can we build something that will truly hold.

Notes & further reading

A few pages I came back to while writing this: