There is a particular kind of IT provider who is exciting to be around. They arrive with a roadmap full of platform migrations, a strong opinion about your firewall vendor, and a genuine enthusiasm for the thing they read about last month.
I have been that provider. I would gently suggest you hire someone duller.
Novelty has a cost that lands on you
Every new platform introduced into an environment carries a hidden bill: the learning curve of the team supporting it, the edge cases nobody has hit yet, the integration that works fine until an update changes an API, and the documentation that doesn’t exist because the product is eighteen months old.
That bill is real, and it is not paid by the person who recommended the change. It is paid by your staff at 8:40am when the thing doesn’t work, and by whoever inherits the environment in three years.
This is not an argument for never changing anything. It is an argument for changing things because a specific problem demands it, not because the current solution has become uninteresting to the people who maintain it.
The industrial habit that should be everywhere
I spent a decent portion of my career around industrial systems, where a network fault stops a production line rather than delaying an email. That environment teaches you a specific discipline, and it is one general IT largely lacks.
On a plant floor, nobody deploys a change on a Friday. Nobody makes two changes at once, because then you cannot tell which one caused the problem. Everybody writes down what they did. And critically, everybody has thought in advance about how to undo it.
None of that is technically sophisticated. It is just boring, and boring survives contact with reality far better than clever does.
What boring actually looks like in practice
It looks like standardisation. The same laptop model across the fleet, so a failure is a swap rather than an investigation. The same naming convention everywhere. Switch ports labelled at both ends. One backup product, not three inherited ones running in parallel because nobody was ever confident enough to turn the old ones off.
It looks like change windows that people actually respect, and a change log that a stranger could read six months later and understand.
It looks like choosing the mainstream option. The unfashionable vendor with ten years of deployment behind it, a support line that answers, and a thousand forum posts covering the exact error you are seeing at 2am. Being the most interesting customer of an obscure product is not a position you want to be in during an outage.
Boring is not the same as neglected
This is the distinction that matters, and it is where the argument gets misused.
An environment running Server 2012 because nobody wants to touch it is not boring. It is rotting. There is a real difference between deliberate conservatism, which is choosing proven technology and maintaining it rigorously, and simple avoidance, which is leaving things alone because change is frightening.
You can tell them apart easily. Deliberate conservatism has a documented lifecycle plan and known end-of-support dates. Avoidance has neither, and produces a sentence beginning “we’re not really sure what that server does, but…”
Where excitement is legitimate
I am not arguing for stagnation. Some changes are genuinely worth the disruption: moving off end-of-life systems, adding multi-factor authentication, replacing a backup product that has never successfully restored, consolidating three overlapping tools into one.
The test is simple. Can the person proposing the change describe the specific problem it solves, in a sentence, without using the word “modern”? If the justification is that the current approach is dated, that is aesthetics rather than engineering.
The uncomfortable business implication
Boring is a harder thing to sell. Project work is profitable and visible; maintenance is neither. There is a structural incentive across this whole industry to propose the migration rather than to fix the thing quietly and charge less.
I do not think most providers are cynical about this. I think enthusiasm is genuine, and it happens to point in a commercially convenient direction, which is a much harder bias to notice in yourself.
Worth asking your provider directly: what did you decide not to change this year, and why? A good answer is a very good sign.