EXECUTIVE LEADERSHIP · INTERIM TRANSFORMATION & PROGRAMME DIRECTOR
An Interim Transformation and Programme Director with authority to decide, not just report.
CE Interim appoints proven Interim Transformation and Programme Directors to take ownership when a programme has been designed, funded and launched, and the business has quietly gone back to working the way it did before.
Confidential from first contact. A vetted, mandate-matched executive ready to start within 72 hours of the completed mandate brief.
The reporting line
BOARD · SPONSOR · STEERING COMMITTEE
INTERIM TRANSFORMATION DIRECTOR
OPERATIONS · FINANCE · COMMERCIAL · SYSTEMS · PEOPLE
1,500+
Mandates delivered per year across the alliance
90+
Operating partners around the world
30+
Countries covered
95%
Cross-border mandates
72 hours
From brief to mission start
Definition
What is an Interim Transformation and Programme Director?
An Interim Transformation and Programme Director is an experienced executive appointed for a defined period to own the delivery of a change programme across functions: the sequencing, the dependencies, the adoption and the benefits. The mandate is execution authority, not programme reporting.
The same seat is called Transformation Director, Programme Director or Chief Transformation Officer. CE Interim writes it out rather than abbreviating, because CTO is widely used to mean Chief Technology Officer and the acronym therefore creates ambiguity about the mandate.
A system can go live while the business continues using old processes. The cause may be unclear ownership, training gaps, insufficient capacity or technical defects. The mandate is to establish what prevents adoption and lead a coordinated response with business owners and the CIO, rather than assume launch equals transformation.
Appointment triggers
When businesses appoint an Interim Transformation Director
01
The programme went live and the business went back to normal
Adoption has stalled after go-live. Teams have reverted to the old process, alerts are ignored, and the reported benefits exist in the business case rather than in the results.
02
An ERP or platform rollout has stalled or failed
The rollout is behind, over budget or paused. Where business readiness and cross-functional decisions are the gap, the mandate resets programme delivery. The CIO leads technical recovery where required, with responsibilities for vendors and acceptance agreed rather than duplicated.
03
Several workstreams are running and nobody owns the whole
Each stream reports progress and the programme does not move, because the decisions that matter sit between streams rather than inside them.
04
The programme office reports but does not decide
Governance has become a reporting exercise. Escalations are logged, noted and returned to the same functions that disagreed, and the interval between them is where the delay accumulates.
05
Transformation has been added to people’s day jobs
Functional leaders are running the change alongside their operational responsibilities. Both compete for the same attention and decision capacity, and operational priorities can displace programme work when the two conflict.
06
A headquarters programme is being rejected locally
The design was made centrally and the sites are complying rather than adopting. The programme is technically on track and practically going nowhere.
07
The benefits case has no owner
Targets were signed off at approval and never assigned. Nobody can distinguish a benefit that has been realised from one that has been forecast, and the business case is quietly diverging from reality.
08
The programme director has gone mid-flight
Departure or reassignment during delivery can disrupt momentum, vendor relationships and stakeholder confidence. Where the programme cannot wait for a permanent replacement, an interim appointment preserves continuity while the permanent search runs separately.
Is this the right seat?
Does the situation require an Interim Transformation Director?
The determining question is whether the programme needs an owner across functions, or whether one function needs to fix something inside it.
Appoint an Interim Transformation Director when:
- Several workstreams have to be sequenced against each other.
- Decisions are stalling between functions rather than inside one.
- Adoption, dependencies and benefits need coordinated ownership.
- The benefits case needs an accountable owner.
- Programme demands exceed the capacity or decision rights currently assigned.
Decision rule
When delivery and adoption depend on coordinated decisions across functions, an Interim Transformation and Programme Director can own the programme. Define how the remit works with technology, operational and business leadership rather than treating implementation and adoption as separate choices.
When a different role is the right one
Where the main gap is technology leadership or technical recovery, an Interim CIO leads that remit. A Transformation and Programme Director may still be needed for wider dependencies, readiness and adoption. The sponsor defines how the mandates work together and avoids duplicate decision ownership.
Where the business needs authority over ongoing operational performance across sites or functions, an Interim COO leads. A Transformation and Programme Director leads a defined change programme, coordinating with the COO where delivery changes the operating model.
Where the operating model itself has to change across sites, an Interim COO has the authority this role has to borrow.
Where the direction of the business is unresolved, no programme will fix it and an Interim CEO is the appointment.
For the transformation approach rather than the executive appointment, our digital and AI transformation service explains how CE Interim structures these programmes.
CE Interim defines the mandate first and recommends the role second.
Role comparison
Which role does the business need?
Scroll the table sideways →
| Interim Transformation Director | Interim CIO | Interim COO | Advisory consultancyy | |
|---|---|---|---|---|
| Owns | The programme and its adoption | The systems and the IT function | The operating model across sites | Analysis, design and recommendations |
| Authority | Delegated across programme workstreams | Delegated within technology | Delegated across operations | Advisory; executive decisions remain with the client |
| Risk it addresses | The change does not embed | Technology reliability, security and delivery | The operation does not deliver | Unclear design or delivery approach |
| Appointed when | Nobody owns delivery end to end | Technology leadership is the gap | Operational execution needs authority across functions or sites | Design, assessment or specialist advice is needed |
| Ends when | Benefits are owned and the model is stable | The platform is stable and led | The operation coordinates | Agreed advisory deliverables are accepted |
| Time to start | Ready to start within 72 hours of the completed mandate brief | Ready to start within 72 hours of the completed mandate brief | Ready to start within 72 hours of the completed mandate brief | Depends on scope and engagement |
Interim Transformation Director
Interim CIO
Interim COO
Consultancy
Failure modes
How these appointments fail
Go-live is treated as the finish line.
The programme celebrates the launch and disbands. After go-live, teams can revert to spreadsheets and local workarounds if adoption is not sustained. The technology remains in place, the benefits do not follow, and the business now carries both the old process and the cost of the new one.
Change is handed off instead of led.
Functional leaders are given the transformation alongside their day jobs. Execution fragments, cross-functional ownership stays unclear, and operational priorities can displace programme work when the two compete. This is a structural problem, not simply a commitment problem.
The programme office reports instead of deciding.
A governance structure without a decision-maker produces status. Escalations are logged and returned to the same functions that could not agree. The programme remains green until it is suddenly red.
A consultancy delivers the plan and nobody owns delivery.
The design is competent and the sequencing is sound. What is missing is someone who will take a decision that a function objects to. Strategy alone does not fail loudly, it fails slowly.
Scope of authority
What an Interim Transformation Director mandate should include
A named sponsor and a defined decision space.
This role’s authority is borrowed rather than owned: the workstream leads report elsewhere. What can be decided without escalation, and what cannot, is agreed in writing before the executive starts, because it will be tested in the first month.
Sequencing authority.
The right to decide what happens in which order across workstreams, and to delay a milestone when the organisation cannot absorb it. Sequencing can be as consequential as design, particularly where several workstreams compete for the same organisational capacity.
Authority to stop things.
Authority to pause, remove or re-sequence work within agreed decision limits. Material changes follow the sponsor approval route and contractual change control. Essential business, safety, security and compliance requirements are not removed simply to reduce workload.
Ownership of the benefits case.
Maintain a benefits case with named business owners, baselines and measures separating realised value from forecasts. Work with finance to validate the evidence and seek sponsor approval where revised assumptions materially change the business case.
Vendor accountability.
Lead programme-level supplier commitments within the agreed mandate. Define one accountable route for scope, escalation and acceptance. Where a CIO leads technical delivery, coordinate responsibilities with that role; authorised client sign-off uses both technical evidence and business-readiness criteria.
Adoption authority.
Agree adoption and acceptance criteria with the sponsor, business owners and technical leads at the start of the mandate. Require evidence of effective use before accepting programme completion. Record any phased handover, residual actions and approved exceptions rather than treating installation as adoption.
Authority note
Decision rights, approval limits and escalation routes are agreed before the start. The interim decides within the mandate; the sponsor resolves reserved decisions promptly. Changes to scope, funding, benefits or acceptance follow the agreed governance.
Statutory responsibility, scope and cover
Statutory responsibility.
Where the mandate requires it, the executive may receive defined signature authority within the programme’s scope, delegated statutory duties or, where formally appointed and permitted by the local corporate structure, a statutory position. The scope is agreed before the start rather than assumed.
Scope is agreed before the executive starts.
The client, CE Interim and the executive define duties, boundaries and signature limits in writing.
Insurance is arranged per mandate.
Executives carry their own professional liability and directors’ and officers’ cover. On some mandates the client provides or contributes to it. CE Interim and every member of the Valtus Alliance carries its own cover as well.
Mandate arc
How a transformation mandate unfolds
This role is often appointed after a programme is already under way. The sequence is adapted to the current position. Benefit owners, acceptance criteria and urgent priorities are agreed during the opening assessment, then tested and refined through delivery.
01
Taking control
Establish what is actually true
Test reported progress workstream by workstream. Identify blocked decisions, dependencies, capacity limits and material risks. Establish one issue queue and escalation route. Agree benefit owners and acceptance criteria, then confirm with the sponsor which work should continue, change or stop.
02
Delivering
Decide, sequence, and hold the line
Resolve decisions within the agreed mandate and escalate reserved matters. Sequence work against dependencies, business readiness and delivery constraints. Hold suppliers to agreed commitments, test adoption against the criteria and measure realised benefits against the approved baseline and forecast.
03
Embedding
Make it survive the programme
Verify adoption against the agreed criteria and transfer operating responsibilities to named business owners. Record remaining actions, risks and any approved phased handover. Define ongoing benefits measurement and the continuing programme-office role before the interim leaves.
PROGRAMME MANDATE · 9 TO 18 MONTHS
In CE Interim’s experience, the opening weeks are used to establish one decision cadence, one issue queue and a working escalation route. Adoption takes longer to prove than implementation, so duration depends on the scale of the change and how far delivery has drifted before the appointment.
RECOVERY MANDATE · FROM THE POINT OF APPOINTMENT
The remaining duration is assessed from appointment against outstanding scope, dependencies, readiness and the resources available. The sponsor and interim agree the recovery priorities, review points and handover conditions rather than treating elapsed delay as the timetable.
Talk to a Partner about the mandate before the situation defines it for you.
Outcomes and handover
What effective transformation leadership should achieve
Decisions get made
Decisions are resolved within agreed authority; exceptions reach the named sponsor through defined escalation routes and tracked response times.
Scope matches capacity
What the organisation is being asked to absorb is aligned with what it can realistically execute, even where that requires reducing or resequencing the original scope.
Adoption, not go-live
The new way of working is how the business actually operates, verifiable at site and function level rather than in a completion report.
Benefits with names against them
Every benefit has a named business owner, baseline, measurement and review date, with realised value distinguished from forecasts.
Vendors held to scope
Implementation partners deliver what was contracted, and the acceptance decision belongs to the business.
Handover
Ownership moves from the programme structure to the line. The continuing role of the programme office is then reduced, retained or closed according to what the business still needs. Continuity without dependency.
Who we send
The Interim Transformation and Programme Directors we appoint
Has rescued a programme, not only run one.
Has taken ownership of something already under pressure, established what reported progress can actually be relied on, and reset the delivery path. Executives who have done this recognise the pattern early, and know which reported progress to test first.
Has delivered adoption, not go-live.
Has stayed past the launch, watched the reversion begin, and stopped it. This is the difference that matters in this seat, and it is worth testing directly rather than assuming from a curriculum vitae.
Has cancelled something.
Has removed scope from a live programme, defended the decision to a steering committee, and delivered what remained. The ability to stop work can be as important as the ability to start it.
Has held authority they did not own.
Programme authority may come from the sponsor while functional reporting lines remain unchanged. The executive therefore needs experience making that authority work across functions without relying on direct line management.
Has been believed by the shopfloor as well as the steering committee.
A programme designed centrally is adopted, or quietly worked around, at the sites. Executives credible in both rooms find out which is happening. Those credible in only one find out late.
CE Interim works through more than 90 operating partners across the Valtus Alliance, in over 30 countries. Where a workstream needs an additional specialist midstream, CE Interim can draw one from the same network.
The appointment model
From confidential briefing to executive appointment
01
Situation briefing
A Partner conversation under NDA, typically with a Partner who has run programmes of this kind. Where the programme stands, where execution is broken, and what authority the sponsor can delegate.
02
Mandate definition and challenge-specific assessment
CE Interim defines the scope, the sponsor, the decision space and what success looks like, then interviews each executive for this programme at this stage rather than against a generic transformation profile.
03
Presentation, appointment and governance
You receive one or two pre-vetted executives matched to the challenge, not a CV list. Weekly Partner check-ins and milestone tracking follow.
Cross-border strain
Why cross-border programmes are harder to govern
What headquarters needs
- Adoption at the sites, not compliance in the reporting
- To hear that a design will not work locally before it is rolled out
- One honest view of progress across every location
What each site needs
- Someone present often enough to be told what is actually happening
- A design that survives contact with how the site really works
- Scope reduced to what it can absorb while still running the business
Local teams may not refuse a headquarters programme outright. They can comply in the reporting and continue as before in practice, leaving headquarters with a progress picture that does not reflect actual adoption.
Corridors we work in most often
Situation modules
Typical transformation and programme mandates
Enterprise-Critical Transformation Programmes
A programme has been designed, funded and launched, and delivery has stalled between functions. The mandate is to reset dependencies, responsibilities and scope against the business outcome and available capacity, then resolve the decisions blocking progress.
Governance, Visibility and Control
The programme reports green and delivers nothing, and the benefits case has no owner. The mandate is to make progress measurable and accountability real.
Post-Merger Integration and Carve-Out
A transformation is running inside an integration and competing for the same capacity. Working with the integration lead, the mandate coordinates dependencies, readiness and delivery priorities so the two programmes do not undermine each other.
Operational Turnaround
A change programme is running while the operation is under pressure. The mandate is to decide what the business can absorb now and what has to wait.
Sector environments
Where CE Interim appoints transformation and programme leadership
Primary sectors
Also served
Ownership environments
Sector understanding matters. The defining selection criterion is comparable programme responsibility at a comparable stage, in a comparable operating environment.
Case evidence
Transformation mandates in practice
European industrial group · High-end equipment for aerospace and medical customers · More than 400 people across Germany and Central Europe · Private equity owned
Professionalisation, digitalisation and ERP readiness at a Hungarian subsidiary
Situation
A fully autonomous manufacturing subsidiary with end-to-end value-chain responsibility, rather than an assembly site, was entering a decisive transformation phase.
Mandate
Professionalise operations, digitalise processes and prepare for a new ERP platform, with the objective of a scalable and internationally competitive business. Scoped at six to twelve months.
TARGET OUTCOME
Professionalise operations, digitalise core processes and establish ERP readiness so the subsidiary has a scalable operating model and clearer management control.
Role Note
This programme was led from the chief executive seat, rather than a programme-director seat. It illustrates a transformation that followed a wider business-leadership appointment.
Related role: Interim CEO
Global materials group · More than 150 years of history · Present in more than thirty countries · Intervention across ten Polish sites
Group ERP template rolled out across ten locations in Poland
Situation
A group ERP template was being deployed into the Polish entities, with the technical implementation governed centrally and delivered locally through an implementation partner.
Mandate
Programme delivery against a fixed go-live: holding the partner to scope, coordinating ten sites, and getting the business ready rather than only the system.
TARGET OUTCOME
Coordinate the ten-site rollout around shared milestones, operational readiness and implementation-partner accountability, with adoption responsibilities assigned before go-live.
Role note
The same Polish ERP mandate also appears on the Interim CIO page. It illustrates how system delivery, site readiness and cross-functional programme coordination work together.
Speak with the Partner who would lead your mandate.
Cost and duration
What a transformation mandate costs and how long it runs
Mandates are priced as a daily rate against scope, authority and duration. There is no percentage of salary, no placement fee and no upfront investment. You pay for days worked against an agreed mandate, and the rate is confirmed before the executive starts.
Indicative daily rate
€1,000 – €3,000
Higher where the mandate carries a statutory position or cross-border complexity.
Duration and milestones
Programme mandate
Nine to eighteen months
EARLY MANDATE FOCUS
Decision cadence, issue ownership and escalation
EXECUTIVE READY TO START
Within 72 hours of the completed mandate brief
What moves the number.
The number of workstreams, sites and countries in scope. How far the programme has drifted before the appointment. Whether systems implementation and vendor management sit inside the mandate. Whether the benefits case has to be rebuilt from the approval papers. Every mandate is delivered on site.
What it should be measured against.
Not the cost of the mandate, but the cost of the situation continuing without an accountable executive while decisions are deferred.
What you will actually pay.
A Partner gives you a figure in the first confidential conversation. No charge, no obligation.
Questions
Questions sponsors and boards ask
Interim Transformation Director or Interim CIO?
The CIO leads technology delivery, the IT function and vendor accountability. A Transformation and Programme Director leads wider cross-functional change and adoption when that is the principal mandate. Both work with business owners on readiness and effective use; the sponsor defines the interfaces and decision rights.
Why not use the consultancy that designed the programme?
A consultancy typically provides analysis, design and recommendations. An Interim Transformation Director carries delegated executive authority to make sequencing, scope and adoption decisions within the mandate, and remains accountable for implementation across functions.
Is this the same as your digital and AI transformation service?
They work together. The service page sets out how CE Interim structures transformation programmes. This page is about the executive who owns delivery: the authority required and how the appointment is made.
Our functional leaders are already running it. Why appoint someone?
Where programme demands exceed existing capacity or cross-functional decision rights, a dedicated leader can make the change a primary mandate. Functional leaders still own their operations and contribute resources. The sponsor and interim agree priorities and responsibilities rather than assume one appointment removes every competing demand.
Can the executive direct people who do not report to them?
Often, yes. Workstream leads may remain in their functional reporting lines while the sponsor delegates programme decision authority to the interim. The decision space is therefore defined in writing before the executive starts rather than discovered during the first escalation.
The system is live. Is it too late?
No. Assess why adoption has stalled after go-live: process ownership, user capability, workload, incentives and technical defects may all matter. The interim coordinates the business response with functional leaders and the CIO. Training, system fixes and operating changes remain part of the solution where the evidence requires them.
Can the mandate include stopping parts of the programme?
Yes. The mandate can authorise pausing, removing or re-sequencing work within agreed limits. Material changes follow sponsor approvals and contractual change control. Essential business, safety, security and compliance requirements remain protected; reducing scope is an option, not the automatic answer to every recovery.
Who contracts the executive, and what does the client carry?
CE Interim structures mandates on a business-to-business basis, and the interim executive does not join the client as a permanent employee. The contracting party is a local entity or a regional hub depending on the country of intervention, drawn from more than thirty entities across the Valtus Alliance. Employment-status, tax, social-security and related obligations depend on the jurisdiction, the contracting structure and the circumstances of the mandate, so the engagement is structured for the country in which the work is performed.
Who carries the risk where the executive holds a formal position?
The executive carries their own directors’ and officers’ and professional liability cover; on some mandates the client provides or contributes to it. CE Interim and each Valtus Alliance member carry their own cover. Duties, boundaries and signature limits are agreed by the client, CE Interim and the executive before the start. Insurance is subject to policy terms and does not remove legal responsibilities.
Why do you not call this an Interim CTO?
Because CTO is widely used to mean Chief Technology Officer. Using the acronym for a transformation mandate creates ambiguity and can describe the wrong job, so CE Interim writes the role out in full.
How do you measure whether it worked?
Use agreed adoption criteria at site and function level, and benefits with named business owners, baselines and measures separating realised value from forecasts. Technical completion alone is not programme acceptance. Any phased handover records remaining actions, approved exceptions and continuing benefits measurement.
Can this run alongside our existing programme office?
Yes. Retain useful planning, assurance, reporting and control capabilities. Agree the programme office’s existing remit and the interim’s decision authority, with clear interfaces and escalation routes. The appointment does not require removing a useful programme office or assuming it has no authority of its own.
What happens at the end?
Operating responsibilities transfer to named business owners, with agreed adoption evidence, open actions and a continuing plan for benefits measurement. The sponsor and business owners retain their agreed responsibilities. Any programme-office role is reduced, retained or closed according to what the business still needs.
A programme that is implemented but not adopted carries the full cost and returns little of the benefit.
Speak directly with a CE Interim Partner about the programme, the mandate and the authority required. Confidential, and it does not commit you to an appointment.
Partner response within 24 hours.
EN 
DE 
FR 
IT 
PL 
RO 
CS 
SK 
HU 
ES 
RU 
AR 
SL