WHY CE INTERIM
Built by operators.
Trusted by boards.
We don't fill roles. We lead missions.
25+
Countries via Valtus Alliance
WHERE WE OPERATE
Interim Executive deployment
across 5 continents.
From Europe to the Gulf to the Americas — senior leaders, deployed locally.
5
Continents & Growing
FOR INTERIM EXECUTIVES
Your next mandate
starts here.
CE Interim connects senior interim executives with high-impact mandates across Europe, Americas & Middle East.
60,000+
Interim Executives in our global network
KNOWLEDGE HUB
Insights from the operators,
not the observers.
Editorial, research and intelligence from executives who've been in the room.
25k+
Monthly readers

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

↑
answers to

INTERIM TRANSFORMATION DIRECTOR

↓
leads

OPERATIONS · FINANCE · COMMERCIAL · SYSTEMS · PEOPLE

Programme authority across functions
Benefits ownership
72-hour readiness
PARTNER-LED GOVERNANCE

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.

The system goes live. The dashboards work. Behind the scenes everything slows down. Teams revert to spreadsheets, local sites treat it as another headquarters project, and the technology is in place while the transformation never embeds. That is not a software problem. It is what happens when change is handed off instead of led.

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 implementation is behind, over budget, or has been paused. Restarting it requires someone who will hold vendors accountable and take the decisions the original programme avoided.

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:

Decision rule

When the change spans functions and the risk is whether it embeds rather than whether it is built, this is the appropriate appointment.

When a different role is the right one

Where the programme is primarily a system implementation, an Interim CIO leads it and this role is unnecessary.

Where the transformation follows a transaction and the sequencing is governed by Day One and transitional service exits, an Interim PMI and Carve-Out Director carries the mandate.

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. 

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 Consultancy
Owns The programme and its adoption The systems and the IT function The operating model across sites The design
Authority Borrowed from the sponsor, across functions Held, inside technology Held, across operations Advisory only
Risk it addresses The change does not embed The system does not work The operation does not deliver The plan is wrong
Appointed when Nobody owns delivery end to end Technology leadership is the gap Execution fails between sites Before the programme starts
Ends when Benefits are owned and the model is stable The platform is stable and led The operation coordinates The report is delivered
Time to start Within 72 hours of the brief Within 72 hours of the brief Within 72 hours of the brief Depends on scope and engagement

Interim Transformation Director

Owns The programme and its adoption
Authority Borrowed from the sponsor, across functions
Risk it addresses The change does not embed
Appointed when Nobody owns delivery end to end
Ends when Benefits are owned and the model is stable
Time to start Within 72 hours of the brief

Interim CIO

Owns The systems and the IT function
Authority Held, inside technology
Risk it addresses The system does not work
Appointed when Technology leadership is the gap
Ends when The platform is stable and led
Time to start Within 72 hours of the brief

Interim COO

Owns The operating model across sites
Authority Held, across operations
Risk it addresses The operation does not deliver
Appointed when Execution fails between sites
Ends when The operation coordinates
Time to start Within 72 hours of the brief

Consultancy

Owns The design
Authority Advisory only
Risk it addresses The plan is wrong
Appointed when Before the programme starts
Ends when The report is delivered
Time to start Depends on scope and engagement

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.

A transformation that only adds is a transformation nobody has capacity for. The executive needs the standing to remove scope, pause a workstream or cancel a deliverable.

Ownership of the benefits case.

Named owners against each benefit, a measurement that separates realised from forecast, and the authority to reopen the case when the assumptions behind it have changed.

Vendor accountability.

Where implementation partners are engaged, the executive is the counterparty rather than a coordinator, with authority over scope, escalation and acceptance.

Adoption authority.

The right to set what “done” means at site and function level, which is a business standard rather than a technical one, and to refuse to close a workstream that has been implemented but not adopted.

Authority note

Authority must be proportional to the decisions the mandate requires in its first thirty days. In a programme, a decision deferred is not a decision delayed: the organisation continues in its existing pattern and the change becomes harder each week.

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 pattern below describes how CE Interim typically structures the takeover of an existing programme.

01

Taking control

Establish what is actually true

Separate reported progress from real progress, workstream by workstream. Identify where decisions are stuck and who has been avoiding them. Re-establish a single cadence, one issue queue and a working escalation route. Reduce scope to what the organisation can actually absorb.

02

Delivering

Decide, sequence, and hold the line

Take the decisions the programme has been escalating. Sequence workstreams against organisational readiness rather than against the original plan. Hold vendors to scope. Assign every benefit to a named owner and begin measuring realised against forecast. 

03

Embedding

Make it survive the programme

Move ownership from the programme structure to the line. Define adoption at site and function level and refuse to close a workstream that has been implemented but not adopted. Define the continuing role of the programme office according to what the business still needs rather than allowing it to become permanent by default.

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

Where the programme has already drifted, the length follows how far it drifted before anyone owned it.

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

The programme stops escalating and starts resolving, and the interval between issue and answer is measured in days.

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 an owner, a measurement and an honest distinction between realised and forecast.

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

What each site needs

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

Germany to Poland
Germany to Czechia and Hungary
Western Europe to Central and Eastern Europe
Western Europe to the United States
United States to Central Europe
International Private Equity to a local portfolio company

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 take ownership, reduce scope to what can be absorbed, and make the decisions the programme has been avoiding.

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, competing for the same capacity. The mandate is to sequence them as one system rather than two.

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

Manufacturing and Industrial
Automotive
Aerospace and Defence
Pharma, Life Sciences and Medical Devices

Also served

Chemicals
Food and Beverage Processing
Energy
FMCG
Logistics
Construction and Real Estate
Technology and Media

Ownership environments

Private Equity portfolio companies
Corporate groups and international headquarters
Mittelstand and mid-market industrial groups
Industrial holdings

Sector understanding matters. The defining selection criterion is comparable leadership responsibility in a comparable situation, in a comparable ownership 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. 

Outcome

Operations were brought onto a more disciplined and scalable footing, with processes standardised, digitalisation advanced and ERP readiness embedded into the wider transformation. The subsidiary entered the next phase with stronger management control, clearer operating routines and a more robust platform for international growth.

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. 

Outcome

The ten-site rollout was brought under one operating cadence, aligning site readiness, implementation dependencies and partner accountability ahead of go-live. Local issues were identified and escalated earlier, giving the business clearer ownership of adoption and reducing the risk of a technically complete but operationally unready deployment.

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

Decision cadence established

In the opening weeks

Executive on site

Within 72 hours of the completed 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

CIO where the programme is primarily a system implementation and technology leadership is the gap. Transformation Director where the change spans functions and the risk is whether the business adopts it rather than whether the platform works.

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.

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.

Because it is a second responsibility, programme work competes with day-to-day operational priorities. A dedicated transformation leader removes that structural conflict and holds the change as a primary mandate rather than an additional task.

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.

No. A programme can still require intervention after go-live. Reversion after launch is where transformation value can be lost, and the mandate focuses on restoring adoption by treating it as a leadership problem rather than a training one.

It should. A transformation that only adds is one nobody has capacity for. The authority to remove scope, pause a workstream or cancel a deliverable is part of the mandate rather than an escalation.

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.

Insurance is arranged per mandate. The executive carries their own directors’ and officers’ and professional liability cover, and 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. The scope of responsibility, the boundaries and the signature limits are agreed in writing by the client, CE Interim and the executive before the executive starts.

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.

Adoption at site and function level, verified rather than reported, and benefits with named owners and a measurement that separates realised from forecast. A workstream that has been implemented but not adopted is not closed, and the executive’s job includes refusing to close it.

Yes. A programme office can continue to provide reporting, coordination and administration while the Interim Transformation Director carries the delegated decision authority. Where responsibilities overlap, the mandate clarifies the boundary rather than assuming the programme office should be removed.

Ownership moves from the programme structure to the line, with named owners against every benefit. Any continuing programme-office role is defined deliberately rather than allowed to become permanent by default.

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 leadership situation, the mandate and the authority required. Confidential, and it does not commit you to an appointment.

Partner response within 24 hours. Urgent leadership situations prioritised.

CE INTERIM

Executive Interim Management Platform

I am a..

Client / Company

Hiring interim leadership

Interim Manager

Seeking mandates