Far too often I see companies invest heavily in new tools; large databases or fancy analysis tools, or complex code or test generators.
Unfortunately, those spending the money often get things backwards. Technology is a tool, not a solution. Buying the largest, most expensive database supply chain suite for millions of dollars is not going to guarantee success. While the salesman probably told you about the impressive successes, they probably didn’t tell you about the many failures. That is because people don’t advertise p the instances where the installations did not turn out optimally or where far more was spent bringing in the new systems than were saved doing so.
Buying large systems to jumpstart improvement is what I generally call “buying enough rope” (as in buying enough rope to hang yourself)
There is an insidious unspoken assumption about technology. That is, if you spend enough money, you are liable to solve SOMETHING.
Sometimes this is true, but too often, the improvements are less than the cost of the new systems, and the money you spent on training, and consulting, and switching over to the new tools.
My philosophy is that you should start with a clear problem that you want solves, and then work on the basics. (You have to have a system before you can automate one)
Ironically you will generally find a much higher ROI refining basic skills (for project managers, or administrators, or basic training for users) than you get swapping out old tools for new ones.
In general you should only swap out technologies when there are specific essential features in the new set that simply cannot be implemented on the old.
Unfortunately, learning to use old tools is not glamorous. Buying new fancy toys is exciting… but it is also expensive and can cost more (in time and money and effort) than switchover is worth.
I could bore you for hours with horror stories of large corporations that literally spend hundreds of millions of dollars on major system overhauls and after three years of solid effort, had nothing to show for their efforts but embarrassingly empty coffers. In the end, the only people who made money were the consultants and tool vendors.
Ultimately, buying the best hammer in the world will not guarantee that you build a good house. Buying the best code generator in the world does not mean you will be able to write good code. Having newer more expensive tools is fun, but if you did not have a clear problem up front to justify the purchase of the tool, you are probably just paying a lot of money hoping the new technology will solve something.