Get it delivered
Interim IT Director: an IT manager in place without waiting for recruitment
Keep your IT running with peace of mind
An interim IT manager is an experienced IT leader, operational from day one, who takes charge of a company’s IT for a fixed period: service continuity, managing teams and providers, day-to-day decisions and preparing what comes next. Lunova is a consulting firm based in Nyon, working across Western Switzerland.
The departure of an IT manager is a tense period for leadership: their knowledge of the information system and its history disappear within weeks, while recruiting a successor can take several months. In the meantime, the company has to keep running and teams need fully working tools. That is exactly what an interim engagement covers: securing the period, then handing it over properly.
Situations
When should you bring in an interim IT manager?
The departure of an IT manager with no internal successor identified is the most direct situation. Others lead to the same answer:
An unexpected departure or a recruitment that drags on.
The role has to be held while the search continues, without putting the business on hold.
An extended absence.
Leave, sick leave, internal mobility: the function still has to be covered.
A deteriorated situation to take back in hand.
Repeated incidents, drifting projects, poorly managed providers.
A transformation to lead.
Reorganisation, migration, change of scale: the workload exceeds what the team can absorb alone.
A role to structure before recruiting.
Defining what the company really needs before writing the job description.
Support
Working with the team in place
A team that has just lost its manager is first of all a worried team. A successful interim depends as much on relationships as on technology.
We start with interviews with direct reports, then discussions with the whole team. Collaborative workshops follow to identify the real issues and bring out solutions, those that often already exist within the team without ever having been acted on. Staff are then involved in implementing the actions chosen.
This approach has a double effect: decisions hold because they were built with the people who apply them, and key skills stay in the company at a time when they might be tempted to leave.
Method
How does an interim engagement work?
The engagement generally follows a three-stage trajectory, with the aim of identifying and launching the first improvements in the first month, without starting work the company cannot absorb. As a framework, the first 90 days can be organised as follows:
1. Days 1 to 30: understand and secure. Assessment of the situation, stakeholder interviews, identification of pain points and quick wins, first version of the action plan.
2. Days 30 to 60: structure and deliver. Clarifying roles and responsibilities where needed, finalising the action plan, delivering quick wins, preparing the longer-term work and setting up steering indicators.
3. Days 60 to 90: formalise and commit. Formalising the remaining elements, sharing the roadmap with leadership and the teams, committing providers to the work streams chosen.
This trajectory rests on experience of running information systems, not on a theoretical method: the first days are for listening and stabilising, not for announcing a plan.
Handover
How does an interim engagement end?
A successful interim is one you can step out of. The handover is prepared; it is not improvised in the final week.
It includes sharing information with all teams, working sessions with the successor (recruited or promoted internally) and handing over the roadmap with the progress of each work stream.
The point to calibrate is the overlap period: long enough to genuinely hand over, short enough for the two people not to get in each other’s way. It is decided with leadership, according to the successor’s profile and the work in progress.
Framework
ITIL as a working framework, not a standard to reach
Cyril Chapon is ITIL certified, the framework of good practice for IT service management. We use it as a working framework, adapted to the reality of an SME rather than applied to the letter: the goal is stable, manageable operations, not conformity to a model.
Experience
What changes when the role is held by a former IT director
Our approach to interim IT management adapts to the specifics of your company.
Proven experience
The engagement is led by a former European IT Director of an international group. That brings a hands-on approach: your application and infrastructure subjects are handled by one and the same person, with a complete view of the information system. Your teams have someone who speaks their language and quickly takes on board the specifics of your company.
A team on board
Staff are placed at the heart of the transition: involved in the work in progress, recognised for their knowledge of the information system. Building trust quickly is a decisive factor: it is what keeps key skills in place during a period of uncertainty. This approach draws on experience managing teams of all sizes, from 5 to 50 people.
A counterpart for leadership
Working with the company’s leaders is the other decisive factor. We work with you to understand your business stakes and the constraints specific to each department, so as to prioritise IT work on what matters to the company. In return, you get a clear view of the IT issues, expressed in leadership language, and you are involved in structural choices rather than presented with a fait accompli.
An outside view of your information system
Experience gained across many transformation projects brings a fresh view: what deserves modernising, what can wait, what consumes resources without adding enough value. Proposals always start from the business issues you want to address, not from a technology catalogue.
Deliverables
What you receive during and after the engagement
An interim engagement does not just leave a role covered. It leaves the company what it needs to continue without its interim manager: a situation understood, priorities decided, and a successor who does not have to rediscover everything. What the engagement produces follows the three stages described above.
An assessment of the information system.
Drawn up in the first month from interviews with leadership, teams, business units and providers: what works, what exposes the company, and what rests on a single person or a single supplier.
A prioritised action plan.
Pain points and quick wins on one side, longer-term work on the other, with what must be dealt with first and why.
Steering indicators.
A small number of measures set up during the engagement, which your leadership and your successor can keep reading afterwards.
A roadmap.
The horizon beyond the engagement, shared with leadership and the teams, and to which the selected providers are committed.
A handover file.
The progress of each work stream, the decisions taken and why, open issues and their deadlines, handed to the successor during the overlap period.
What is not included
Two things are not included in the service: technical delivery, which belongs to the selected providers, and running the information system once the engagement is over, which belongs to the successor. Follow-up beyond the handover is decided separately.
Comparison
Interim IT manager or Fractional CIO: which to choose?
Presence
Interim IT manager
Strong presence for a fixed period, to hold a vacant role or take a situation back in hand.
Fractional CIO
Regular, limited presence each week or each month, over the long term.
End of the engagement
Interim IT manager
Ends with a handover to the successor.
Fractional CIO
An ongoing arrangement, with no planned end.
The need it answers
Interim IT manager
Answers: “we no longer have an IT manager.”
Fractional CIO
Answers: “we don’t need a full-time CIO, but we do need a CIO.”
Before you decide
Frequently asked questions about interim IT management
How quickly can an interim manager be operational?
Much faster than a recruitment: there is no notice period to serve and no long onboarding. The start is arranged according to availability and the context of the engagement. The first days are used to meet the stakeholders and establish the assessment, not to learn the job.
How long does an interim engagement last?
The duration is counted in months: the time needed to secure the period and hand over to the successor.
Interim manager or Fractional CIO: how do you choose?
Ask yourself about the end: if the need stops the day someone takes over the role, it is an interim. If it has no foreseeable end and does not justify a full-time role, it is a fractional arrangement. Lunova carries out interim engagements.
Should we wait until we have recruited before starting anything else?
No. Putting IT on hold during a recruitment lasting several months can let incidents pile up and projects drift. An interim engagement deals with urgent matters and prepares the work streams while the search continues, and helps better define the role to fill.
How does the handover to the successor work?
It is prepared: sharing information with the teams, working sessions with the successor, handing over the roadmap with the progress of each work stream. The overlap period is calibrated with leadership, long enough to hand over, short enough for roles to stay clear.