The most common reasons that prevent IT to reach full potential – 5th: Analysis paralysis
- 1st reason – Do you know your process?
- 2nd reason – Too manual process!
- 3rd reason – Decentralize IT
- 4th reason – IT Silos
The fifth reason is also common to all IT departments that I know; it’s actually very common to most of the engineers also known to me. We, as engineers, prefer to know and to understand all the details of a problem before we start to work on the solution.
When we see a problem we start with a detailed and an in-depth analysis of the problem by collecting details of the current business process we want to enhance or fix. Obviously as the complexity of the problem increases we end up collecting more and more details until we are overwhelmed by the problems size and complexity. When we reach an understanding that we are facing a very complex project, we prefer to stop it and look for other projects.
Sometimes analysis paralysis helps, but most of the time as an anti-pattern we find ourselves pushing or cancelling big projects as a results of the analysis, while we could have run it successfully if we would follow the approach of breaking it to smaller chunks of work and do the analysis for each piece of work.
The end result of analysis paralysis is a growing list of old and complex projects and technologies that we keep on maintaining, while they continue to become more and more expensive to maintain, support and replace.