Hiring an interim service manager: when it fits and when it does not

Hiring an interim service manager makes sense when you temporarily need expertise or steering power you do not currently have in house, with a clear beginning and end. It is the wrong choice when you are trying to plug a structural gap that calls for a permanent hire, or when you hope an outsider will solve a problem in a few months that the organization itself is unwilling to address. This article shows when interim fits, what defines a good assignment, and how to make sure the knowledge stays behind when the assignment ends.

When interim fits

Interim works best when the need is clear and temporary. A few situations where it is usually a good choice.

A temporary gap. Your service manager leaves, falls ill or goes on leave, and you do not want the service to sag while you look for a successor. An interim keeps the shop running and prevents ongoing improvements from stalling.

A specific job with a start and finish. You are about to select and roll out a new ITSM tool, you want to professionalise the service desk, or you need to clear a backlog. Those are bounded assignments where temporary, experienced capacity fits exactly. How to approach such a tool selection is covered in choosing an ITSM or ESM tool.

Expertise you do not need permanently. Sometimes you need someone who has done this more often, to set a direction or get a team moving. If you do not need that knowledge permanently afterwards, it makes no sense to create a fixed role for it.

A fresh pair of eyes. An outsider sees patterns that have become normal internally. Someone who is not part of the organization dares to ask why something works the way it does, and has no stake in the status quo.

In all these cases the common denominator is that the assignment has a clear end. Interim is not a disguised permanent appointment; it is a temporary engagement with a result.

When interim does not fit

Just as important is knowing when not to do it.

When you actually need a permanent hire. If the role is structural and stays that way, interim is an expensive detour. You would be hiring externally for months for work that calls for a permanent employee. Use interim at most to bridge the period until the permanent hire, not as a replacement for it.

When the organization is unwilling to address the problem. An interim can design and kick-start an improvement, but cannot force the organization to change. If management does not back the change, the result evaporates the moment the interim leaves. The will to change has to sit internally.

When you hope for a miracle in too little time. Culture and habits do not change in six weeks. An assignment that is too tight yields a nice report and little lasting change. Give an interim assignment the time the subject genuinely needs.

When there is no internal counterpart. Without someone internal who walks along and takes over afterwards, the knowledge leaves with the interim. More on that below.

What defines a good interim assignment

The difference between an interim assignment that delivers and one that just costs money often lies in the framing up front. A good assignment has a few things sharp.

• A concrete goal. Not "improve the service desk", but "halve the lead time of requests" or "tool selected and configured". Measurable, so at the end you can see whether it worked.
• A clear scope. What is in and what is out. Without a boundary an assignment quietly grows and the result dilutes.
• An end date or end result. Interim without an end is not interim. Agree when the job is done, or on what condition.
• A mandate. An interim who is allowed to decide nothing can achieve nothing. Arrange up front which decisions fall within the assignment.
• An internal owner. Someone in the organization who stays responsible and carries the results afterwards.

If you do not yet have the goal sharp, that in itself is a signal. Start by mapping where you stand. An ITSM maturity assessment helps aim the assignment at the place with the most gain, instead of at whatever happens to stand out loudest.

How to make sure the knowledge stays behind

The biggest risk of interim is that the improvement walks out the door with the interim. The assignment is done, the report is there, and three months later the organization is back to square one because nobody took over the new way of working. You prevent that by building in continuity from day one.

Appoint an internal counterpart. Someone who walks along from start to finish, not just gets briefed at the end. That person gradually takes over the knowledge and ownership, so the handover is not a separate moment but a gradual process.

Write down what you agree. New ways of working, agreements and decisions belong in a living knowledge base, not in the interim's head. How to set up such a knowledge base that actually gets used is covered in building a knowledge base people use.

Invest in the team, not just the process. An interim who takes the team along and coaches them leaves more behind than one who does everything themselves. If the people on the floor can carry the new way of working themselves, the improvement stands. That ties into onboarding service desk staff: transferring knowledge and habits is a craft in itself.

Plan the handover, do not plan it away. Reserve the final weeks of the assignment deliberately for handover, not for the last stretch of the work itself. Otherwise the interim leaves while the team is not yet ready to take over.

Continuity is not an afterthought; it is a design principle. An interim assignment set up for handover from the start delivers lasting results. One that is not delivers an expensive breather.

Frequently asked questions

What does an interim service manager cost? That depends on the weight of the assignment, the duration and the level of experience. More important than the hourly rate is whether the assignment delivers a concrete, measurable result. A cheaper interim who leaves nothing behind is more expensive than one who moves the organization forward for good.

How long does an interim assignment in service management last? From a few months for a bounded job to a year or longer for a bridge or a larger professionalisation effort. Culture and habits do not change in six weeks, so be realistic about the time the subject genuinely needs.

What is the difference between interim and consultancy? A consultant advises and usually delivers a report or an approach. An interim temporarily takes over a role with responsibility and carries out the change too. In practice these blur; what matters is agreeing up front whether you are buying advice or execution.

How do you prevent the knowledge from leaving with the interim? Appoint an internal counterpart from day one who walks along, record ways of working in a knowledge base, coach the team instead of doing everything yourself, and reserve the final weeks deliberately for handover. Continuity is a design principle, not an afterthought.

Not sure whether interim is the right choice for your situation, or want to frame the assignment sharply? book a call and we will look together at what fits. For temporary steering power and taking your team along, see our services for coaching and vision and strategy.

Further reading

• Interim management (Wikipedia)
• IT service management (Wikipedia)
• What is ITSM? (Atlassian)
• ITIL (AXELOS)