How Is Cloud Powering the Future of Work?

This techUK Cloud Week panel is a few years old now, but its central argument has aged well precisely because it isn't about a specific technology, it's about what cloud adoption actually requires of people rather than infrastructure. The panel brought together Richard Hotchkin (Aptum), Moira Roberts (Cloud Gateway), Steve Brown (Empiric) and techUK's Nimmi Patel, and the throughline across all four was that SaaS adoption, accelerated hard by the pandemic, had already normalised hybrid and distributed working faster than most organisations' training and skills strategies had caught up.

The panel's sharpest point is a distinction worth sitting with: cloud-enabled roles need "more agile talent that can adapt to different cloud tools," not simply more technically-trained staff. Automation frees up time that could go toward upskilling, but the panel was equally clear that it risks the opposite outcome, "skills dilution", if organisations don't deliberately redirect that freed-up time into genuine capability building rather than just absorbing it as efficiency savings.

On actual technology choices, the panel pushed back against treating public cloud migration as automatically the right answer for every sector. Hybrid connectivity models, they argued, can genuinely serve certain use cases, public sector emergency services was the specific example, better than an immediate full migration to public cloud, a nuance that's easy to lose in more generic "cloud-first" messaging. They also flagged that most cloud platforms already ship with built-in analytics tools offering real AI capability without needing to build anything custom, useful context for any organisation assuming AI adoption requires a separate, expensive build project.

The organisational argument is where this holds up best years later: shifting from CapEx to OpEx spending isn't just a finance department change, it requires a genuine culture shift in how projects get approved and measured, and "lift and shift" migrations, moving an application to the cloud without redesigning it to actually use cloud-native features, were explicitly called out as insufficient. Applications and the skills needed to run them both need real optimisation for the cloud environment, not just relocation into it.

Perhaps the most durable line from the panel is about hiring philosophy rather than technology at all: "recruit for attitude and train for skills." In a fast-moving field like cloud, where the specific tools in use will keep changing, hiring for adaptability over a checklist of current tool experience is a more sustainable long-term strategy, and the panel's point that leadership itself needs retraining alongside technical teams (not just signing off on someone else's transformation plan) is a genuinely useful corrective to how cloud strategy discussions often get framed as purely a technical team's problem.