The quantum train – Seventh station: those left on the platform

Major technological disruptions often produce a surprising phenomenon. When their consequences become visible, many people feel they appeared out of nowhere. Yet looking back, the early warning signs had been present for a long time.

Personal computing, the internet, smartphones, cloud computing, and more recently generative artificial intelligence have all followed a comparable trajectory. For several years, these technologies seemed to interest mainly researchers, a few innovative companies, or enthusiasts. Then, almost without warning, they stopped being subjects of experimentation and became the market's new benchmarks. Quantum computing will most likely follow a similar trajectory.

Imagine an organization that, for several years, hears about this technology without really changing its priorities. Its executives know the subject exists. They read a few articles, attend the occasional conference, and agree that it will have to be looked into one day. The timelines still seem distant, other projects are already keeping the teams busy, and nothing appears to justify immediate mobilization.

This decision seems reasonable. After all, day-to-day emergencies are numerous and resources remain limited. Why invest today in a transformation whose effects may not be perceptible for several years? Meanwhile, the context gradually shifts.

Vendors begin integrating new security mechanisms into their products. Standards bodies publish recommendations that will shape the next generations of software. Major financial institutions, governments, and certain industrial sectors quietly begin their migration work. A few competitors invest in training their teams and carry out their first cryptographic inventories. None of this yet causes any visible disruption. And yet the landscape is slowly changing.

Then comes the moment when a client demands new security guarantees. A business partner imposes different standards. A request for proposals calls for compliance that did not exist a few years earlier. Insurers reassess their risk criteria and regulators clarify their expectations. Within a few months, what was once a matter of foresight becomes a concrete requirement.

The organization then realizes that it does not know precisely the full extent of its cryptographic mechanisms. It discovers that some applications rely on aging components, that several essential bodies of knowledge are concentrated in the hands of a few specialists, and that the interdependencies among its systems are far more numerous than it had imagined.

The real problem is not quantum computing. The real problem is time. The companies that began their thinking several years earlier are not necessarily wealthier or better equipped. They simply did not wait for an emergency to understand their dependencies, document their environments, and define a roadmap. They now enjoy the luxury of being able to plan their decisions rather than endure them.

Conversely, those that have continually postponed this reflection discover that the months gained yesterday become years lost today. They must simultaneously understand their systems, reassure their clients, modernize their infrastructure, and develop the skills they were lacking.

Economic history shows that great disruptions do not always reward the most powerful organizations. They often favor those that were able to recognize the first signals of change and use time as a strategic advantage. Preparation does not eliminate challenges, but it prevents them from turning into crises.

Quantum Beyond is convinced that the real question is not which organizations will adopt tomorrow's technologies. They all will, eventually. The difference will lie in how they prepared for that transition. Some will see it as a natural evolution of their strategy. Others will feel they are chasing a train they had nonetheless watched approaching for years.

Every technological revolution inevitably leaves a few travelers on the platform. Not because they lacked talent or resources, but because they had underestimated the speed at which the world could change. The best way to avoid this scenario is not to predict the future perfectly. It consists of building, starting today, an organization capable of adapting to it when the next train pulls into the station.