If it isn’t broken don’t fix it is a reasonable adage if you know it isn’t broken. However, as in medicine prevention is always better than cure. When symptoms exist that suggest a change has occurred we should all be wary. This is as true in IT as it is in health.
How often have you heard the system is running slow today? Or seen impatience waiting for that vital web page to load? Been told that we have lost an important email? These are all symptoms that are likely hiding more serious issues waiting to reveal when we least expect or want them. But as with visiting the doctor often the last thing on our or our IT function’s mind is a health check.
Technology is ever changing. New systems, solutions, ideas and processes are added to our portfolio daily. The overall complexity is increasing and our capability to keep pace with education, knowledge and understanding is diminishing. We add new to old, we change, we overlay, we add capacity, we integrate. IT is a fluid dynamic that is ever changing creating new often unrecognised symptoms. In this context if it isn’t broken don’t fix it becomes a tougher adage to rely upon.
How can we help?
What can we do to minimise the risk of IT change or reassure ourselves that the system is indeed stable and fit for purpose? A focused Capability and System Review would be a good start.
- An objective high level AS-IS map of your current IT portfolio that identifies the critical integration and process dependencies.
- A critical review of the various technologies utilised and your capabilities to support and develop those technologies over time.
- A segmentation analysis detailing the elements of the IT portfolio in respect the service timeline – retire, redundant, legacy, core, enhance, innovation.
- A risk analysis on core systems
- Recommendations for further investigation, change, preventative maintenance or simply reassurance that all is well.