The uk's convergence ambition is real – is something inadvertently working against it

The UK's convergence ambition is real – is something inadvertently working against it?

The UK is globally recognised for world-class research across AI, quantum, photonics and robotics. Government backing is strong — the UK's Modern Industrial Strategy singles out AI and quantum with dedicated measures, and existing bodies like the Innovation and Knowledge Centres already support the photonics industry.

But the real question cuts deeper. Each of these technologies receives its own set of interventions. The frontier of value, however, lies at the intersections — quantum powering more advanced AI, or AI accelerating breakthroughs in quantum computing.

We're well placed. But is convergent capability growing fast enough to hold that position?

DDaT is largely focused on a world of discrete disciplines

Consider what this means at the executive level of UK public sector technology delivery. How do we grow people in exactly the fields that keep the UK ahead? The DDaT framework has done a tremendous job codifying the role types and mixes that accelerate delivery of high-calibre, modern digital services. Since 2010, the Civil Service, in conjunction with industry, has significantly raised the bar in digital delivery.

But the job families — software engineer, product manager — reflect the digital landscape of the late 2010s. They are imperfect at best in a post-2026 world. Frontier roles simply don't fit the taxonomy. A quantum-ML specialist blends theoretical physics, computer science and maths — and spans design, modelling and implementation in the same breath. The temptation is to shoehorn it into "software engineer" and bolt on a technology Pay Supplement.

That temptation must be resisted. Frameworks don't just describe roles and set pay bands — they shape what people aspire to become, and how transformative work gets structured. The taxonomy becomes the ceiling.

Playing this out in practice

We see this regularly. We are engaged on "an AI programme here" and "a cloud modernisation programme there" — sometimes within the same directorate — when the real opportunity sits precisely at their intersection.

In recruitment, hiring managers already know when they need hybrid, cutting-edge roles that don't map cleanly onto DDaT families. The result: salary justifications, grades and job titles become a battle, and the convergent talent they need either goes unhired or gets boxed into an ill-fitting role — and eventually walks.

For people already in post, the path of least resistance over a multi-decade career is to go deeper in a single discipline. That shapes personal investment and structurally constrains away from convergence. Leading-edge tech firms deliberately rotate talent across domains, roles and technologies — a discipline the public sector has rarely attempted.

Commissioning and procurement compound the problem. Both are directly informed by DDaT, so programmes are inevitably built around siloed job families, reinforcing the very divisions that cross-domain thinking needs to dissolve.

What convergence-ready organisations look like

The diagnosis points to a clear aspiration. In a convergence-ready organisation, people and teams self-organise around value streams, optimising for flow. Structures and roles become fluid — hierarchy as discipline gives way to outcome as discipline. Growth means acquiring complementary skills: both discipline-based and technology-based.

Companies at the frontier are rarely stymied by job titles. Teams are fluid in how they align work to outcomes. The principle worth copying is this: organise around the work to be done and the outcome to be achieved — not the job taxonomy. There are examples of this in government, and cross-functional teams are a genuine tenet of modern digital service delivery. But they may not yet be cross-functional, or fluid, enough.

A complementary convergence layer for DDaT?

There's nothing wrong with DDaT. It is a significant success and will remain so. But there is a clear case for adding a "convergence layer" alongside it — a set of flexible, redefinable cross-domain pathways that enable portfolio career progression and formally recognise the value of hybrid expertise: for individuals, teams and whole organisations.

Two concrete asks follow from this:

First, CDDO and DSIT should convene a working group with industry — not just frontier tech firms, but the wider ecosystem already delivering capabilities, services and products into government — to design this layer properly.

Second, Programme Leaders, CDOs and procurement teams should stop letting the current taxonomy dictate programme structure. Think from value streams first. Consider how convergence could shape the overall programme design, then map back to DDaT where needed, not the other way around. Engage with the market, even if there is no active procurement in scope, to seek industry views on the right skills mix and how they might fit within DDaT.

You can't seize what your talent architecture isn't designed to hold

Seizing the opportunities at the intersections of frontier technologies requires more than ambition — it requires the talent architecture to support it. Frameworks that govern talent, careers and programme design must be built for a convergent world, not inherited from a siloed one.

This is a low-cost, high-leverage intervention — particularly in a knowledge-worker industry where talent architecture is the product.

This article first appeared on techUk.