Hiring for a Transformation Programme: A Hiring Manager's Guide

Most transformation programmes do not fall over on technology. They fall over on people. The core replacement, the cloud migration, the payments rebuild, the case management platform. The tech is hard, but it is knowable. What actually sinks a programme is hiring the wrong people, in the wrong order, at the wrong time, and then losing them halfway through.

We have staffed a lot of these across banking, government, energy and health in New Zealand. This guide is what we tell hiring managers and programme sponsors before they go to market. It will not tell you how to run your programme. It will help you build the team behind it.

Contract or permanent: decide by phase, not by preference

The instinct on a big programme is often to hire permanently. It feels safer, it looks like commitment, and the headcount lands on someone else's cost line eventually. But a transformation programme is not a steady state. It has a shape: a ramp, a peak, and a wind-down. Hiring for the peak permanently leaves you carrying people you no longer need the day the programme closes.

The cleaner way to think about it is build versus run.

The build is temporary by definition. Delivery leads, architects, senior engineers, migration specialists, test leads. You need serious capability for eighteen months, not forever. This is where contract earns its place. You get people who have done this exact work three or four times already, they are available in weeks not months, and they leave cleanly when the work is done. You are paying for a known outcome over a known window.

The run is what you keep. The capability that operates and evolves the thing once it is live. Product owners, platform engineers, the people who will still be there in three years holding the institutional knowledge. Hire these permanently, and hire them early enough that they are in the room while the build happens, not handed a finished system they had no part in shaping.

The mistake we see most is treating every role the same. Permanent hiring for genuinely temporary work leaves you managing people out at the end. Contracting the roles you should have kept means the knowledge walks out the door the moment the programme closes and you are paying to relearn it. Sort each role into build or run first, then choose the engagement model.

One honest caveat for the New Zealand market: senior transformation contractors are a finite pool, and the good ones are usually already placed. The rate reflects that. If a day rate looks high, the alternative is usually a permanent hire who takes three months to find, three months to onboard, and does not have the pattern recognition that comes from having done it before.

Sequence the team: shape-setters before bodies

The second failure mode is hiring everyone at once. A programme gets funded, the pressure comes on to show momentum, and forty roles get thrown to market in the same week. Six months later half of them were the wrong roles because nobody senior had defined the work yet.

Hire in order of who sets the shape.

First, the people who decide how the thing gets built. The delivery lead or programme manager, and the lead architect. These two define the operating model, the delivery approach, the technical direction and, crucially, the roles underneath them. Get these wrong and everything downstream is wrong. Get them right and they will tell you exactly who to hire next.

Second, the leads who own each workstream. Engineering lead, data lead, test lead, change lead. They translate the shape into a plan and a team.

Third, the delivery layer. The engineers, analysts, testers and specialists who do the work. By now the roles are properly defined, the standards are set, and the leads can interview their own people rather than you guessing.

The temptation is always to hire bodies early to look busy. Resist it. A delivery engineer sitting idle for two months waiting for direction is expensive and demoralising, and they will leave before the work even starts. Bring people in when there is real work with their name on it.

Write a spec senior people actually respond to

Senior people read job specs differently to everyone else. They are not scanning for a checklist to match. They are trying to work out one thing: is this a real problem worth their time, or is it a mess they will get blamed for.

Most specs fail them on three counts.

They are laundry lists. Thirty bullet points of technologies and certifications with no sense of what actually matters. A senior person reads that and assumes you do not know what you need, which means the programme is not clear, which means it is a risk to their track record.

They hide the problem. Pages of company background and culture language, nothing about the actual work. Senior people want the problem stated plainly. What is broken, what are you replacing, what does good look like, what is the deadline. Give them the real thing to solve and the right ones lean in.

They bury the mandate. The single most important thing to a senior hire is authority. Who do they report to, what do they own, what can they actually change. A director-level person will walk past a role with a big title and no real mandate every time.

Write the spec as if you were briefing a peer. Lead with the problem and why it matters. State the mandate clearly. Be honest about the hard parts, senior people are drawn to hard problems and repelled by ones that pretend to be easy. Cut the buzzwords entirely. The tone of the spec tells an experienced person more about the programme than the content does.

Why counteroffers fail

You have run the process, made the offer, and your preferred candidate goes back to their current employer, who panics and throws a counteroffer at them. It works often enough that hiring managers dread it. Here is why it almost never holds, and what to do instead.

A counteroffer solves the wrong problem. People very rarely leave purely over money. They leave because of the work, the manager, the lack of progression, the sense of being stuck. A pay rise does not fix any of that. It buys a few months of the same frustration with a slightly bigger number attached.

The trust is already broken. The moment someone resigns, their employer knows they were looking. The counteroffer is a reaction to that, not a genuine reappraisal of their worth. Both sides know it. The relationship does not go back to how it was.

The numbers back it up. A large share of people who accept a counteroffer have moved on within a year anyway. The underlying reasons they wanted to leave were still there, and now their loyalty is in question on top of it.

The fix is not to fight the counteroffer at the end. It is to win at the offer stage, before it ever appears. Move quickly, an offer that lands weeks after the final interview gives the current employer time to get in first. Make sure the candidate is genuinely sold on the work and the mandate, not just the package, because that is the thing a counteroffer cannot match. And have the conversation about counteroffers up front, so when it comes, they have already thought it through. A candidate who has decided on their reasons for leaving is far harder to buy back.

The short version

Sort every role into build or run before you choose contract or permanent. Hire the shape-setters before the bodies. Write specs that state the real problem and the real mandate, and cut the buzzwords. And win your senior hires at the offer stage, because you will not win them back after a counteroffer.

Get the people right and the technology becomes a solvable problem. Get them wrong and no amount of budget will save the programme.

Find has staffed transformation programmes across New Zealand's largest banks, government agencies and enterprises for over two decades. If you are scoping a programme and working out who to hire and when, we are happy to talk it through, no obligation.