IFOW logo

Supported by the Innovate UK BridgeAI programme, this case study took place as part of an action research project carried out by CIPD’s research partner, the Institute for the Future of Work (IFOW).  The project sought to foster a shared understanding on how to use AI effectively and responsibly.  This case study describes how a bank explored the impact of an AI coding assistant on software developer’s daily work and lived experience. The findings show how a people-centred approach to AI creates holistic management strategies to support employees through change.

Profile  

This case study focused on a UK bank with digital and high-street services, referred to here as FinanceCo. With  a workforce of over 26,000 supported by a team of 370 people professionals, the organisation maintained high employee engagement, consistently ranking in the upper decile.  

In terms of AI maturity, FinanceCo was ahead of the curve in the sector. The bank had established a formal framework for responsible AI guided by a dedicated AI strategy, an AI council and a centre of expertise. This approach was built on the responsible AI principles of accountability, contestability and redress, fairness, empowerment, and societal and environmental wellbeing. 

While FinanceCo managed a diverse portfolio of AI projects, this case study examined the rollout of an AI coding assistant for their software developers. To support the action research process, FinanceCo formed a senior cross-functional working group. This working brought together AI delivery experts and specialists from across the people team including AI and people, skills, strategic workforce planning, and colleague enablement. 

Operational context 

FinanceCo’s approach to technology – including AI – was inherently cautious. Every AI use case was tracked end-to-end, ensuring all deployments aligned strictly with the bank’s risk appetite and governance frameworks.  

Recognising that AI was more than just a technical deployment, FinanceCo invested in a dedicated people and communications workstream to guide its workforce through the transition. This initiative focused on supporting the workforce through change via tailored skill development and transparent insight sharing across the bank.  

FinanceCo’s senior people professionals emphasised that AI tools should be used as ‘thinking partners’. Employees were encouraged to engage with these tools critically to improve processes rather than follow without question. 

For software developers, the introduction of an AI coding assistant marked a ‘fundamental shift’ in job design. By using the AI coding assistant to generate boilerplate code, software developers can pivot their focus toward high-level system architecture and creative problem solving. Leaders viewed this shift as an opportunity for ‘people's creativity to shine’.  

Challenge 

A key challenge for FinanceCo was to bridge the gap between technical potential and lived experience to understand exactly how the AI coding assistant was reshaping software developer roles. The working group’s goal was to use these insights as a blueprint for future AI projects, specifically to inform their approach to learning pathways and strategic workforce planning. 

The working group identified the following areas to uncover through the research: 

  • Real-world use. Understanding how software developers used and experienced the AI coding assistant in practice, and how these capabilities reshaped existing workflows. 
  • Meaningful engagement. Understanding how to openly involve software developers as AI use increases. 
  • Leadership communication. Equipping  leaders and managers with the insight they needed to communicate clearly as they integrated AI into existing workflows. 
  • Future-proofing. Evaluating the opportunities and risks that AI presented to the bank’s current and future capabilities. 
  • Learning design. Defining the criteria for effective learning pathways. 

As one working group member noted: ‘There's constant adaptation. You're not just using a software tool that has some limits … the software is improving all the time … your ability … to get the most from it is improving all the time as well.’ 

For the people team, the ultimate obstacle was reliance on anecdote. While the benefits of AI were discussed by a few, the team lacked the representative insights required to build a people strategy rooted in reality. 

What they did 

To capture lived experience in the transition, the working group co-designed an in-person workshop session with IFOW. The workshop was facilitated by external researchers to ensure a neutral environment where participants felt comfortable sharing their experiences. This allowed seven software developers of varying seniorities to discuss how their roles were shifting, joined for part of the session by a senior people professional. 

For their workshop approach, IFOW guided participants through the first three stages of the 6Rs framework: ‘Reveal’, ‘Reflect’ and ‘Reimagine’.  

An initial icebreaker activity surfaced what software developers considered a responsible approach to AI. Beyond the foundational requirements of AI governance – including data privacy and human oversight – participants emphasised the need for  informed consultation, strong employment protections and comprehensive training opportunities. 

Software developers then benchmarked their progress on a learning journey from ‘awareness’ to ‘confidence’. Senior software developers noted that their use of the AI coding assistant was limited, as they preferred to use other tools. They also highlighted that the linear learning journey failed to capture the varying intensity of AI use – a key insight for tailoring future learning pathways for high-skilled roles.  

Transparency played a vital role in the process. After a senior lead shared FinanceCo’s roadmap for the AI coding assistant, the group engaged in open discussion. This prompted critical questions regarding performance measurement, efficiency traps and the necessary evolution of learning and development.  
 
To transition from reflection to solutions, breakout groups unpicked how specific job characteristics were being impacted by the AI coding assistant (see Appendix 1). In the final segment, participants focused on how work could be designed to maximise positive, people-centred outcomes. By mind mapping a range of practical solutions and concrete interventions, participants co-developed solutions centred on five key themes (see Appendix 2). 

When looking at insights from this workshop, the discussions illuminated several critical areas of concern and opportunity:  

  • Performance metrics. Software developers questioned whether new metrics that focused on quantity (eg lines of code) rather than quality would be introduced. Such an approach would fail to capture the value of senior developer roles, which involve less coding and more time dedicated to fixing code and mentoring. 
  • ‘Efficiency traps’. Despite the promise of efficiency and high investment in the AI coding assistant, the technology provider did not provide a framework for measuring genuine productivity gains.  
  • Holistic learning. Participants emphasised that learning and development must include coaching and mentoring. This was especially relevant for entry-level roles. Without the know-how to challenge AI-generated outputs, they risk  over-relying on the AI coding assistant.  
  • Shifting skillsets. Participants underlined that as tasks evolve, understanding the code infrastructure and design was becoming more essential than act of writing the code itself. 

The conversations expanded beyond the AI coding assistant to consider the individual, team and organisational factors that shape a positive experience of work. The value of this people-centred approach was further captured by one working group member, who remarked: ‘This is probably the best conversation on AI I’ve had in a long time.’ 

Outcomes 

Led by the people team, the working group established two critical workstreams to drive a people-centred approach to integrating AI at work: fostering social learning and bolstering management capabilities. Both areas aligned with existing expertise and delivery capacity of FinanceCo’s people team.  

Looking at fostering social learning, insights from the workshop revealed that software developers, particularly those in junior roles, required a holistic approach to learning that moved beyond standard third-party training materials. Key suggestions included: 

  • Peer-to-peer coaching. Increasing dedicated face-to-face coaching between experienced and junior developers to build deeper contextual awareness and critical thinking regarding system architecture. 
  • Communities of practice. Establishing supportive team spaces such as formal communities to support a co-learning culture. This provide teams with the autonomy to pinpoint value-add tasks and define learning pathways needed to achieve them. 
  • AI champions network. Embedding a network of AI champions within software developer teams to drive engagement, support collective decision-making and align AI usage with long-term career pathways. 

When looking at bolstering management capabilities, the working group identified a need for greater support for managers to ensure consistent practices and drive a cultural shift for high-involvement management practices. Key areas highlighted by software developers included: 

  • Strengthening management coaching. Reviewing existing programmes – with a focus on teams with lower manager capability scores – to build essential coaching skills. This would enable managers to better support the shift in software developer roles from individual coding to a more collaborative focus on peer-to-peer code review and quality. 
  • Developing team-based collaboration. Equipping managers to foster their teams’ communication and problem-solving abilities. This would ensure that as the technical burden of coding shifts to AI, software developers are supported in building the foundational collaboration skills necessary for effective peer review.  

Learning points 

  • Leverage existing people team expertise. People teams often already have the strategic skills and experience to provide immediate value-add and improve return on investment on AI projects.  
  • Analyse impacts through job design. Applying a job design lens helps identify how AI changes specific roles. This approach provides a tangible way to see exactly how the technology impacts daily work at both the individual and team level. 
  • Go beyond standard training. The deployment of AI at work should be underpinned by a holistic strategy. This must go beyond third-party training to include the strengthening of management capabilities, which enables a culture of peer-to-peer support and social learning. 
  • Redefine productivity through engagement. Measuring shifts in productivity is rarely straightforward. Engaging directly with the workforce is a powerful way to uncover changes in actual value-add activities and avoid reliance on superficial metrics. 
  • Recognise the non-linear nature of AI uptake.The intensity of AI use varies significantly across different roles and experience levels. Success depends on moving away from one-size-fits-all learning path toward tailored approaches that reflect the way the tool is used daily. 

Appendices

  • All case studies