02.11.26

How to Hire a Change Manager for a Data and AI Transformation Programme

Technical transformation programmes don't stall because the architecture is wrong. They stall because the people who are supposed to use the new system never fully adopt it. If you're a Programme Director or Head of Transformation hiring for a data or AI change initiative, the Change Manager you bring in matters as much as the platform engineers building the thing. Get this hire wrong and you'll have a technically perfect data marketplace, lakehouse, or AI tool that nobody in the business actually trusts enough to use.

This guide walks through how to screen and hire a Change Manager for a data/AI transformation programme, based on a real contract brief we ran for an AI SaaS company deploying a new data and insight programme. It covers what to ask about methodology, stakeholder engagement, and the practical realities of running change alongside a live technical build.

What You Need Before You Start Screening

• A clear picture of the technical programme itself — what's being deployed, and what "adoption" will actually look like for end users

• An understanding of whether the role sits inside or outside IR35, and what day rate band is realistic for the market

• A view on remote vs. hybrid working, including whether in-person kick-offs or occasional site visits matter to your stakeholders

• Visibility of the project plan and milestones the Change Manager will need to align their change plan against

Step 1: Define the Change Mandate, Not Just the Job Title

Before you write a job spec, be precise about what "driving adoption" means on your programme. In a real brief for an AI SaaS client, the requirement was a Change Manager to own the full change lifecycle for a data and insight transformation programme — driving adoption of a trusted data and insight marketplace, owning the change plan, stakeholder engagement, communications, and training, and working closely with the programme team to keep adoption on track with delivery milestones.

Notice what's bundled into that one sentence: this isn't a comms role, and it isn't a training role. It's end-to-end ownership of how the organisation absorbs the change, synchronised to the same milestones the technical delivery team is working against. Write your spec with that same level of specificity — vague language about "supporting change" will attract candidates who've only ever done one slice of the job.

Step 2: Screen for Prosci Certification — and Ask What It Actually Means to Them

Prosci certification is the qualification to look for when assessing a Change Manager's methodology credentials. In the brief above, Prosci certification was explicitly the certification the end client wanted. When we screened candidates, confirming Prosci certification was a gating question, alongside other frameworks like SAFe and Agile.

But don't stop at "do you have it." A candidate who's "fully immersed" themselves in a structured change methodology should be able to describe how they operationalise it, not just name it. Ask them to walk through a real example. On this brief, one candidate described a two-tier approach: a high-level change plan that sits on top of the project plan and tracks its milestones, with a "deep dive" underneath covering the specifics of how they'd get the organisation to each stage — communications, training, training needs analysis, stakeholder engagement and stakeholder management, go/no-go decision criteria, and a return-on-investment and process-improvement review once the change has landed. That level of structural detail is what separates someone who holds the certificate from someone who's actually run the methodology end-to-end.

Step 3: Probe Stakeholder Engagement With Specific Scenarios

Technical fluency gets a transformation built. Stakeholder engagement gets it used. When screening, push candidates past generic claims of "strong stakeholder engagement" and ask them to describe their actual process.

A strong answer looks like this: identify everyone impacted by the change, set up meetings with them, run a full impact assessment to surface their worries and perceived risks, then feed that back to the project team so any issues that could affect rollout are known and mitigated through a formal risk and issue plan. The goal, as one candidate put it, is making sure people understand "what's the benefit for me" and that the transition goes as smoothly as possible. If a candidate can't articulate how they translate stakeholder anxiety into a concrete mitigation plan, that's a gap worth flagging before you put them forward.

This is also where risk assessment experience becomes relevant — the end client on our AI SaaS brief specifically wanted someone who could speak to risk management, risk assessment, delivery milestones, and adoption metrics, not just change communications. A candidate who only talks about comms plans and training decks hasn't covered the full brief.

Step 4: Check for Experience Running Parallel Technical and Organisational Workstreams

A data or AI transformation programme moves on two tracks at once: the engineering build and the organisational adoption curve. Your Change Manager needs demonstrated experience keeping both in sync, not managing change as an afterthought once the technical team has finished.

Look for candidates with a track record across data migrations and data transformation specifically. One candidate we screened for this type of role had led data migrations and change work for a telecoms business, including migrations and changes across a large European data centre, as well as change management work within banking and financial services involving data schematics and full data transformations. That breadth across sectors matters less than the consistent pattern: change managed in lockstep with a live technical migration, not bolted on afterward.

Ask directly how they've kept a change plan synchronised with a project plan when the technical scope shifted mid-programme. If they can only describe change management in isolation from the engineering roadmap, they're not ready for a programme where the data platform and the adoption plan are moving simultaneously.

Step 5: Confirm Logistics Won't Become a Blocker

Even the best-qualified Change Manager is no use to you if the contract terms don't work. Be upfront early about:

• Day rate and IR35 status. On the AI SaaS brief referenced throughout this guide, the role was offered at £500 a day, outside IR35.

• Contract length and extension likelihood. The same role was structured to start in August and run to the end of December, against roughly a year's worth of underlying work — meaning candidates should understand upfront that an extension is likely, not guaranteed.

• Remote vs. hybrid expectations. The role was advertised as fully remote, with the client based in London, but candidates who value occasional face-to-face contact for kick-offs often ask whether in-office time is possible — build that flexibility into the offer rather than treating it as fixed. Being explicit that occasional office visits (two, three, four times a month) are optional, not mandatory, helps you land strong remote-based candidates without losing those who want the in-person touchpoint.

Getting these details wrong late in the process is one of the most common ways a well-screened candidate falls through at offer stage.

Step 6: Verify CV Currency and Recent Role Detail Before Submission

Before putting a shortlisted candidate forward, make sure their CV reflects their most recent engagement in full, including end dates. In the case referenced here, the recruiter needed to go back to the candidate mid-conversation to request an updated CV because the end date of their most recent role, with a housebuilder, wasn't captured. A gap like this slows down the right-to-represent and submission process and can cost you time against a live start date.

Tips & Best Practices

Having run this kind of brief, a few patterns consistently separate a strong submission from a weak one.

• Treat Prosci as a floor, not a differentiator. Plenty of candidates will hold the certification; what matters is whether they can describe how they apply it against real project milestones.

• Ask for the "deep dive," not just the headline plan. A candidate who can describe the layer beneath the high-level change plan — training needs analysis, go/no-go criteria, post-launch ROI review — is demonstrating the methodology has actually been lived through, not memorised.

• Don't treat remote-first as inflexible. Candidates with strong stakeholder instincts often want occasional in-person contact specifically so stakeholders have "a face to the name" they can approach with problems — accommodate this where you can, it tends to correlate with the stakeholder engagement discipline you're hiring for.

• Confirm sector-relevant data transformation experience, not just generic change management. Change management in a data and insight marketplace programme draws on different muscles than change management for a straightforward software rollout — migrations, schematics, and large-scale data environments are the relevant proof points.

Troubleshooting Common Hiring Snags

The candidate's CV doesn't show a recent end date. Don't let this stall the process — request the updated version immediately and confirm verbally when the most recent contract ended before you proceed to right-to-represent paperwork.

The candidate wants hybrid, the role is advertised remote. This is rarely a hard conflict. Clarify whether your client is open to occasional office attendance; many consultancies run these roles as remote with optional in-person time built in, which satisfies candidates who want visibility with stakeholders without requiring a full return to site.

The candidate has strong change credentials but no data/AI transformation experience. Push for specifics on the type of change they've led — telecoms data centre migrations, banking data schematics, or similar large-scale data environments are reasonable proxies even without direct AI programme experience.

Key Takeaways

Hiring a Change Manager for a data or AI transformation programme is not the same exercise as hiring a generic change professional. You need someone who holds a recognised methodology certification like Prosci, who can describe stakeholder engagement as a structured process rather than a soft skill, and who has proven they can run a change plan in lockstep with a technical delivery milestone plan rather than behind it. Screen for the detail beneath the certification, confirm contract logistics early, and keep CVs current before submission — these are the practical steps that turn a plausible-looking candidate into a hire who actually gets your programme adopted.