Executive Leadership for Transformation, Transition and Recovery

Experienced leadership to stabilise, transform and deliver — from mandate definition through handover.

There are moments when an organisation cannot wait. A technology or operations executive leaves at the worst possible time. A transformation has been approved but nobody senior owns it. A programme is months late and the reporting no longer matches what is actually happening. A permanent hire is the right answer, but it is four to nine months away and the decisions are due now.

Interim management exists for those moments. It is not consultancy delivered from outside, and it is not a staffing gap filled by a contractor. It is an experienced executive taking a defined mandate inside the organisation — with authority, accountability and hands-on execution — for as long as the situation requires and no longer.

VODIS provides that leadership in technology, operations and transformation, with the emphasis on environments where the two are inseparable: regulated financial services, technology-intensive operations, and businesses going through modernisation, integration or launch. The measure of a good mandate is that the organisation needs the interim leader less every month, and can stand without one at the end.

When organisations bring in interim leadership

The trigger is rarely abstract. In practice an interim mandate starts because something specific has happened, or is about to:

  • A sudden executive vacancy, with decisions already in the diary.
  • A planned leadership transition where continuity matters more than speed.
  • A major transformation that has been approved but not yet owned.
  • A programme that is late, fragmented, or no longer reporting reality.
  • Delivery that has stalled between a promising start and anything operational.
  • An organisation redesign that needs someone to carry it rather than announce it.
  • Technology modernisation that has outgrown the capacity of the current team.
  • A merger or acquisition where integration is now the real work.
  • A carve-out or separation with hard dates and shared systems.
  • Regulatory or operational pressure that requires visible senior ownership.
  • A new institution or business line being launched from nothing.
  • Restructuring, where someone has to hold both the plan and the people.
  • A critical vendor or platform transition that cannot be delegated downwards.
  • The gap before a permanent executive is recruited, onboarded and effective.

What these have in common is not crisis. It is that a decision-making seat is empty, or occupied by someone who already has a full-time job, and the cost of waiting is higher than the cost of acting.

What interim management is — and what it is not

The words are often used loosely, and the difference matters commercially, because it determines who is accountable for the outcome.

Four distinct things:

  • A consultant analyses, recommends and hands over a conclusion. Accountability for acting on it stays with the client.
  • An executive adviser challenges, supports and strengthens decisions, usually without line authority over the people doing the work.
  • An interim manager holds the post. Agreed mandate, agreed decision rights, accountability for results, hands-on execution, and a planned handover.
  • A permanent executive owns the same post without a defined end date, and carries the longer-term organisational and cultural agenda.

VODIS offers the third and, separately, the second. It does not pretend that advice is leadership, and it does not take an interim mandate without the authority to discharge it. An interim arrangement is a working arrangement — it is not a regulated executive office, and it does not confer a statutory directorship unless that is separately and formally agreed.

Interim CIO and technology leadership

The most common mandate, and the one most directly supported by the founder’s own executive history. Scope is agreed at the start rather than assumed, and typically covers:

  • IT and technology strategy, set against what the business actually needs next.
  • Leadership of the technology organisation, including the parts nobody currently owns.
  • Organisation design: roles, structure, and the decisions each level may take.
  • Technology governance and the forums where decisions are genuinely made.
  • Enterprise and solution architecture, proportionate to the rate of change.
  • The application landscape, including overlaps and end-of-life exposure.
  • Infrastructure, hosting and the resilience expectations behind them.
  • Service delivery, support model and operational performance.
  • Cybersecurity governance as part of the technology mandate.
  • Sourcing strategy and the balance of internal and external capability.
  • Vendor and partner management across a growing platform estate.
  • Budget ownership, cost transparency and investment prioritisation.
  • The transformation roadmap and its dependencies.
  • Executive and board reporting that is honest about status.

Where the organisation already has a capable technology team but no one in the chair, the mandate is usually about decisions and direction rather than about doing the work for them.

Interim COO and operating leadership

Offered where operations and technology cannot sensibly be separated — technology-enabled operations and financial services in particular. Typical scope:

  • Operational leadership across the service and delivery chain.
  • Organisation and workforce structure for the operating model you need.
  • PMO and the portfolio of change running through operations.
  • Customer operations, service levels and the reality behind them.
  • Payments and transaction operations where these are core.
  • General services, facilities and the unglamorous functions that stop things.
  • Process optimisation and simplification before automation.
  • The service model: who does what, at what cost, to what standard.
  • Operational governance, risk and control in day-to-day running.
  • Execution of transformation inside the operation, not alongside it.

This is deliberately not offered as generic COO staffing for any industry. The relevant experience is technology-intensive and financial-services operations; outside that, VODIS would say so rather than stretch.

Interim transformation director

For organisations that have approved a transformation and discovered that approving it was the easy part. The mandate is to make it executable and then to execute it:

  • Mobilisation: turning an intention into a structured programme with owners.
  • One integrated roadmap rather than several competing ones.
  • Business and technology workstreams held together, not run in parallel.
  • Governance and the decision forums that actually unblock work.
  • Dependency management between workstreams, vendors and business units.
  • Delivery recovery where momentum has already been lost.
  • Executive and board reporting that survives contact with scrutiny.
  • Vendor coordination where several must deliver together.
  • Decision gates, so scope and spend are re-tested rather than assumed.
  • Transition to business as usual, with the operation able to carry it.

Where the need is programme governance and change capability rather than a named executive in post, programme and change management is the better-fitting service, and this page links there rather than duplicating it.

Programme and transformation recovery

A particular and common case: the programme is not dead, but it is no longer convincing. Typical symptoms:

Recovery work usually finds some combination of:

  • Delay that has stopped being explainable by any single cause.
  • Fragmentation into projects that no longer add up to an outcome.
  • Complexity that has grown faster than the ability to govern it.
  • Ownership that is formally assigned but not actually exercised.
  • Vendor conflict, or several vendors each delivering to their own plan.
  • A disconnect between what is being built and the business case.

The honest position: recovery is possible more often than it is attempted, but it is not guaranteed, and the first output is usually an unwelcome picture of where things really stand. VODIS will not promise a recovered programme in advance of understanding why it stalled — and sometimes the right recommendation is to stop, re-scope, or split it rather than to push on.

Fractional and part-time executive leadership

Not every situation needs a full-time interim. Where the organisation needs senior judgement regularly but not daily, a fractional mandate is often the more honest arrangement:

  • A fractional CIO for organisations too small for a full-time technology executive, but too dependent on technology to go without one.
  • Technology executive support alongside an existing, capable but stretched leader.
  • Transformation leadership for a defined period or a defined phase.
  • Periodic executive governance: chairing the forum that makes decisions stick.
  • A board or CEO technology adviser for a small number of consequential decisions.

The commitment is explicit — days per month, what is decided, what is escalated — because a fractional arrangement without that definition tends to become either unpaid or ineffective.

The mandate lifecycle

A practical model, applied to the situation rather than imposed on it:

  • 1. Situation and mandate definition. What the post is for, what the interim may decide, who they report to, and what the end looks like.
  • 2. Rapid assessment. Facts, risks, people, commitments and the gap between the reporting and reality.
  • 3. Priorities and stabilisation. Stopping the bleeding before redesigning anything.
  • 4. Governance and operating rhythm. The meetings, decisions and reporting that let the organisation run itself.
  • 5. Execution and transformation. Delivering the agreed agenda with the team, not around it.
  • 6. Capability transfer. Deliberately moving knowledge and authority into permanent roles.
  • 7. Handover and exit. A successor briefed, a documented position, and a clean departure.

The design intent runs through all seven: the organisation should need the interim leader less each month. A mandate that increases dependency has failed, however well it reports.

The first 30, 60 and 90 days

An illustrative framework, not a contractual guarantee — the shape of a mandate follows the situation, and a recovery looks different from a vacancy cover:

  • First 30 days — understand and stabilise. Establish the facts, the real risks, the committed dates and the people. Put minimum viable governance in place. Agree the short list of things that matter now.
  • 30 to 60 days — mobilise. Decisions taken rather than deferred; teams, vendors and roadmap aligned; execution started on the priorities; reporting that reflects reality.
  • 60 to 90 days — embed. A delivery rhythm that holds without constant intervention, structural blockers resolved or escalated, progress measurable, and the longer-term operating model and handover taking shape.

Some mandates compress this considerably; a carve-out with a fixed separation date has no 90-day luxury. Others run longer because the underlying problem is organisational rather than operational.

What stays constant is that the first month produces an honest baseline, and that the baseline is shared with the sponsor even when it is uncomfortable.

Why this is not generic executive staffing

Interim management is a crowded market, and much of it is CV-matching. The distinction VODIS offers is depth in the specific combination of technology, operations and regulated-sector transformation.

The relevant background covers:

  • CIO leadership, directly held.
  • COO and operations leadership, directly held.
  • Large-scale transformation programmes, led and coordinated.
  • Enterprise technology and core platform environments.
  • IT governance and the decision structures around it.
  • Organisation redesign and enterprise function setup.
  • PMO and programme office design and recovery.
  • Core banking and enterprise platform transformation.
  • Infrastructure and data-centre consolidation and relocation.
  • Process optimisation and enterprise automation.
  • Merger, acquisition and post-deal integration work.
  • Greenfield institution and regulated business launch.

The practical consequence is that the conversation can start at the level of the actual problem — a core platform, a separation date, a regulator’s expectation — rather than at the level of a role description.

Executive advisory — when an interim mandate is not required

Sometimes the organisation has the leadership it needs and lacks only an independent, experienced counterweight. Executive advisory is offered as a complementary mode, and deliberately not merged with interim management.

It can support:

  • CEO and board decision-making on technology and transformation.
  • Constructive challenge to a CIO or technology leader who wants it.
  • Transformation governance and the quality of what reaches the board.
  • Investment prioritisation across a competing portfolio.
  • Architecture and sourcing decisions with long consequences.
  • A second opinion on a programme that feels wrong but reports green.
  • Organisational design options before they are announced.
  • Independent executive review of a situation, function or programme.

The boundary is stated plainly: advisory does not automatically mean taking line authority. An adviser strengthens decisions; an interim manager takes them and is accountable for them. If a mandate needs the second, it should be contracted as the second. Relevant background is set out in Selected Experience.

Specialist leadership, including security

Cybersecurity and operational resilience frequently form part of an interim technology mandate: security governance, risk ownership, incident escalation, regulatory expectations and the controls that sit behind them.

That is different from claiming the security executive office itself.

VODIS does not present its founder as an interim CISO. The direct executive experience is CIO and COO, with cybersecurity and information security among the functions led — which is not the same as having held the CISO post, and the distinction is kept rather than blurred.

Where an engagement genuinely requires a CISO-level mandate, VODIS can assemble or coordinate an appropriately qualified specialist as part of the engagement model, subject to scope and availability. No such specialist is permanently employed by or already assigned to VODIS, and none is implied. Where the subject is the security capability itself rather than the leadership of it, cyber resilience is the relevant page.

Engagement models

The shape follows the mandate, not a staffing template:

  • A full-time interim mandate, in post for a defined period.
  • A fractional executive mandate, with agreed days and decision rights.
  • Transformation or programme leadership for a phase or a portfolio.
  • Executive advisory, without line authority.
  • A recovery or stabilisation mandate with a narrow, explicit remit.
  • A small specialist leadership team assembled around one mandate.

Senior specialists and delivery partners are brought together according to the mission. VODIS is a boutique practice: it does not maintain a large permanent bench of employed executives, and does not propose one.

Experience behind the approach

The approach is informed by programmes and executive responsibilities held by the VODIS founder in prior senior-management and executive roles, across banking, financial services and technology-intensive organisations.

That work spans technology and operations leadership, enterprise and core platform transformation, organisational redesign, programme governance and recovery, infrastructure and resilience, process automation, and integration following mergers and acquisitions.

Two points of accuracy, because they matter more than the claim. That work was performed in prior roles; VODIS is the practice through which the approach is now offered, and does not present those programmes as its own delivery history. And the examples are illustrative of capability, not a guarantee of outcome in a different organisation. The detail is in Selected Experience.

How this sits alongside the other VODIS services

Interim management is a way of engaging, not a separate subject matter. The specialist services below carry the depth, each with its own page:

An interim mandate usually touches several of these at once. The page you are reading is about who holds the post; those pages are about what the work consists of.

A reasonable starting point

The most useful first conversation is short and concrete: what post is open or unowned, what has to be decided in the next quarter, what has already been tried, and when a permanent appointment is realistically expected.

From there it is usually quick to say whether an interim mandate, a fractional arrangement or an advisory engagement fits — and, equally importantly, where none of the three is the right answer.

Discuss an interim leadership mandate