Those findings matter. You have to know your backups are broken and your firewall is dead. But knowing and fixing them is remediation, not a technical initiative. A roadmap item should change the trajectory of the environment, not just patch the present. When the whole roadmap is "replace the thing that's old with a newer version of the thing," nobody has actually asked the harder question: does this thing need to exist at all?
The reflex is understandable. An engineer sees a server at end of life and reaches for the answer they've been rewarded for their entire career: replace it with a new server. Sometimes that's genuinely the right call. But one of our core jobs in technical alignment is to reduce support burden — and a newer server hosting the same problem doesn't reduce anything.
If an on-prem line-of-business app is generating a quarter of a client's tickets, putting it on fresh hardware leaves you with exactly that — a quarter of the tickets, on a box with a newer warranty. Working with the client to move that system to the vendor's own SaaS or cloud offering is what actually solves it. It removes the on-prem liability and the support load from our side, and it cuts downtime and issues on the client's side. That's the difference between replacement and elimination. We optimize for elimination: get rid of the server whose services can live in SaaS, get rid of on-prem identity where the business doesn't need it, move the app to the cloud option that already exists. Eliminate the thing, and you eliminate everything that came attached to it.
What this looks like in practice
A manufacturing client came to us with five Windows servers and two NAS units. One was a 2012 R2 box running as a secondary domain controller, whose only real job was serving a share that required SMB1 and NTLMv1 — protocols that should have been dead a decade ago — just to feed an MS-DOS CNC machine. The other physical box ran Hyper-V, hosting a primary DC with print services and an app server handling licensing for their CAD and labeling software plus their accounting database. The obvious initiative wrote itself: the host is six years old, replace it, migrate and update the VMs onto something new.
We didn't do that. Instead we moved the CAD and labeling software to the vendors' cloud licensing. The archival accounting files and that insecure CNC share went onto a single business-grade workstation — the host serving the company files, with a segregated VM isolating the CNC share so its ancient requirements couldn't touch anything else. Active Directory moved to Entra. Workstations came under Entra and Intune management, with device-based conditional access locking things down at both the device and account level. The aging NAS archives went to cold cloud blob storage, and the working file shares moved to SharePoint, with users trained on OneDrive and what their accounts actually gave them. Every on-prem liability, pulled into cloud services.
Here's the part that makes the case. With what server hardware costs today, the migration roughly broke even against simply buying a new host and storage — same spend, but in exchange for far more availability, security, and scalability. And then it proved itself: the client decided to open a production facility in another country. Because the foundation was now cloud-based, that just happened. Nobody had to fly out to stand up infrastructure on site. A replacement roadmap would have handed them a newer version of a system that couldn't have done that at all.
The part I didn't expect
I braced for resistance. Getting experienced engineers to unlearn a reflex they've been praised for over many years usually takes a fight. It didn't. Once the goal was reframed — from "keep it running" to "eliminate what shouldn't exist" — the team took off with it. Very little follow-up, almost no reminding. They understood the assignment. Now, when a genuinely hard roadmap item shows up, we brainstorm the best outcome together instead of defaulting to the catalog answer.
The newest server in the room is still a server. Someone still has to patch it, secure it, back it up, and replace it again in a few years. The best technical roadmap doesn't give a client a newer problem to manage. It removes the problem. Replacement keeps everyone busy. Elimination is what actually moves the business forward.