What if apprenticeship planning started with the outcome your business needs, rather than the programme you want to deliver? Drawing on examples from Microsoft, West Midlands Police and PSE Agency, we explore how connecting learning to real roles, challenges and opportunities can turn skills development into meaningful business impact.
A programme outline can tell you what an employee will learn upon completion. But it takes a different conversation to establish what that learning will help them contribute at work.
For an apprenticeship manager, that distinction matters. Funding, staff time and managerial support are committed long before a qualification is awarded. If development bears little relation to the work, you may be left defending a programme choice that has used levy funding and colleagues’ time without delivering the improvements the business needed.
Employees can become frustrated too: they have invested in developing skills, but cannot see where to use them. Some may look elsewhere for that opportunity. If they leave, HR faces fresh recruitment and onboarding, while their manager is left a person short.
The answer is not to set aside apprenticeship requirements. It is to make the workplace context part of the plan from the beginning, for existing staff as well as new recruits. For TDM, that means measuring skills development by what people achieve at work, not simply the training hours they complete.
Microsoft’s experience with TDM offers a useful illustration. In our conversation with apprentice Aarushi and her mentor, Simon, the value of the IT Consultancy pathway within the Digital and Technology Solutions Professional Degree Apprenticeship is its connection between business needs and technology delivery.
During her first year, Aarushi supported a manufacturing customer introducing AI tools responsibly to early-career employees. Her perspective as an apprentice helped her relate to the audience, while her developing analytical and communication skills helped her explain complex ideas.
TDM’s contribution is the structure and support around that work. Aarushi describes coaching that helps her recognise the skills she is building and where she needs to improve. Simon explains how TDM’s work-based learning and evidence framework aligns with Microsoft’s own development plans.
Aarushi’s responsibilities give her somewhere to apply her learning while she is developing. The employer does not have to wait until completion to see what she can contribute. Read Aarushi and Simon’s experience.
At West Midlands Police, Apprenticeship Manager Glynis identifies that fit as a reason for choosing TDM for IT and digital apprenticeships. She describes an employer-focused, flexible approach tailored to the organisation’s job roles and performance requirements, alongside responsive support. The organisation’s apprenticeship strategy includes both existing employees and new talent. Read the employer’s account.
For employers, this is a useful expectation to set. A provider should understand the contribution you need and help connect development to it. Managers remain involved, but should not be left to translate the training into relevant work on their own.
PSE Agency provides a separate example through TDM’s eight-week AI and Automation for Work Skills Bootcamp, rather than an apprenticeship. Seven colleagues took part. The employer reports improvements to reporting, dashboards and content workflows, with hours saved each week. Four more employees were subsequently booked onto training. Read PSE’s experience.
These are employer-reported results from that programme, not a forecast of apprenticeship returns. The useful principle is to connect learning with a problem worth solving, then look at what changes in practice. As AI becomes part of everyday work, success depends on developing the people who use it alongside the technology itself.
Look for a discussion about responsibilities and performance requirements, not simply a suitable course title. The apprenticeship standard stays in place; workplace learning should reflect your organisation’s context.
Clarify how relevant opportunities, feedback and support will be agreed. Employees need room to take responsibility, try things and reflect on the result. Managers need a shared plan, rather than another problem to solve alone.
Start with the business problem the skills should help solve. Agree what improvement would matter: quicker reporting, fewer errors or someone handling more complex work. Record the starting point, then ask how the learner, manager and provider will review actual work against it. Look at what the learning helped change, alongside any new tools or other changes that may also have contributed.
Considering AI or automation development for your teams? Whether you’re reviewing an existing programme or exploring something new, we’re happy to talk through your requirements and how TDM could help. Talk to us about your team’s development needs.
we went with; wizard pi
