The Sovereign

Seven postures facing AI: the Sovereign.

A fashion multinational — one of our clients — banned any AI project by definition for the first eighteen months. The risk of sending data to servers outside their control was considered unacceptable, and that was enough. No prototypes, no experiments, not even a theoretical thought about value. Eighteen months without a single attempt. They did eventually start, but with constraints that today keep generative AI well below what it could deliver. They paid the price of absolute caution. And they’ll keep paying it.

But the Sovereign isn’t that company. It’s a posture, and that ban is only one specimen. You recognise it in the developer who says: “nobody writes classes the way I do, so no AI.” In the professional who defends their craft and sees in AI only the erosion of their expertise. In the company that calls third-party AI “a transfer of know-how whose limits I can’t see.” Different roles, the same gesture: faced with an AI opportunity, the first question isn’t “what can I gain?” It’s “what can I lose?” And often, they never move on to the next question.

It’s understandable. When you’ve built a domain, it’s natural to defend it. That goes for those protecting data, those protecting know-how, those protecting a craft. They always see, first, what they might lose.

The blind spot is that the Sovereign calls their own stopping prudence — but it isn’t. They convince themselves that seeing the risks is enough. It isn’t. Real prudence suspends the risks for a moment, looks at the value, and only then brings them back into play to capture it. The Sovereign never reaches the “after.”

The Sovereign has their defences up before understanding what they’re defending against.

P.S. In the next article: the Process Thinker. The one who immediately sees the system in AI — not the people.

Scroll to Top