Adoption Lead

Sheffield, United Kingdom | Posted on 11/06/2026

GCB4/ 5 typical — Various —co-located with the FDTTech

She sit within the FDT Tech team and close to users (business teams, delivery pods, transformation squads) as the accountable Change/Adoption Lead for rapidrollout and sustained adoption of AI-enabled solutions (including GenAI wherein scope). Build and execute a change and adoption plan aligned to release increments—turning real user needs into embedded ways of working quickly,safely and repeatably. This role bridges product intent, delivery execution and operational ownership, accelerating time-to-value while ensuring solutions are trusted, responsibly used, and aligned to enterprise controls and guidance.

Reporting & stakeholders:
Solid line into FDT Tech Lead / Delivery Lead. Strong day-to-day partnership with Product Owner(s), businessSMEs and delivery pod leads on scope, prioritisation and trade-offs. Close collaboration with operations, frontline teams, risk/compliance, change,training, comms, and support teams to ensure readiness and sustainable adoption. Engage with regional teams to identify champions/super-users andensure materials land effectively across geographies.

Scope &authority:
Accountable for shaping and owning thechange strategy, adoption approach and business readiness for AI-enabled prototypes and production-viable thin-slice releases close to users. Owns local change decisions required to deliver outcomes at pace, within approved governance, controls and communications standards. Authority includes defining adoption KPIs, setting readiness gates (training/comms/SOP updates),coordinating champions networks, and escalating material adoption risks,policy/control gaps or operational readiness blockers

This role exists because AI-enabled delivery changes behaviour, trust and accountability, not just screens and processes. Users need plain-language guidance on what AI can/can’t do, how toverify outputs, and how responsibility remains with people. The Change/Adoption Lead keeps releases moving while ensuring adoption is measurable,benefits are realised, and responsible use is embedded into day-to-day operations.

• Change strategy and stakeholder alignment - Build a change and adoption plan aligned to the release roadmap (who changes, what changes, when,and why). Map stakeholders and impacted user groups; identify change champions/super-users across regions/teams. Shape the narrative: “what’s in itfor me”, expected impacts on workload, risk, customer outcomes, and controls.
• User journey, operating model, and process change - Define the future-state process including hand-offs, decision rights, and escalation paths (especially important when AI introduces “human-in-the-loop” steps). Update SOPs/knowledgearticles/playbooks and ensure operational ownership is clear. Ensure role impacts are managed (new tasks, removed tasks, new skills, capacity shifts).
• Training, comms, and enablement - Create role-based training(frontline, operations, risk, support, managers) with practical scenarios.
  
  Deliver communications: launch packs, FAQs, demo sessions, “what changed”notes, and release highlights. Build self-serve assets: short guides, videos,in-tool tips, prompt guides, and troubleshooting steps.
• Adoption measurement and benefits realisation - Define adoption KPIs(active users, frequency, task completion rates, time saved, error reduction,case deflection, customer outcomes). Track benefits vs baseline and work with Product/Delivery to adjust backlog based on feedback and data. Run pulse checksand qualitative feedback loops (surveys, floor-walks, listening sessions).
• Trust, transparency, and responsible use -Drive user trust by explaining AI limitations, confidence cues, and when to override…