Never get attached to a specific technology
The tools that work today can still become tomorrow’s migration project.
After writing about why you should get comfortable switching models, I want to extend the same idea to technology as a whole.
One intrinsic attribute of technology is that it is always evolving.
For public-facing deliverables like websites, most people understand this already. A site will probably need a revamp every three to five years.
For internal and business-critical systems, it is much harder.
“Don’t fix what’s not broken”, right?
Businesses need stability, for sure. You cannot rebuild everything every month just because something new came out. But stability can slowly turn into stagnation.
You should regularly ask what could improve your workflows, test new options when it makes sense, and stay ready to switch when the case becomes clear.
Sometimes, the switch is not even optional.
I have been using Amazon WorkMail, AWS’s managed business email service, for years. It is reliable, compatible with modern protocols, and cheaper than many alternatives. No complaints. I have been a happy customer.
Then, in April, AWS announced that Amazon WorkMail would be discontinued, effective March 31, 2027.
No direct AWS replacement. Just an end date.
I could complain all I want, but the service will still go away. At some point, I will have to move, or lose my email.
This is an exception, sure. Most tools do not disappear like that.
But it can happen to any product, platform, or service your business depends on today.
So do not get too attached.
Keep your systems stable, but keep your thinking flexible. And for the tools that matter, have at least a basic migration SOP so you are not forced to write one under pressure.
If you need help to increase clarity around your tech stack, and see your leverage grow, let’s talk