Adaptability as a Discipline

Soldiers returning from combat without reintegration ritual struggle to inhabit civilian life. This is one of the most documented patterns in twentieth-century anthropology and clinical psychology.^[1] The work of war was finished, the body came home, the role had ended. What was missing was the marking. Where the marking happened — in Plains warrior return ceremonies, in the post-conflict cleansings practiced across many cultures, even in the parades and decompression weeks that some modern militaries still attempt — reintegration was substantially better. Where it did not happen, Vietnam being the cleanest negative case in living memory, the damage was generational.

There is a name for the pattern. Unmarked passage.

Most organizations currently going through AI transformation are running an unmarked passage. Their leaders do not know they are running one, because the language they have for the work is project management, and project management has no concept of marking. This is the leadership gap AI is about to expose, and it is more consequential than any deployment question.

The Deployment Frame Is Wrong

Most companies are treating the AI transition as a deployment problem. Choose the platform, license the seats, train the workforce, measure adoption. This was the frame for ERP, for cloud, for mobile. It worked, more or less, when the technology was changing the operating procedure but not the operating identity.

AI changes the operating identity. It changes what the company is for, what people are for in the company, what skills count, what trust hierarchies exist, what kind of decision is fast and what kind is slow, what the work even is. That is not a procedure shift. It is identity work, and identity shifts have to be marked.

This is not a soft claim. It is the lesson of a hundred years of anthropology, of veterans’ research, of organizational psychology, and of every Indigenous tradition that worked out the architecture of transition long before the modern firm existed.^[2] The architecture is functional, not aesthetic. When you skip it, the cohort moving through the transition gets damaged in predictable ways.

What Unmarked Passage Looks Like Inside an Organization

The symptoms of an unmarked transition are recognizable enough that an observer with the right frame can spot them in a leadership team within three weeks of an AI rollout. Different content, same shape as the symptoms in any other unmarked passage.

Most leadership teams running an AI transformation right now are producing several of these symptoms simultaneously. Not because the people are weak or the strategy is wrong. Because the passage has not been marked.

The Aramai and the Architecture of Marked Passage

The valley I walk through in Pacifica was Aramai territory. The Aramai were one of the Ohlone tribelets, part of the Ramaytush-speaking peoples of the San Francisco peninsula. Their villages stood in the San Pedro Valley, including Pruristac, near what is now the Sanchez Adobe Center. They were taken into the Mission Dolores system in the late 1700s, and contemporary Ramaytush Ohlone descendants are still here, still teaching, still working to recover what was disrupted.^[4]

What the Aramai and their neighbors understood, and what nearly every Indigenous tradition understood, is that a transition has to be structurally marked or the cohort moving through it gets damaged. A boy did not become a man by accumulating birthdays. He went through a structured passage: separation from the prior context, a liminal phase that was both dangerous and instructive, and reincorporation into the community as someone different. The community knew. The marking was the whole point.

A century later, the anthropologists Arnold van Gennep and Victor Turner mapped the same architecture across cultures. Separation, threshold, reincorporation.^[2] Indigenous initiations, monastic ordination, coronations, military reintegrations, every passage that successfully produced a new kind of person on the other side ran the same three-phase structure.

The Aramai would recognize the symptoms above. The pattern is generic. The diagnosis is fast.

What Initiation Actually Does

Each phase of the architecture does specific work that cannot be skipped without producing the symptoms.

Most leadership teams do none of these three. They do not separate, because they cannot afford to admit the old model is gone. They do not hold the liminal, because they reach for certainty before the new terrain has resolved. They do not reincorporate, because no one has named what the new identity actually is. They are stuck in a threshold they do not know they are in.

Project Management Has to Change Shape

This does not mean project management goes away. It means it has to be held differently. Five shifts in particular.

The plan changes function. From defended artifact to probe. It is the most coherent hypothesis available given current understanding, and it is expected to be revised as the terrain teaches the team what they did not know. The discipline is in updating it without losing momentum.

Milestones change function. From progress markers to threshold events that name “we are no longer the company that started this work.” Some of those moments need to be convened on purpose, because if they are not named, the team keeps operating from the prior identity even after it is functionally gone.

The leader’s role changes. From blocker-clearer to space-holder. The passage sponsor protects the team from premature certainty, names what is dying and what is forming, and absorbs the discomfort of operating without a finished answer. Many senior leaders have spent twenty years training the opposite reflex.

Reporting changes. Project status is green, yellow, or red against plan. Passage status asks where we are in the threshold, what signals we have read this week, what assumptions we have updated, what old vocabulary we are still using that no longer fits. The reason most transformation reporting reads as fiction is that it is using project artifacts to describe passage work.

Risk changes. The dominant project risks are scope, schedule, and budget. The dominant passage risk is freeze — the organization stalling in the threshold, refusing to fully release the prior identity, and starting to perform the new state without inhabiting it. The first job of the passage sponsor is to recognize when the team has slipped into theater and name it before it sets.

What I Learned Walking the Same Trails for Five Years

I live in Pacifica. The trails here — Mori Point, Sweeney Ridge, the spine of San Pedro Valley — look the same on a map. They are not the same on any given morning.

The fog moves with the marine layer and the wind that pushes through the gap between San Bruno Mountain and Montara. Some mornings it sits tight against the cliffs and the trail is washed in cold gray. Other mornings it lifts in the first hour and the bay flashes blue. Coyote brush flowers on a different schedule than the wild radish. The whales pass closer in some weeks than others. A trail that felt easy in February turns ankle-twisting after the spring rains soften the cut.

Walking the same ground repeatedly does something that walking new ground cannot. It builds a baseline. You begin to register the small things that have changed because you know what the morning is supposed to look like. The signal stops being noise.

This is the cognitive muscle the liminal phase actually requires. Reading change requires a baseline. A baseline requires repetition and attention. Most leadership careers do not include either.

The Catalyst Trail Walk

I take clients onto these trails. The exercise is simple. The discipline it builds is not.

We walk a defined route. I name three things to track. Wind direction, light angle, where the trail surface is softer than yesterday. The client narrates what they see in real time. Every fifteen minutes we stop and revise. What did I expect to see? What did I actually see? What does the gap suggest about my model of the next mile?

Then we map the same exercise to their organization. Three signals to track. Customer behavior, internal language, partner posture. We narrate. We stop. We revise. The discipline transfers because the underlying skill is the same. Hold a working hypothesis lightly. Notice the gap between expectation and observation. Update without ego.

The trail teaches what a slide cannot. The shift is too small to see if you are not looking, and too consequential to miss once you know to look. And the work happens on land that has held the practice of marked transition for thousands of years, which is not nothing.

What AI Exposes

AI does not create the problem of unmarked passage. It exposes it.

The pace of capability change is faster than any deployment cycle, which means leaders who run AI as a project produce the symptoms continuously, in public, in front of their boards, while their dashboards stay green. The leaders who have done their own initiation work — who can release the prior identity, hold the liminal phase, and inhabit a new operating identity rather than perform it — will compound advantage every quarter. The leaders who have not will keep running deployment plays into terrain that no longer accepts them, and producing patterns that any anthropologist or any Aramai elder would recognize on sight.

If you are running a transformation right now and you can feel that the bottleneck is not the technology, this is what you are feeling. The platform is fine. The cognitive posture is the gap. And the passage is unmarked.

That is the work.