The Webster Dictionary describes fatigue (also sometimes called exhaustion, tiredness, languor, lassitude or listlessness) as "a subjective feeling of tiredness which is distinct from weakness, and has a gradual onset."
Technology management transformations – and in specific, I&O transformations – suffer from fatigue in many organizations. Some of it is due to the fact that the term "transformation" is more jargon than anything real. Transformation means many things to many people and therfore we never really exit a transformation as we move from project to project, continually transforming.
If I asked you, does I&O transformation mean reshaping your architecture? Streamlining your service management and integration (SIAM) processes? Adjusting your automation strategy? Improving your application performance management to become more proactive? Reducing operational cost? Shifting your infrastructure and applications into the cloud? You would say "yes" to all of them, with all of them being described as some kind of transformation. Eliminating fatigue means following a transformation plan. The plan needs to be supported with details to shift the conversation from costs of the technology “feeds and speeds” to how the technology will enable the business to win, serve, and retain their customers.