The status report has moved from amber to red. A supplier has missed a deadline, two workstreams are pulling in different directions and the next steering group is close enough to make everyone uncomfortable. Then someone says what people often say at this point. “We need a programme manager.”
It sounds decisive. It may unlock budget and give the team something practical to act on. But it is not yet a hiring brief. More importantly, it may not be the answer.
The programme might need someone who can recover delivery and challenge decisions that are no longer working. It might need a change lead who can rebuild trust with the people expected to adopt what is being introduced. It might need stronger PMO control, firmer technical direction or an interim leader with enough authority to bring several competing interests back together.
These are different problems. Searching for the same familiar title each time is how organisations end up meeting credible contractors who are wrong for the situation they are entering. Experienced contractors are rarely hired into calm, perfectly defined environments. They arrive when something important needs to move, when internal capacity is stretched or when confidence in delivery has started to weaken. The value they bring depends not only on what they have done before, but on whether that experience fits the condition of the programme now.
Before searching for a project, programme or change contractor, the most useful question is not simply, “Who do we need?” It is, “What needs to be different because this person joined?”
The job title often arrives before the diagnosis
Under pressure, job titles become shorthand. A Programme Manager will bring control. A Business Analyst will define the requirement. A Change Manager will handle adoption. Sometimes that shorthand is accurate. Sometimes it conceals the fact that the organisation has not yet agreed what is actually going wrong.
Consider a systems implementation that is technically on schedule but losing support across the business. The plan may be sound. The supplier may be delivering. The immediate risk could sit with operational teams that do not understand how their work will change and have begun resisting decisions through delay. Hiring another delivery-focused project manager may add reporting without resolving the reason progress feels fragile.
Now take a programme described as a change problem because stakeholder confidence is low. Look more closely and the cause may be weak dependency management, unclear ownership or decisions sitting unresolved between business and technology teams. In that situation, better communication alone will not repair the machinery of delivery.
The same outward symptoms can point to very different needs. Missed milestones, tense governance meetings and overloaded internal teams tell you that the programme is under pressure. They do not tell you which contractor will relieve it. The first job is to identify the stage the programme has reached and the problem that now stands between the organisation and its intended outcome.
Mobilisation needs someone who can turn intent into movement
At mobilisation, the danger is rarely a lack of ambition. It is that the programme begins carrying assumptions that have not been tested. Scope looks settled until delivery teams examine it. Governance exists on paper, but decision rights remain vague. Plans contain dates without enough confidence in the dependencies beneath them.
The right contractor at this stage brings shape without creating theatre. They can turn a strategic objective into work people understand, expose the decisions that need an owner and establish enough control for delivery to begin with confidence. Evidence of mobilisation matters more here than a long list of programmes. Ask what the contractor inherited at the beginning of a comparable assignment. What was uncertain? Which assumptions did they challenge? How did they move the work from approval into credible delivery?
Active delivery needs judgement across the gaps
Once delivery is under way, the work changes. Plans exist. Teams are moving. The risk now sits in the gaps between them. A data migration can be progressing while the wider implementation falls behind. A supplier can meet its milestones while internal decisions remain unresolved. Each workstream can report green and the programme can still be heading towards trouble because no one has joined the consequences together.
This is where experienced programme and delivery contractors earn their value. They see dependencies early, recognise when an isolated delay will become a wider problem and know when to intervene without dragging every issue into governance. #They create enough challenge to protect the outcome without becoming another layer through which decisions must travel.
When assessing this experience, do not settle for hearing that a contractor “managed multiple workstreams”. Ask about the moment when those workstreams came into conflict. What did they notice? What choice did they make? Who needed to be brought with them? What changed because they acted? Real delivery experience becomes visible in the detail.
Recovery is not normal delivery at a faster pace
Programme recovery is often treated as if the existing plan simply needs more energy behind it. That is rarely enough. By the time a programme needs recovery, people may have spent months defending earlier decisions. Reporting may no longer reflect what teams privately believe. Suppliers and internal stakeholders may have different versions of why progress has slowed. The programme does not only need a new plan. It needs someone capable of discovering what is true without creating more fear around the answer.
A strong recovery contractor can enter that environment, listen without being absorbed into its politics and decide what must stop as well as what must continue. They understand that credibility is rebuilt through decisions people can see and trust, not through a more optimistic set of milestones. This calls for a particular kind of experience. Look for someone who can explain the condition they inherited without blaming the people already there. Listen for how they established the facts, reset expectations and secured authority for the decisions that followed.
Adoption problems need more than a communications plan
Some programmes reach the final stages of technical delivery before the real difficulty becomes visible. The system works, but the organisation is not ready to work differently. At that point, adoption can be mistaken for a communications exercise. More updates are issued. Training is scheduled. Stakeholder packs become more polished. Yet the people affected may still be worried about losing control, unconvinced by the new process or unclear about how the change will alter decisions they make every day.
The right change contractor understands that resistance is information. They can distinguish between discomfort that needs support and a legitimate operational concern the programme has failed to address. They work between leadership, delivery teams and the wider business, translating the intent of the programme into changes people can understand and realistically adopt. The useful question is not whether someone has delivered a change plan. It is how they responded when people did not behave as the plan expected.
Stronger governance does not always mean more governance
When leaders lose confidence in a programme, the instinct is often to add control. More reporting is requested. More people attend meetings. More decisions are sent upwards for approval. That can create visibility, but it can also make the programme slower and less accountable. Everyone can see the problem, while nobody feels able to resolve it.
An experienced PMO or portfolio contractor should do more than improve the appearance of the reporting pack. They should help decision-makers understand which information matters, where ownership is unclear and which issues genuinely require senior attention. Good governance creates a cleaner route to action. It does not simply produce a better record of why action did not happen. If that is the pressure point, look for evidence that the contractor has improved the quality of decisions, not only the quality of reporting.
A shortlist should show why each person fits the situation
Once the condition of the programme is understood, the search becomes more precise. CVs still matter, but titles and sector familiarity should not do all the work. A credible shortlist should explain the connection between each contractor’s experience and the situation they are being asked to enter. That means understanding the scale of previous assignments, the contractor’s personal contribution and the decisions for which they were genuinely accountable. It also means confirming availability, rate expectations, working arrangements and genuine interest before the hiring team commits time to an interview.
Our IT contractor recruitment process is designed to bring that context forward. Alongside CVs and recruiter insight, video shortlists allow decision-makers to hear how contractors describe their experience in their own words.
Video should not reward the most polished speaker. Used well, it helps the hiring team identify which claims need deeper examination and which contractors can explain complex work with credibility. Our guide to evaluating a video shortlist explains how to make that comparison without confusing presentation with delivery ability.
Commercial details should be handled with the same discipline. A day rate has to make sense, but the cheapest contractor is expensive if the organisation loses another six weeks before recognising the mismatch. Rate, availability and engagement structure matter because they shape whether the appointment can work. They should support the decision, not replace it. Employers comparing the market can use our IT contractor day-rate guide as a starting point.
Hire for what must happen next
The strongest contractor is not always the person with the biggest programme, the most familiar title or the closest sector match. It is the person whose experience makes sense for the situation the organisation is facing.
For an IT director, that is the decision beneath the hiring decision. Does the programme need to mobilise, regain control, recover confidence, improve adoption or create stronger visibility across delivery? What will the contractor need to influence, and what authority will they have to do it?
Answer those questions well and the market becomes easier to navigate. The search moves away from collecting plausible CVs and towards finding evidence that somebody has faced comparable pressure and changed the outcome. When an important programme comes under pressure, the aim is not simply to add another person. It is to appoint someone who can alter what happens next.
Tell us where the programme stands and discuss the contractor experience you need.