Signals are observations through the lens of Theory A. Each explores one aspect of a broader worldview about organizations, intelligence, and human agency.

TheoryA.aiSignal

Can Your Company Survive AI Transformation?

Jim Scully

Not every company can transform in place. That’s the honest answer nobody puts in the consulting brochure.

Most organizations approach AI transformation the same way: assess the current state, design the future state, build a roadmap, execute the plan. Reasonable. Methodical. And for many, it stalls at exactly the same point.

I call it Stage Four Stalling. The pattern looks like this: you define outcomes, build better visibility into operations, install signal architecture that tells you what’s actually happening in real time. You now have better eyes than you’ve ever had. And then — nothing changes. Because seeing the problem and responding to the problem are two different organizational capabilities. Better dashboards don’t help if the same three-week approval chain stands between the signal and the action.

“Seeing the problem and responding to the problem are two different organizational capabilities.”

The organization develops what I think of as antibodies. Remove a formal approval step, and an informal one grows back — because the people who built those steps still have the same incentives, the same fears, the same need to demonstrate value. Train people in new ways of working, and they revert within weeks — because the structure rewards the old behavior. You’re changing the process, but not the system that created the process.

This is where leaders have to make an honest assessment. There are three viable paths forward, and the right one depends on how deeply embedded the old model is.

The first is incremental migration: define outcomes, build signals, pilot in one domain, prove the model, expand. This works when the culture is receptive and the institutional resistance is manageable.

The second is selective adoption: pick specific elements of the new model — outcome orientation, signal architecture, management unbundling — and implement them as standalone improvements without committing to full transformation. Lower risk. Lower reward. But real progress.

The third is the parallel build: construct the new operating model alongside the existing one. Staff it with people who self-select. Let work migrate naturally as the new model proves itself. The legacy operation continues running while the new one grows. This is the hardest to accept politically — it feels like giving up on the existing organization. But for companies with decades of accumulated process and deep institutional habits, it may be the only path that doesn’t stall.

The diagnostic questions are uncomfortable but necessary. When you remove an approval step, does the organization accept it or route around it? When you give people authority to act, do they use it or wait for permission anyway? When AI produces a recommendation, do your people evaluate it or override it out of habit?

But perhaps the biggest reason for the parallel build option is organizational backlash. As work shifts to AI, employees will be displaced. In response, employees will read the writing on the wall with justifiable fear. The best employees — the ones you really need in the future — will find jobs elsewhere. Only the ones with no options will stay. No organization can survive long under these conditions.

The answers tell you which path is realistic. Not which path you prefer — which path your organization can actually walk.

The companies that survive AI transformation won’t be the ones with the best strategy decks. They’ll be the ones honest enough to choose a path that matches their actual organizational capacity for change.