Situation 04 / 08 — External pressure

Retiring expertise

One person understands the system. He gave notice in March.

Retiring expertise is one of the most common reasons that companies contact Salem. The system works but has been back of mind for a long time. Then the person who has kept it running sets a retirement date, and the clock to support it starts.

Sound familiar

How Salem approaches it

01

Capture the knowledge while the expert is still on staff

Salem engineers work with the local administrator to write it down: interfaces, batch schedules, failure modes, and the workaround from 2009 that nobody remembers the reason for. The result is technical documentation produced by people who can read the code, not interview notes.

02

Take over support so the retirement date stops being a cliff

Salem covers the system under contract. Nothing has to change on the platform for coverage to begin, which means the timeline is no longer driven by one person’s calendar.

03

Decide the long-term path on the business’s schedule

Once the knowledge risk is contained, modernization returns to being a planned decision with options, rather than an emergency handoff to whoever is available.

Related services

When is his last day?

His last day sets everything else.

Tell Salem how much time is left and what the system does. You will get a realistic answer about what can be captured, supported, and planned in that window.

We use cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.