This role reports to the Head of Enterprise Architecture UK.

In This Role You Will

Own the target state for both domains, convert it into a funded and sequenced multi-year roadmap, assure delivery against it, and raise the standard of architecture practice across the community that builds it.

Domain architecture and target state

• Define and maintain the target architecture across Digital Workplace, Network and Hosting, Cloud and Hybrid, and Platform Engineering, including capability-level views, principles, standards and reference patterns.
• Maintain an accurate baseline of the current estate, working with domain and service owners so landscape models reflect reality.
• Align to Cybersecurity and Monitoring and Observability capability models owned elsewhere in the function, ensuring designs integrate with and are assured against them.
• Contribute domain content to cross-cutting standards and represent the domains at architecture governance forums.
• 
  

Demand, risk and emerging technology

• Bring together the signals that shape the plan: risk and obsolescence, programme and bid demand, growth and acquisition activity, supplier and market direction, and the security threat picture.
• Translate those signals into a concise, defensible set of domain drivers that underpin the roadmap and investment plan.
• Assess emerging technology on evidence rather than hype, using proportionate proof-of-value activity and clear adopt, trial, watch or avoid recommendations.
• Maintain awareness of relevant vendor, open-source and industry direction, incorporating it into domain standards and roadmaps where it earns its place.
• 
  

Roadmaps and long-term planning

• Own and maintain a rolling three-year domain roadmap with a five-year technology outlook, refreshed on a predictable cycle.
• Sequence change around the constraints that genuinely matter: hardware and operating system lifecycle, licence and contract renewals, datacentre and cloud commitments, and the rate of change the business can absorb.
• Model options and trade-offs — buy or build, cloud or on-premises, refresh or replace — making cost, risk and capability impact explicit.
• Plan headroom for growth so capacity, licensing and footprint decisions do not become tomorrow’s constraint.
• Maintain a single published view of obsolescence and technical debt, with the cost of inaction quanti
•