The first time you outsource a capability is usually the last decision you get to make about it.
The question the business case leaves out
Somebody has to operate the thing. The proposal covers the purchase, the migration, and the benefit, and assumes operation as a background condition, the way it assumes the building will have electricity.
Operating a new platform is a skill that either exists on your team or does not, and if it does not, somebody has to acquire it during a period when they are already fully committed.
Eight hosts and three hundred machines
After the first virtualization rescue worked, I made it a directive to virtualize everything. I left the first host running only that one system, because virtualization was new to us and I was not confident adding workloads would leave it fast.
So I bought a second host and put around thirty systems on it. Then another. Then another. By the end we had eight hosts.
Those eight replaced roughly three hundred old machines, which we sold off as used equipment.
Every system got faster and the gains were large rather than marginal. Security improved, because workloads sat inside a managed layer rather than on individual boxes scattered around a building. Availability improved.
By any technical measure the project was a success, and that success created the problem.
They wanted to learn it
My team wanted to learn it. Nobody objected, nobody dragged their feet, and nobody argued the technology was a bad idea.
They had no time. They were running the middleware, the databases, the applications, and everything else, and those systems did not pause while a new platform arrived.
The classes existed. Training was available and I was willing to pay for it. Taking a class means days away from work that has no cover, and the work would still be waiting afterward with a few days added to it.
They would not do it outside normal hours either, which is a fair position and I have never held it against anyone.
Training requires slack. My team had none, and no amount of willingness substitutes for hours that do not exist.
So I hired the firm
The private cloud was running production systems and needed competent operation immediately. My people wanted the skill and could not get to it. Waiting was not available.
So I hired US Technical Services, the same people who had already proven themselves several times over.
It worked exceptionally well. The platform ran properly, the systems stayed up, and the technical outcome was everything I had wanted.
My team did not like it. They were right to feel that way and I would make the same call again, and both of those are true.
The door locks behind you
My team never got the skill back. The vendor ran that platform from then on, permanently, and nobody ever decided that. It arrived as a consequence.
The mechanism is simple once you see it. The reason to learn a technology is that you need to operate it. Once somebody else operates it, the reason disappears, and the hours that were unavailable when the reason existed are certainly not going to appear now that it does not.
Each year the gap widens. The platform advances, your people fall further behind, and bringing it back in house becomes a bigger project than the original migration.
Nobody makes that decision. It is made by the absence of a decision.
Three paths, and only one is a failure
If you intend to bring the capability in house eventually, say so before signing. Name who will learn it, put shadowing in the agreement, and set a date for reviewing whether it happened.
If you have decided to outsource permanently, that is a legitimate choice and deserves the same clarity. Know what your exit would involve and be honest with your team.
The failure is the third path, where nobody chooses, everyone assumes the skill will come back later, and it never does.
The question before signing is not whether the vendor is good. It is what happens in five years if they are still doing it, because for a capability like this, they will be.
The full article is on my site: https://thewritingking.com/outsourcing-a-skill-is-permanent/. It runs longer, carries the diagrams, and answers the questions readers ask most.
These are AI-made summaries of longer articles on my site, written with AI assistance from my own interviews and my own career. Nothing goes out that I have not read and approved.