Roles for a
modern cloud journey.

Designed 4 Cloud’s original discussion of cloud journey roles makes a useful distinction: business stakeholders and delivery leadership remain essential, while architecture, security, and engineering capabilities adapt to cloud. The roles below are a modern interpretation of that idea, not a staffing prescription.

Keep business ownership close

Executive sponsors clarify why the organisation is changing, make trade-offs, and unblock decisions. Product and service owners connect those goals to user needs, service priorities, operational readiness, and measurable outcomes.

Programme and delivery leads coordinate dependencies and incremental delivery. They should work with product teams rather than treating a cloud migration as a plan that ends at cutover.

Shape the architecture and platform

Enterprise and domain architects connect business strategy to principles, target-state choices, and cross-system constraints. Platform architects and engineers build the shared cloud foundations and paved paths that application teams can use safely.

Solution architects work with product teams on workload-specific choices. These roles overlap in smaller organisations; make the responsibilities explicit even when one person covers more than one area.

Make controls part of delivery

Security, identity, and risk specialists define guardrails and help teams continuously validate access, configuration, threat exposure, and compliance. Embed this work in delivery instead of handing it over at the end.

Data architects and stewards address data quality, classification, lineage, access, retention, and sovereignty. FinOps practitioners connect product, finance, and engineering teams to cost allocation, forecasting, and value measurement.

Operate and improve the service

Software, reliability, and operations engineers own deployment, observability, incident response, backup, recovery, and service improvement. In a platform-engineering model, a central team enables consistency, while workload teams retain responsibility for the services they build and run.

AI-enabled services also need named owners for model selection, evaluation, data and prompt changes, human escalation, monitoring, and retirement. Governance is a shared capability across product, technology, security, privacy, and the affected business domain.

A practical way to size the team

1. List the outcomes, workloads, risks, and operational responsibilities in scope.
2. Map each decision and ongoing responsibility to an accountable person or team.
3. Identify gaps in skills or authority, then train, recruit, or bring in a partner deliberately.
4. Review the model after each delivery increment; combine or separate roles as scale and complexity change.

Source: Adapted and updated in original wording from Designed 4 Cloud Limited, “Roles for Cloud Journey” (22 July 2022). This article summarises and extends the source; it does not reproduce it.