Really interesting story about Harvest, a specialized code breaking computer built in the 1960s by IBM for the NSA.

Plug a phone into a modern charger and the first 10 minutes are impressive. The next 20 are not.

This is not a defect. It’s the connected device protecting itself. As temperature rises during charging, a smartphone’s battery management system reduces the current it will accept, because heat accelerates the chemical degradation that permanently reduces battery capacity. The charger may be capable of delivering more, but the device simply stops taking it.

For anyone building products in the portable power category, this creates an uncomfortable gap between specification and experience. A device rated at 25 watts is accurate in the sense that it can deliver 25 watts. Whether it delivers 25 watts for the duration of a charge is a different question, and one the specification does not answer.

The specification gap

The gap matters commercially because it is invisible at the point of purchase and obvious in use.

Consumers compare wattage figures on packaging. They don’t compare thermal curves, because thermal curves are not published publicly. The result is a category where products differentiate on a number that describes peak output rather than sustained output, and where the actual user experience of two products with identical specifications can diverge substantially.

This is particularly acute in magnetic wireless charging. Inductive power transfer generates heat at both the transmitting and receiving coils, and the magnetic attachment that makes these products convenient also places the heat source in direct contact with the device it is charging. Convenience and thermal performance are working against each other by design.

The industry’s response for the past several years has been materials science. Graphite sheets, thermal interface materials, conductive housings, and heat-spreading layers have all improved how efficiently accumulated heat moves away from the source. Each generation has been incrementally better than the last.

But passive dissipation has a structural limitation: it can only move heat that has already been generated, and only as fast as the surrounding air will accept it. In a sealed, pocket-sized enclosure, that ceiling arrives quickly. Improving the materials slows the rate of temperature rise. It does not prevent the temperature rise.

Moving from dissipation to removal

The alternative is active thermal management, which is standard in stationary electronics and largely absent from portable ones for reasons that are easy to understand. Fans add volume, weight, moving parts, and noise. In a product category defined by portability, each of those is a meaningful cost.

At Anker, which manufactures charging and power products, engineering teams spent the past several development cycles working on whether that tradeoff could be made acceptable rather than eliminated. The approach involves several interacting systems: a micro centrifugal fan, dual airflow channels routed to avoid interference with the magnetic array, a three-layer graphene heat-spreading layer, and a control algorithm that modulates fan speed based on real-time temperature and battery state rather than running at a fixed rate. The result is that the Anker MagGo Power Bank 2 Pro has become the world’s fastest and coolest wireless power bank.

In internal testing, at 77 °F (25 °C) ambient, the back of the power bank stays below 96.8 °F (36 °C) throughout wireless charging, 21.6 °F (12 °C) below the international standard limit of 118.4 °F (48 °C), for a comfortable grip. Comparable magnetic power banks in the same testing typically reached 113 °F (45 °C) or higher within 20 minutes. The functional consequence is that the connected device does not reach the threshold at which it begins reducing charge acceptance, so 25 watts of Qi2.2 magnetic wireless charging is delivered as a working rate rather than an opening rate. In practice, an iPhone 17 Pro reaches 50% charge in 25 minutes. The Anker MagGo Power Bank 2 Pro’s premium performance in both charging speed and thermal management is certified by SGS, an independent testing and certification company.

The same principle applies in reverse. Recharging a power bank generates heat too, which is why devices in this category are often slow to recharge, leaving users with an empty accessory at the moment they need it. Active cooling during input allows the unit to accept 45 watts and reach 80% in 52 minutes.

What this suggests about the category

There is a broader pattern here worth naming, because it is not unique to charging.

When a category improves along a single axis for long enough, the constraint usually migrates somewhere else. Charging spent a decade optimizing power delivery. Power delivery is now, for most practical purposes, solved: the electronics can supply more energy than the receiving device is willing to accept. The binding constraint moved to thermal management, and the industry continued optimizing the axis it had always optimized, because that is the axis the specifications describe.

Recognizing when a constraint has moved is difficult precisely because the old metric keeps improving. Wattage figures have continued to climb. Products have continued to get faster on paper. The measurement stayed valid while quietly ceasing to describe the thing users experience.

For product organizations, the practical question is whether their specifications still measure the constraint or merely measure the capability. The two align until the constraint shifts and specifications rarely shift with it.

The transparency problem

A second implication follows from the first. If sustained performance differs meaningfully from peak performance, and if only peak performance is disclosed, then buyers cannot evaluate the products in front of them.

This is one reason Anker is adding displays on charging products. The Anker MagGo Power Bank 2 Pro shows real-time power, temperature, battery level, and estimated time remaining. Some of that is user convenience. But some of it is a Anker stating a deliberate position—this category deserves to have the complete and accurate data made transparent to all.

Anker expects independent reviewers to test these claims and considers our internal numbers to be the correct outcome. The gap between specification and experience closes faster when the experience is measurable. The Anker MagGo Power Bank 2 Pro will be available in the U.S. on September 17, 2026.

This content was produced by Anker. It was not written by MIT Technology Review’s editorial staff.

Throughout the history of the computer chip, engineers have treated waste heat as an inevitable cost of a calculation. Hannah Earley, however, thinks it’s a design choice. Earley, 31, is cofounder and chief technology officer of Vaire Computing, a startup building chips that recycle energy usually thrown away as heat—a strategy known as reversible computing. Ultimately, she thinks, this approach could help make data centers (and our laptops and phones) much more energy efficient. 

When conventional computer chips perform calculations, they erase the information they no longer need along the way, dissipating energy as heat in the process. Earley compares the approach to racing through a city only to pump the brakes at every intersection: The car loses momentum and must burn more fuel to accelerate again. Reversible computing aims to keep the momentum going—instead of erasing information from the intermediate steps in a calculation, the circuit retains it, making it possible to run the computation backward and recover some of the energy.

While the idea was first proposed more than 50 years ago, it proved impractical to implement with existing transistors and circuits. Earley, though, has completely rethought the hardware needed to make energy recovery work. She designed a patent-pending type of resonator—a microscopic chip component that stores recovered energy for later reuse. “It’s really a glorified pendulum,” she says. Last year, Vaire announced a key breakthrough: a chip with a resonator that recovered more energy than it lost, even after the energy needed to power the component was taken into account. For a subfield that has existed mostly in theory, the result was proof of life.

“It’s clear they have something interesting,” says Igor Markov, a researcher in electronic design automation and a former professor at the University of Michigan, Ann Arbor. Still, he says, the technology is quite early stage; the company will need “a series of increasingly realistic and convincing demonstrations to attract the industry support needed for commercialization.” 

She gradually became convinced that the connection between information, energy, and heat could change computers forever.

Earley’s journey into chip design started sooner than most. She began programming around the age of nine, starting with high-level coding for the web before digging into other programming languages like Perl and Java. She continued progressing to more and more abstract layers of computing, until she got all the way down to transistors.

She eventually enrolled in a PhD program at the University of Cambridge under the computational biologist Gos Micklem. She started out studying how materials such as DNA could be used to perform calculations, but a few months in, Micklem sent her the 1999 PhD thesis of Michael Frank, a pioneer in reversible computing. Earley read it once, felt skeptical, read it again, and sat with it for a few weeks. She gradually became convinced that the connection between information, energy, and heat could change computers forever.

The fascination completely redirected her PhD work. Earley studied the physical limits of computation and built software that could turn ordinary programs into reversible ones. “Eventually I wouldn’t let her put my name on any of her papers, because I felt that I couldn’t really stand up and give a proper talk about them,” Micklem recalls. “It was her stuff.”

After completing her degree in 2021, Earley met Rodolfo Rosini, a technology entrepreneur and investor. The pair cofounded Vaire that same year, and the company has since raised more than $12 million, hired Frank as a senior scientist, and begun turning the vision of reversible computing into real hardware.

Innovation, however, doesn’t happen overnight. During the winter of 2022 in Grinnell, Iowa, Earley spent weeks in her now-wife’s basement apartment as the wind chill outside reached roughly −40 °F, covering a whiteboard over and over again with schematics for the core piece of circuitry needed to make reversible logic work. By the time the design finally came together, after the couple had escaped the cold for Las Vegas, it felt less like an aha moment and more like a gradual wave of relief. “I’m not completely out of my depth,” she remembers feeling. 

Earley and her colleagues’ next challenge is making their drastically different chip fit into familiar devices and manufacturing systems. She believes that’s where the future lies—not in further refining existing chips but in rebuilding them from the ground up with an eye toward reversibility. “I want to tackle every part of how computers are built,” Earley says, “and rethink it in these terms.” 

Some of the world's leading democracies are pushing governments and companies to start preparing for post-quantum cryptography before quantum computers become powerful enough to break the encryption systems that protect global digital infrastructure today.

In a joint advisory released Thursday, the G7 Cybersecurity Working Group and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) said organizations should begin their transition to post-quantum cryptography now, rather than waiting until cryptographically relevant quantum computers (CRQCs) are available to threat actors.

Why the Post-Quantum Cryptography Shift Cannot Wait

The publication, titled "Preparing for the Post-Quantum Era: A Call to Action," warns that the quantum computing threat is no longer a distant concern. While the exact timeline for CRQC development remains uncertain, the working group said recent technological advances suggest such machines could emerge sooner than expected, putting widely used public-key cryptography mechanisms at risk.

One of the most immediate dangers is a tactic known as "harvest now, decrypt later," where malicious actors intercept and store encrypted data today with the intention of decrypting it once a CRQC becomes available. This poses a serious risk to governmental records, sensitive personal data, and trade or business secrets that require long-term confidentiality.

The advisory also cautions that CRQCs could eventually be used to target authentication mechanisms, allowing bad actors to impersonate trusted entities, forge data, or compromise equipment. Because supply chain vulnerabilities can cascade, a single organization's delay in adopting post-quantum cryptography could expose entire sectors to compromise.

According to the report, organizations that fail to act may also face business consequences beyond security risk, including exclusion from public procurement contracts and loss of competitive advantage.

Five Priorities for the PQC Transition

The G7 Cybersecurity Working Group outlined five priority areas to guide the global shift toward post-quantum cryptography:

1. Raising awareness — Many organizations still view the quantum threat as a distant or purely technical issue. The group called for awareness campaigns, technical guidance, and workforce upskilling to reframe it as an economic and business risk.
2. Developing national strategies — Countries are encouraged to build strategies that ensure an adequate supply of quantum-safe hardware and software while encouraging adoption, integrating the effort into broader digital privacy and security policies.
3. Advancing research and development — Governments should fund research programs and support pilot projects and testbeds to help organizations test and refine their transition to post-quantum cryptography.
4. Building public-private partnerships — Collaboration between government, industry, and academia is seen as key to developing domestic expertise, lowering transition costs, and sharing playbooks and case studies across sectors.
5. Integrating PQC into cybersecurity requirements — The group recommends treating post-quantum cryptography adoption as a natural evolution of cryptographic best practice, and embedding requirements into public procurement to push both vendors and organizations toward quantum-safe systems.

The advisory emphasizes that the shift to post-quantum cryptography cannot be solved by individual organizations in isolation. Instead, it calls for early engagement, coordinated planning, and informed decision-making across public and private sectors worldwide.

Tackling the risks that the impending quantum computing era poses to current cryptographic systems... requires a coordinated global effort to transition to PQC," the report states, adding that public and private organizations must act now to safeguard confidential data, supply chains, and critical systems.

The document was jointly published by cybersecurity authorities from Canada, Germany, Italy, Japan, the United Kingdom, the United States, and France's ANSSI, with participation from the European Commission and support from the EU Agency for Cybersecurity (ENISA).

For years, legacy technology has been a problem companies knew they needed to solve, but one they often struggled to tackle. The cost, complexity, and risk of replacing business-critical systems could make modernization feel like a disruption to manage instead of an opportunity to pursue. But with the rise in customer expectations and the changes AI brought to the economics of software development, that calculation is changing. Bupa’s modernization of its My Bupa mobile application offers a case study in what becomes possible when a legacy migration is treated as a business transformation rather than a technology rewrite.

Bupa CIO of health insurance Asifa Sherazi describes the risks of waiting for legacy systems to become an emergency: “The end-of-life technology is a risk that compounds quietly, and then arrives all at once.” For Bupa, moving its application from Xamarin to native Swift and Kotlin improved the app rating from 3.7 to 4.7, while the user-perceived crash rate fell by nearly 24 percentage points on Android and eight points on iOS. “What they’ll notice is that when they need us, often at a stressful moment, it just simply works,” Sherazi says.

Sanjeev Tripathi, senior vice president and region head of BFSI, healthcare, and public sector for Australia, New Zealand, and Southeast Asia at Infosys, contends that AI is helping change the equation. “The emergence of AI is fundamentally shifting the economics of modernization,” he says, reducing the effort, risk, and time traditionally associated with these programs. At Bupa, combining AI-assisted reverse engineering with forward engineering helped deliver the transformation in approximately 60% less time than would have been possible in the pre-AI era.

Sherazi and Tripathi also highlight the human dimension of modernization: preserving institutional knowledge, giving teams capacity to adapt, and creating an environment where employees can surface problems early.

Looking ahead, both experts see modernized platforms as foundations for more personalized, predictive and AI-driven experiences. The payoff of modernization may be less about replacing aging technology and more about building the flexibility needed for whatever comes next. 

“Modern platforms will become the base for far more intelligent AI-driven ecosystems, where AI is not just an add-on, but it is built into everything from design to operations. That’s how the modern platforms will evolve, and the customer experiences will become far more personalized and predictive,” says Tripathi. For Sherazi, that shift is already changing the questions organizations can ask: “It used to be, can our platform support that? Now, it’s: is that the right thing to do for our customers?”

This episode of Business Lab is produced in partnership with Infosys.

Full Transcript:

Megan Tatum: From MIT Technology Review, I’m Megan Tatum, and this is Business Lab, the show that helps business leaders make sense of new technologies coming out of the lab and into the marketplace.

Our topic today is legacy modernization. Companies across industries continue to struggle to bring AI modernization to legacy technology stacks, increasing the risk of losing vendor support, degraded customer experience, and limited capacity for innovation.

Two words for you: future-ready foundation.

My guests are Asifa Sherazi, who is CIO of health insurance at Bupa, and Sanjeev Tripathi, who is senior vice president, region head of BFSI, healthcare, and public sector for Australia, New Zealand, and Southeast Asia at Infosys.

This podcast is produced in association with Infosys.

Welcome, Asifa and Sanjeev.

Asifa Sherazi: Thank you, Megan. Delighted to be here.

Sanjeev Tripathi: Thanks, Megan. Wonderful to be here. And good talking to you again, Asifa.

Megan: Thank you both so much for being here. Asifa, if I could start with you just to set the context for our conversation. There are seven million healthcare customers across the Asia-Pacific. Could you tell us a bit more about Bupa and the challenges it’s faced in its modernization plan?

Asifa: Yes, absolutely. Let me start with something about Bupa that shapes everything we do. We are a global healthcare organization. Think hospitals, clinics, dental, age care, digital health, alongside our insurance business. We reinvest back into the organization, so into our services, our capability, our teams, and our outcomes that we deliver for our customers. In Asia-Pacific, we serve around, as you said, seven million customers across health insurance and health services, individuals, families, corporate clients, patients. Our purpose, helping people live longer, healthier, happier lives is more than just a statement. It actually shapes our strategy, guides our investment decisions, and influences the choices our teams make every day.

Now, for most of our health insurance members, the day-to-day digital relationship with Bupa begins through My Bupa, our self-service platform. It’s the front door for managing cover, updating policy details, submitting claims, checking entitlements. Alongside of it, Blua plays a complimentary role. Where My Bupa helps members manage their cover, Blua helps them manage their health, digital healthcare services, clinical support, preventative health. And together, they let us move beyond transactional interactions towards more personalized, proactive care.

Here was our challenge. Our mobile app, My Bupa, was built on Xamarin, and Microsoft support for it ended sometime in 2024. We had extended support in place, so our customers remained protected throughout, but we were clear-eyed that this was a bridge, not a destination. The runway was finite, and it was shortening for us. We made the decision to modernize from a position of stability proactively for the long-term safety and experiences of our customer rather than waiting until circumstances forced our hand, because the platform carrying our most important customer relationship was in effect standing still while the world around it was moving.

Megan: Right. So you decided to act really proactively in that sense. And so, Asifa, what are some of the risks then of sticking with end-of-life technologies, and how will moving away from legacy technologies help you improve the customer experience?

Asifa: Yeah. Look, the end-of-life technology is a risk that compounds quietly, and then arrives all at once. We saw it in three ways. The first is security and compliance. Once a technology is out of vendor support, the flow of security updates and fixes changes fundamentally. In our case, we put extended support in place as a bridge so our customers stayed protected. But extended support buys you time, it doesn’t buy you a future. In healthcare, we hold some of the most sensitive information a person will ever share with an organization. That isn’t data to us, it’s trust. And trust is extraordinarily expensive to rebuild. We weren’t prepared to run that risk on a shortening runway.

The second is losing control of your own roadmap. How I’d explain that is iOS and Android don’t stand still. Every operating system release, every change to app store requirements becomes something that you react to rather than plan for. As each one slows you down a little further, over time, that opens a widening gap between what customers expect and what you can actually give them. We’re all customers. We don’t benchmark a health insurer against other health insurers. We benchmark against whatever app we used last.

And the third way was, and this is one we’d flag for peers, is the shrinking talent pool. Xamarin is legacy technology, and the engineering expertise available for it is limited. You end up with a critical customer platform supported by a narrowing group of specialists. That’s a workforce risk wearing a technology costume. We partnered with Infosys and we migrated the entire application estate from Xamarin to fully native Swift and Kotlin, and the customer outcomes are why we’re comfortable talking about this today. Our app rating moved from 3.7 to 4.7. Some of the stats that I’d love to share are that the user-perceived crash rate fell by nearly 24 percentage points on Android and eight points on iOS. The Android login success per visit doubled back up to 77%, and that’s one the team that is most proud of, because a login failure isn’t a technical event. It’s a person who wanted to check their cover and they couldn’t.

The team achieved 100% feature parity in a single release, and 90% of our active customer base moved to a new version, and they’ve, I think, downloaded nearly 1.8 million unique downloads. From our customers’ perspective, customers will never think about any of this as a technology change, and they shouldn’t have to either. What they’ll notice is that when they need us, often at a stressful moment, it just simply works, and that’s the outcome we were really after.

Megan: Those are some really striking results and statistics that you’ve shared there on the success of the migration. I mean, Sanjeev, could you talk a bit about why modernizing legacy technologies is so critical at this time, and how Infosys has approached that transformation journey with Bupa?

Sanjeev: Sure, Megan. To be honest, legacy modernization initiatives are not new, and there has always been a strong desire to drive modernization across the entire technology landscape. And Asifa covered all the points that I was going to cover about the risks that have been there. But I’ll reiterate, the reality is the industry has been held back by the cost complexity, and also the risks that have been associated with any legacy modernization initiative that has been undertaken historically.

As Asifa mentioned, customer expectations of what was acceptable five, 10 years back are simply not acceptable anymore. The customers today expect a seamless, intuitive, responsive interaction across every channel. And Asifa also covered the growing challenges around security, resilience, talent availability, and so on. Finding talent on legacy technology is extremely, extremely difficult, and that introduces risk in every organization and in every legacy platform, most of which are actually business-critical platforms as well. Security vulnerabilities are getting increasingly difficult to manage, and as I mentioned, finding deep expertise in older technologies is very, very difficult now.

So what has changed? What has changed is that we now have new tools that are available to us to address these challenges. The emergence of AI is fundamentally shifting the economics of modernization, and it’s doing that by helping organizations to reduce the effort, risk, and also the time that is traditionally taken for programs like these, and that is why we believe that the time is now for legacy modernization. In fact, in Infosys, we have six strategic value pools that we have identified in our AI-first value framework, which is publicly available, and legacy modernization is one of these six value pools. And in the market, we are seeing very strong interest across our client base, and they recognize that the opportunity to unlock both technical and business value is now.

With Bupa in particular, we approached the journey as a business transformation rather than simply a technology rewrite, and our approach had two key phases. One is reverse engineering, and then forward engineering. Let me just quickly cover what these two are.

Reverse engineering, what we did is we extracted and we understood the rules, the processes, and the logic within the legacy environment, and that’s a standard approach we took, we take in any legacy modernization program. What that does is it allows us to preserve the critical business functionality, but at the same time, it avoids the risks that often come with large-scale migration programs.

The second aspect is forward engineering, where we re-architected the solution to enable a reimagined customer experience. The objective is not just a feature-by-feature migration or ensuring feature parity, which is important, but it is even more important that since we’re investing this kind of money to create a modern platform that is scalable, maintainable, and is also capable for future innovation, and that’s what Asifa mentioned about you need to be in control of your own roadmap. You have to build a platform which is capable of supporting future innovation as well. We essentially ensured nothing was lost in translation, and we significantly improved the platform stability and long-term maintainability. And some of the metrics that Asifa mentioned reflects the meaningful improvement in customer experience as well.

Finally, just one more point before I close this question is the time to market. I spoke about the time is now, and because we’ve got the power of the tools that are available now. What AI allowed us is to accelerate the transformation dramatically. What would have traditionally been a long and complex modernization, was delivered in approximately 60% less time than what would have happened in pre-AI era, and that is the real story.

Megan: So AI in this context is a real enabler in terms of the economics and the speed and all of those things you’re talking about. If I could come back to you, Asifa, as much as modernization is a technology challenge, there is the human component as well, and I wondered if you could talk about how you prepared employees for these new technologies, and what challenges and solutions you faced on that front as well?

Asifa: The human side of it is what I’m really passionate about. Technology was only half the challenge. The real work was helping people move from what they knew to what was possible. Modernization isn’t just about replacing systems, it’s about giving teams the confidence, the capability, the clarity to embrace a different future, and that’s what determines whether change actually succeeds.

From that experience, there were three human challenges that stood out for us. The first one was scarcity of expertise on both sides of the transition, and like we said before, Xamarin is a legacy app. We were moving away from a legacy technology, supported by a rapidly shrinking specialist talent pool, and modernizing onto two native platforms. Documentation of that existing environment was limited. Much of the operational knowledge sat in individual experience and in the code base itself, and that created a real dependency on a small number of people. And for the team, it was a confronting reality and a powerful reminder that modernization isn’t just about technology imperative, it’s actually a resilience one.

What changed the dynamic was using AI to do the archeology. As Sanjeev mentioned, Infosys applied AI-assisted reverse engineering to harvest the legacy Xamarin code and extract the flows, the rules, the business logic, and generate native-ready user stories and acceptance criteria from it. The team did a lot of work. They mapped hundreds, I think nearly 1,500 regression scenarios to native epics, and that way, parity critical journeys were preserved by design rather than by memory. The human effect was just as important. Knowledge stopped living with a handful of individuals and became shared across the team, and our people could spend less energy holding institutional memory and more on designing and improving. So that was the first challenge.

The second challenge, Megan, was capacity and not willingness. Our business analysts were fully committed to ongoing feature delivery. And this is a live customer-facing app, and you cannot pause improving the customer experience while you rebuild underneath it. AI-driven discovery and documentation removed almost an estimated of 400 hours of manual BA effort, and that’s not a headcount story, that’s actually people not being asked to do two full-time jobs at once.

The third challenge that stood out was pace. Our original internal estimate was around 18 months, and thanks to Sanjeev and the team, almost like a one-team approach of how do we tackle this, the team delivered it in seven, and that’s exhilarating.

t’s also demanding, and both things need saying out loud. We mobilized cross-functional squads across engineering, architecture, testing, release, because managing parallel environments while protecting BAU commitments is such an emotional load as well as a logistical one. We leaned in hard alongside the team, being present rather than reporting from a distance, regular check-ins, genuinely listening to concerns, unblocking things quickly so people weren’t sitting waiting on a decision. And Megan, one thing I’ll say is when you’re compressing 18 months to seven, the most useful thing leadership can do is remove the friction in front of someone else and get out of their way.

But the thing that made the biggest difference was surprisingly simple, actually. We built a visual depiction of the transformation journey, and we updated it every month so the team could actually see how far they’ve come. Because when you deepen migration of this scale, it’s really easy to only see what’s left to be done, and being able to look back at the ground that’s already been covered gave people real intent and real momentum. And genuinely, it was exhilarating to watch. Watching the team’s pride became their fuel.

Megan: I love that idea of it being exhilarating, but exhausting. I think that’s a great description.

Asifa: Yeah. And the leadership lesson for all of us was just simpler than any of it. Programs like this have hard weeks, there’s going to be incidents, delay, difficult conversations. And Sanjeev, you and I have had those conversations many times. The job of leadership in those moments is to absorb the ambiguity rather than transmit anxiety, because if people feel safe telling you bad news early, there’s almost nothing you can’t fix. I say this plainly because it’s the truest thing about the whole program. I am so incredibly proud of this team, because what they achieved in seven months, while continuing to serve customers every single day without disruption, was genuinely remarkable. But what I’m really proud of isn’t the speed and it isn’t the engineering, it’s that the team never lost sight of who it was for, so every decision that we were making, and they came back, it just came back to the person at the other end of the app.

Megan: It sounds like you did an incredible job focusing on that people element just as much as the technology, which is so important. And Sanjeev, we’ve heard some of the incredible results Bupa has had with this, but more broadly, I suppose, looking across modernization use cases, where do you find that companies see the most ROI, and what advice do you have for leaders who need to focus on transformation at that legacy level?

Sanjeev: Thanks, Megan. That’s a very important and actually a very good question, because what we see is modernization ROI is sometimes viewed too narrowly through just a technology lens, and as Asifa mentioned, it is broader than just technology. Legacy modernization has aspects associated with business implications as well, so I’ll just cover that very quickly.

There are two dimensions, as I mentioned. One is technical ROI or technology-related ROI, and second is business ROI. On the technical side, and as you heard from Asifa as well, the biggest benefits come from faster time to market, platform stability and resilience, of course, and a lot of times, in fact, almost in all the cases, lower operating costs, and that is one of the aspects associated with some of the legacy modernization programs.

Besides this, access to broader, more readily available talent pool, and security management, and ensuring that the platforms are secure and free from, as much as possible, free from vulnerabilities in the current environment. At the same time, making it easier to innovate, releases become faster so that the feature delivery into the market becomes faster, and also able to respond to any new technology innovation that comes into play. But this is only on the technology side.

On the business side, however, the returns are often reflected in customer outcomes, and what we typically see are improvements in measures such as net promoter score, and in this case, for example, application ratings that you see on the app store. Both of which are actually very strong indicators of customer satisfaction and digital experience quality. I think it is important for us to cover, look at the ROI from both technology, but more importantly, from a business perspective.

The second part of your question was about what would be my advice to leaders, and I think Asifa covered it very well, where she mentioned that the one-team approach, the providing safe environment to the team to be able to say what is going well, but also what is not going well, and keeping your eye on the end outcome. I think those are very important things. But I would also like to add that don’t treat modernization as a technology initiative. It is a unique opportunity for us to rethink the business platform itself, and rather than pursuing a like-to-like migration, use the investment that you’re making to improve customer experience, simplify processes, and re-architect for capabilities such as real-time personalization and data-driven decision-making. The greatest returns come when technology transformation is directly linked to business outcomes.

And finally, and this is something that I have seen from personal experience multiple times, is you have to think from first principles. AI does not replace good engineering practices. It enables organizations to execute those practices faster, and it enables it faster, but also more consistently and at greater scale. The foundations of good architecture, sound engineering, and clear business objectives will continue to remain important, and in fact, their importance is going to increase as we progress. That, I think, is what I would say anybody embarking on a legacy modernization program should be focused on.

Megan: I love the idea that this is not just about migration. This a chance, as you say, to reimagine what you can deliver and what’s possible. Fantastic. Let’s close with a forward look. Asifa, what innovation are you looking forward to that wouldn’t have been possible before this, and what do you see on the horizon?

Asifa: There’s definitely lots of things on the horizon. But what excites us most isn’t specific technology, it’s that the question in our conversations has changed. It used to be, can our platform support that? Now, it’s is that the right thing to do for our customers? And that’s a profound shift.

There’s three things, Megan, that genuinely weren’t possible before, and we’ve touched on this a little bit, and Sanjeev’s touched on it as well. This first is speed as a permanent capability. Since launch, Android and iOS, the team has shipped multiple rapid-fire releases, including our migration to a new payment gateway. Builds are now completing four times faster, codes are reaching to testers in about an hour, and we’ve reduced our code base by 30%, and our application footprint’s reduced 18% as well. A simpler estate isn’t an aesthetic preference anymore, it’s what makes the next change cheap, and we’ve bought ourselves optionality to do that.

The second is quality at that speed, which is the part we’ve been most skeptical about five years ago. AI-driven triage and predictive defect analysis, we ran it across nearly 1,400 cases to focus on testing on the highest risk journeys, which meant we went live with zero security defects and zero high severity defects, and Sanjeev mentioned that just before. The old trade-off between moving fast and moving safely is being renegotiated right in front of us, so that’s the second point.

The third one is AI-driven accessibility testing, which the teams treated as a critical rather than an optional opportunity. In healthcare, people who most need to reach us are very often the people whom our poorly designed interface is a genuine barrier, and so being able to test that systematically at scale was a real advance for us as well.

And Megan, you mentioned on the horizon. It’ll be remiss of me not to take the name of agentic AI. The shift from AI that supports a task to AI that completes an outcome end-to-end with proper governance, human oversight at the key decision points. What this program showed us is that the constraint is no longer the models. It’s whether your platforms, data, processes are modern enough to let AI act safely, which is precisely why this work mattered now. Sanjeev alluded to it as well about that underlying architecture. Responsible AI as a source of advantage, not a compliance exercise, I would say. In health, if people don’t trust how you’re using their information, nothing else you build matters. We didn’t modernize to have modern technology. We modernized to earn the right to do the next thing, and to do it in weeks rather than years.

Megan: Absolutely. And now you have those foundations in place, like you say, all of these opportunities open up. Fantastic. And Sanjeev, just finally, as companies complete these migrations, what kinds of innovations and benefits are you seeing, and what do you expect in the next five years?

Sanjeev: Sure. Again, good question, Megan. The reason is there is no uniformity on how these migrations are being done even today. As I mentioned earlier, so where there is simple lift and shift of existing code base onto a new platform, a like-to-like replacement, the benefits generally tend to be limited. Where we apply first principles, thinking about re-imagining, re-architecting, and refactoring the system to establish foundations for a far more flexible system, where rules are not boxed into the architecture, but are managed in a way that changes can be incorporated faster, personalization can be achieved in real time, and time to market improves multifold. That’s where we are really seeing far more benefits coming through.

And to take the example of Bupa, it is a pretty clear step change, both in terms of customer experience and how fast teams can actually deliver now. I think the app ratings have gone up significantly. The customer experience has improved. Even simple things, such as login success rate, has improved quite significantly. And on the engineering side, we are now building and releasing features roughly about four times faster, and we are also seeing the migration of nearly 100% of the customers onto the new platform.

Now, if I look ahead over the next, you mentioned about next five years, I don’t know about five years, four years, but over the next few years at least, I think it is going to get very interesting, because modern platforms will become the base for far more intelligent AI-driven ecosystems, where AI is not just an add-on, but it is built into everything from design to operations. That’s how the modern platforms will evolve, and the customer experiences will become far more personalized and predictive. And even the way we build software will shift, with AI playing a much bigger role in the development process itself.

Megan: Fantastic. Really exciting changes on the horizon then. Thank you both so much.

That was Asifa Sherazi, who is the CIO of health insurance at Bupa, and Sanjeev Tripathi, senior vice president, region head of BFSI, healthcare, and public Sector for Australia, New Zealand, and Southeast Asia at Infosys, whom I spoke with from Brighton in England.

That’s it for this episode of Business Lab. I’m your host, Megan Tatum. I’m a contributing editor at Insights, the custom publishing division of MIT Technology Review. We were founded in 1899 at the Massachusetts Institute of Technology, and you can find us in print, on the web, and at events each year around the world. For more information about us and the show, please check out our website at technologyreview.com.

This show is available wherever you get your podcasts. And if you enjoyed this episode, we hope you’ll take a moment to rate and review us. Business Lab is a production of MIT Technology Review, and this episode was produced by Giro Studios. Thank you so much for listening.

This content was produced by Insights, MIT Technology Review’s custom content arm, not its editorial staff. It was researched and written by humans, with any AI tools that may have been used limited to production processes under human oversight.

Quantum computing has alternated between breakthrough darling and overhyped promise in technology circles. Its powerful new capabilities come with a threat to break current cryptography, but for business leaders navigating the noise, the signal should be clear: post-quantum cryptography (PQC) is a manageable evolution, not a crisis.

The mathematics behind today’s encrypted digital transactions may yield to quantum computers one day, but the transition to quantum-resistant algorithms is neither sudden nor insurmountable. For executives concerned about disruption, cost, or complexity, a structured and phased approach exists with trusted technology partners like Intel that are already beginning to deliver the infrastructure to make it possible.

A natural evolution, not a cliff edge

The “quantum threat” narrative often swings between two extremes: imminent catastrophe or distant irrelevance. The reality occupies a more pragmatic middle ground. Quantum computers are highly specialized accelerators that exploit quantum physics to solve specific hard problems. They have the potential to crack modern encryption, but they will not replace classic servers overnight, nor will they instantly break every encryption protocol on the internet. What they will do is gradually shift the security landscape, much as previous cryptographic transitions have done over the past three decades.

In late 2024, the Global Risk Institute, a Toronto-based financial services think tank, surveyed 32 quantum computing experts on when a quantum computer could break a 2048-bit RSA key within 24 hours. An average of optimistic and pessimistic estimates from the experts gave it an even 50-50 probability of reaching this code-breaking milestone by 2040. This timeline, uncertain but measurable, creates space for deliberate planning rather than emergency reaction. The near-term focus should be on “harvest now, decrypt later” scenarios, where adversaries collect encrypted data today and then hold it for future decryption later when that capability becomes possible. This is particularly applicable for information requiring confidentiality beyond 10 years.

For most enterprises, this can be a manageable risk when addressed through methodical modernization.

Government signals as confidence builders

The U.S. government has issued new directives for National Security Systems (NSS), which would likely be first on the list for potential quantum attack. Beginning January 2027, CNSSP-15 states new NSS acquisitions must be capable of supporting Commercial National Security Algorithm Suite 2.0 (CNSA 2.0) requirements for PQC algorithms standardized by the National Institute of Standards and Technology (NIST) and selected by the National Security Agency, the U.S. intelligence agency responsible for signals intelligence and information assurance. Implementation for new systems (with certain exceptions) is then required by 2031, with 100% adoption targeted by 2035.

For commercial enterprises, these timelines are not mandates, but could be signposts. They indicate where vendors, standards bodies, and auditors are headed, providing a reference architecture for responsible stewardship. Organizations can borrow this discipline without necessarily copying the exact timelines, using government guidance to calibrate their own risk tolerance and investment cadence.

Intel’s role: Infrastructure ready for the transition

Intel is at the heart of the AI revolution by delivering quantum-resistant capabilities across our product portfolio. This is not just aspirational roadmap language; it is starting to be shipping technology.

For instance, the Intel Xeon 6 Processor already incorporates quantum-safe memory encryption (AES-256) and microcode signing to protect processor integrity. Upcoming platforms will extend post-quantum algorithms to more firmware and software signing, device interconnects, attestations, and secure boot functions, aligning with the most stringent government and industry directives.

Post-quantum algorithms carry different key sizes and computational overhead than legacy methods. Intel addresses this through dedicated cryptographic accelerators, optimized libraries, and specialized CPU instructions that reduce latency and preserve service-level agreements. Technologies such as Intel QuickAssist Technology offload cryptographic workloads, enabling enterprises to adopt stronger algorithms without sacrificing performance.

PQC is not a processor-alone problem. System builders and application owners must take a comprehensive view spanning solid-state drives, network interface cards, operating systems, hypervisors, applications, and connected services. Intel is delivering its pieces of the stack, while collaborating with ecosystem partners to ensure interoperability and smooth transition paths.

A more in-depth discussion of post-quantum algorithms and attacks can be found in my recent blog posted on Intel’s Community forum: “Post-Quantum Crypto: Panic Like It’s 1999?“

A practical roadmap for enterprises

The path forward does not require upheaval, just discipline. Organizations can follow a phased approach that mirrors patterns emerging in government and critical infrastructure sectors:

• Approach PQC as modernization, not mitigation. Frame the transition as an opportunity to strengthen cryptographic foundations, reduce technical debt, and improve system maintainability.
• Leverage trusted partners. Technology suppliers like Intel are already shipping quantum-resistant capabilities with performance acceleration. Evaluate platform readiness and vendor roadmaps as part of procurement decisions.
• Start with visibility. Cryptography is embedded throughout modern technology stacks: not just in database encryption settings but in data at rest, data in transit, digital signatures, code signing, device identity, password hashing, and software update mechanisms. Start by mapping where cryptographic assets live, what algorithms protect them, and which data sets have the longest confidentiality requirements.
• Protect long-lived data first. Not all cryptographic uses age at the same rate. Encryption protecting long-lifespan intellectual property, personal data, or state secrets faces more immediate attention than short-lived session keys or rotating certificates. Focus initial investments on high-value, long-retention data stores and the trust anchors (root certificates, firmware signing keys) that underpin system integrity.
• Design for evolution and agility. Post-quantum algorithms are not simple drop-in replacements. They carry different key sizes, performance characteristics, and integration requirements that ripple through protocols, APIs, and hardware. Design systems that can transition algorithms without business disruption: testing compatibility, ensuring vendor roadmaps align, and engineering for rotation.

The bottom line

Quantum computing will reshape cryptography, but despite what occasional click-bait headlines say, it will not upend business overnight. The transition to post-quantum algorithms is a measured, multi-year journey, one that organizations can navigate with confidence by partnering with capable technology providers, prioritizing long-lived data, and designing for agility. Leaders who approach this as an engineering evolution rather than a threat response will not only be ready for whatever timeline quantum delivers; they will emerge with more robust, transparent, and maintainable cryptographic foundations across their platforms.

This content was produced by Intel. It was not written by MIT Technology Review’s editorial staff.

This is good:

Post-quantum cryptography is now one pip-install away for the entire Python ecosystem. With funding from the Sovereign Tech Agency, we implemented support for ML-KEM, the NIST-standard key-establishment primitive, and ML-DSA, the NIST-standard digital-signature primitive, in pyca/cryptography.

Remember, the reason to do this now is because there’s no emergency. And because you will make your systems crypto agile, which is always a good idea.