The System is Not the Head

After attending a workshop with Philip Shepherd and reading Radical Wholeness, I kept returning to one idea: wholeness requires intention.

That is especially difficult in software engineering, a field that puts enormous pressure on us to live in our heads. We're expected to think ahead, stay ahead, and keep pushing ahead. We plan, predict, abstract, and optimize. Over time, this way of working can begin to feel almost entirely top-down—as though intelligence resides in the head and the rest of the body is merely there to carry it around.

Even our organizations tend to reproduce this pattern. We swing between top-down control and grassroots autonomy, as if those were the only choices. But both extremes can miss the meeting place in the middle: the connective tissue that allows the whole system to sense, communicate, and act as one.

I see this clearly in my work as a staff engineer. People become absorbed in their own projects, repositories, teams, and spheres of influence. Information is siloed. Each part may function well on its own, yet few people can feel what is happening across the system.

This feels analogous to living entirely in one's head.

The head begins to act as though it is separate from—and responsible for controlling—the body. It doesn't trust the rest of the system to hold it. But the head is not actually at the top of a hierarchy. It is one part of a continuous being, held in place and sustained by everything around it.

An organization works the same way. No single team, leader, or repository is the system. Each exists through its relationship with the others.

Ironically, we recognize the value of this wholeness most clearly during a crisis. When we're on call and something breaks, we reward the person who can see across boundaries: the application, its dependencies, the infrastructure, the users, and the history behind the decisions that brought us here. Debugging demands an awareness of the whole.

But why do we wait for a crisis before valuing that awareness?

If we remained more connected to the entire system—if we noticed its quieter signals before they became alarms—we might prevent some of those crises. The same may be true of our bodies. Shepherd's work invites us to notice what the head tends to supersede: the pain in our fingers and toes, the knowledge of the gut, and the bowl of the pelvis that helps us collect and settle ourselves. These signals are not distractions from intelligence. They are part of it.

This has also shaped how I think about AI development and calls to “slow down.” Perhaps what we need is not simply a pause or a reduction in speed. Perhaps we need to acknowledge that we have over-indexed on one part of the system while neglecting the whole.

We hyper-focus on a technology, a metric, a product, or a narrow idea of progress. We then try to force ourselves—and the world—into the mold created by that limited perspective. That may be how much of the world around me is structured, but it does not feel healthy for the whole.

It leads to burnout. It leads to rage and other extreme reactions. It narrows our capacity to work together.

Some of the workplaces that have resonated most deeply with me have explicitly recognized the humanity of everyone involved—not only developers or customers, but everyone touched by the system. Values such as starting with the human, practicing humility, making room for creativity, and remaining pragmatic matter because they resist reducing people to functions.

Wholeness does not ask us to stop thinking. It asks us to remember that thought belongs to something larger.

Whether we are considering a body, a software platform, an organization, or the development of AI, the work is similar: sense the relationships, listen to the neglected parts, and stop mistaking one part of the system for the whole.