Skip to main content

https://digitaltrade.blog.gov.uk/2025/04/22/dbts-machinery-of-government-an-insight-into-the-teams-behind-the-single-it-platform-migration-project-part-2/

DBT's Machinery of Government: an insight into the teams behind the Single IT Platform migration project (part 2)

A duck and her ducklings having a swim

Welcome to part 2 of our Machinery of Government (MoG) blog. This series explores one of the biggest digital MoG migration programmes in government.  We migrated almost 2,000 colleagues onto the Department for Business and Trade’s (DBT) Single IT Platform.

Read the MoG blog part 1 which discusses some of the technical workstreams on this migration programme. In part 2 we hear from a different workstream; the Change, Communication and Engagement (CCE) team. CCE played a crucial role in ensuring the success of the programme, helping colleagues navigate their digital migration into DBT and adapt to the changes brought with it.   

While 2 blog posts cannot do the hard work of this migration programme full justice, we are trying to capture some of the incredible work that has gone into it. Hopefully this can help others working on future MoGs or large change programmes, and showcases the breadth of work that colleagues across Digital, Data and Technology (DDaT) do.

Change Communication and Engagement

Miriam Wheeler

Miriam Wheeler

Imogen Barker

A woman wearing a black jacket on a beach.

Charlotte Saxby

Charlotte Saxby

The Change, Communication and Engagement workstream was made up of colleagues from the DBT Project, Delivery and Change, and DDaT directorates. We have expertise in working on change projects, colleague engagement, communications, User Research and Content Design.

The CCE workstream has been vital in bridging the gap between the programme team and colleagues undergoing their migration onto the DBT Single IT Platform. We engaged with colleagues to ensure they were fully supported throughout their migration journey. We used:

  • email communications
  • departmental bulletins
  • the MoG Champions network
  • our internal SharePoint site called the Migration Hub
  • drop-in sessions to cascade information and updates to colleagues

CCE worked closely with all the programme workstreams including DBT’s internal communications team, as we were responsible for cascading key messages to colleagues on their behalf.

We worked most closely with the Device Rollout and Personal Data Migration (PDM) workstreams discussed in part 1 of this blog. We were in direct contact with colleagues booking to attend sessions to receive their replacement DBT devices. It was fundamental for us to stay connected with these workstreams to ensure they knew when colleagues were scheduled for their migrations. The Device Rollout and PDM workstreams could then ensure the correct personal data migrations were completed and the engineers running the sessions were notified.

As this was a change programme, we learnt to tailor our communications to suit individuals and help them feel more confident adapting to new ways of working. Many colleagues required help with accessibility or were worried about what the changes would bring, so we needed to consider the impact this would have.

We adjusted our messaging to be more informal and used direct messages with colleagues when required. We worked with the engineers to arrange one-on-one sessions with colleagues where needed to help those who were particularly anxious or less ‘tech-savvy’. We also worked with colleagues who used assistive technology or equipment to understand what they required to make sure we were prepared ahead of their sessions. This helped alleviate anxieties and made sure they could continue working effectively through their migration.

We also ran and facilitated drop-in information sessions in collaboration with other workstreams. This was a chance for colleagues to have their questions answered and make sure they knew what to expect.

Colleagues migrated with their directorates in cohort groups. Each cohort was assisted through the MoG by a diverse network of Champions; representatives from each cohort who provided a pivotal link between the programme team and colleagues.

The CCE workstream led engagements with the Champions, who were able to assist colleagues with queries and provide support along with a familiar face. They also helped gather feedback and encourage colleagues to take part in User Research to help us continuously improve their experience.

Adapting our approach from User Research

It was challenging for us to establish clear processes at the start of the MoG. As the programme evolved, we learned and continually improved the experience for each cohort.  

Throughout the programme, we conducted User Research (UR) sessions and issued surveys to gather feedback on how to iteratively improve our communications and colleagues’ understanding of the MoG.

At the beginning, we were sending guidance which was unclear for colleagues and used time-consuming methods. These were often static such as PowerPoints or manually sent emails. From UR feedback, the programme’s content designer created a Migration Hub. This was a fantastic SharePoint site where colleagues could find all the information and guidance they needed at every stage of their migration journey. This could also be continuously updated and meant guidance was kept current.

Webpage with information about the migration process

This resource was hugely improved by carrying out UR with colleagues undergoing their migration. We learnt that they were busy and required simple language which was easy to understand and not too technical. They preferred guidance to be presented in a variety of digestible formats such as pictures or videos. They also wanted to easily find out who to contact for help. These changes proved to be hugely useful for colleagues also using assistive technology. Having to download PowerPoint documents makes it difficult to navigate back to guidance pages and unnecessary images are hard for screen readers to understand.

Key learnings

We have a lot of learnings from working on this programme. The 5 top things the CCE team have learnt are needed to deliver a successful migration programme include,

  • collaboration: Effective collaboration with other teams involved in the programme. Understanding what other teams were working on allowed us to effectively communicate with colleagues and vice versa
  • flexibility: Being able to adapt communication and support methods based on user feedback and changing needs. Although we had standard communication plans, we had to be open to altering these for different cohorts
  • user-centered approach: We tailored our approach to individual needs, such as assisting users with specific concerns. Providing personalised support really helped to alleviate any fear of change and allowed for a more ‘human’ experience for many colleagues. 

Colleague quote: “The team are truly amazing and everyone they speak to and help comes out of the room praising them. Thank you all so much. They deserve all the praise.These projects are not easy to manage, but this had felt very professionally and humanly led”

  • early engagement: Engagement with colleagues and stakeholders early in the process helped to address concerns and prepare colleagues for their migration in good time
  • clear communication: Making sure all communications were consistent, clear and  jargon-free helped colleagues understand the process more easily and reduced confusion

Although this only captures a small amount of the migration programme work, we hope this provides useful insight into the type of work DDaT can do. This is also not the end. The team are creating a MoG playbook for DBT, capturing everything that has gone into this programme and our learnings, to help future programmes like this one.

Ready to join us?

Digital, Data, and Technology are always looking for a wide range of skills. Explore current opportunities and discover how you can make a difference.

Sharing and comments

Share this page

Leave a comment

We only ask for your email address so we know you're a real person

By submitting a comment you understand it may be published on this public website. Please read our privacy notice to see how the GOV.UK blogging platform handles your information.