Updated: Oct 18, 2020
IT folks are notorious for over-thinking, over-designing, and over-complicating things. Oftentimes, implementing a minimum viable product and evolving it through small iterations through time is far more superior than delivering something perfect after 2 years. Fail fast, succeed fast. Have a clear road-map and follow it through, and when there are road-blocks — do course-corrections and seek alternative routes.
This article is a sequel to Fast IT (where I delved on why traditional IT is slow and gave some insights on how we can combat them). In this article, I would like to walk you through on, why not having a “Just do IT!” attitude is detrimental to your organization and will try to offer some suggestions on how to make the best possible decisions without getting caught with your pants down. “Whenever you see a successful business, someone once made a courageous decision.” -- Peter F. Drucker (the founder of Modern Management).
The main problem that most traditional IT teams have, is how to deal with their own internal demons in order to take a decision. This gets even worst, when they need to consider the universal impact of that decision at hand, the status quo, and the bureaucratic protocols they need to adhere to. As Victor Hugo wrote in one of his famous novel Le Miserables, “The straight line, a respectable optical illusion which ruins many a man.” So how can one avoid analysis-paralysis? Perhaps, the guiding principle of, “it is better to take a wrong decision, then make course corrections afterwards” is applicable here. Of course, if you made all the factual analysis and considered the most important and relevant things, then there’s a pretty good chance that you’ll make the right decision. That is, by far the best decision you can take, but the second best — is a wrong decision. Again, so long as you’ve done the necessary due diligence to understand the facts and the potential impacts, but still made the wrong decision – then accept it and do the necessary course corrections as soon as you realize your fault. The worst thing you can do, is not to take any decision at all. IT is not a perfect science, it is in fact, a very volatile one. What is true today may be wrong tomorrow. A leader in a magic quadrant today may fall behind tomorrow. A hype today maybe obsolete tomorrow. There are just so many things to consider in this fast-paced digital world and yes — taking the right decision is not an easy task.
So, what can you do if you need to choose between the devil and the deep blue sea? Most traditional IT teams would rather take the deep blue sea and drown. Why? They believe in archaic dogmas, beliefs, and traditions. They believe in the devil and the eternal damnation. Well, first of all “Inferno and the devil” were just a product of a creative imagination of Dante and then monetized by Hollywood. These unfounded fears make people take poor judgement calls, inhibit them to move forward, and bring them to a point of cognitive paralysis. “You can't make decisions based on fear and the possibility of what might happen” – Michele Obama. The problem with this situation, is that they don’t drown alone, oftentimes they drag the whole organization with them – and that would be a Titanic catastrophe.
In determining what is important and critical to your organization, you need to know what the top-line goals of your company are. Typically, in the end it boils down to increasing profitability; since increasing throughput/sales/price/market share, reducing cost, and reducing inventory are all part of the same equation. You cannot be blind-sided by the fact that in your quest to reduce cost, you negatively impact sales, production, or lose key strategic customers. Without loyal customers and good products, you will perhaps not be in business at all. People pay extra for prime and exceptional service, and this is what makes or breaks a company.
One of the fastest evolving IT services nowadays is the convergence of audio, video, and general collaboration services. During this global pandemic, the rat race for UCaaS (Unified Communication as a Service) tools has never been more relevant. The battle between Zoom, Webex, MS Teams vs traditional communication systems, has never been more intense. The choice for many is obvious, but to some it all depends on their specific needs, how receptive the organization is to the change, how much they are willing to pay, and most importantly — is the overall IT Infrastructure foundation ready? Imagine implementing a unified collaboration system where your phone, audioconferencing, videoconferencing system, and other collaboration services are all dependent on a 1.5 mb network without a back-up link and power protection? Unifying collaboration services in the same network only makes sense if and only if you can guarantee the resilience of the service. Otherwise, it will be a “hará kiri”, a suicide mission diving into the deep blue sea without even a flotation device. The problem with this equation is that “Rome wasn’t built in one day” — if you did not build the necessary IT Infrastructure foundation ahead of time, you will find yourself a year or two delayed in your project without even starting it yet. So, now when somebody asks why traditional IT is always 2 years late? It is the lack of a solid roadmap that allows for quick course corrections is really the main problem. As Yogi Berra once said, “If you don’t know where you’re going, you might wind-up some place else”. This is very true in IT.
“Just do IT!” does not mean taking haphazard decisions, but taking calculated risks; considering all the facts, conditions, and using top-line business priorities and goals as your North Star to guide you in those obscure decision-making processes. Consider “stop-gaps” as valid solutions to stop the bleeding. It's not about making the right choice. It's about making a choice and making it right.