Main Menu
Home / CIO / 3 Anti-Principles for Enterprise IT Decision-Makers

3 Anti-Principles for Enterprise IT Decision-Makers

As a career technologist working for a tier one bank, CIO Hussein Badakhchani has had time to think about what makes a great IT decision-maker. Writing for The Enterprisers Project, he divulges three IT decision-making anti-principles by first redefining the word “computer:”

To fail to explicitly point out that computers automate calculation is to overlook the quintessential nature of these machines and perhaps explains why we still see so much needless manual intervention in their use.

Three CIO Anti-Principles

  1. NoDev
  2. NoOps
  3. NoIT

“If you’re not in the business of IT, stop making IT your business,” summarizes the NoDev anti-principle. The conversion of IT to a commodity, or the consumption of IT as a utility, has been predicted for decades. From this realization, the wise CIO understands that in-house development can and must be avoided in all instances that apply, and that third-party vendors are the best option where products or services exist in their mature form.

Second, regarding the endless meetings where development specialists once hashed out requirements with the operations folks – the capacity forecasts, the ticket writing, the change requests – it all happens on the cloud now. What took hours can now be done in seconds. Every time a process is simplified, it can then be standardized and eventually automated. The drive to maximize productivity (profit) using computers should be accomplished through an ever-expanding culture of automation, says Badakhchani:

To put it another way, when you decide to introduce that shiny new risk tracker, architecture taxonomy repository, knowledge management system, document management system, procurement system, etc, etc, etc,…the team that is introducing this system [must] ensure the highest standards of user experience. The highest standard of user experience for any administrative function is that the user doesn’t experience it at all.

Badakhchani distinguishes between a function and a service. Whereas a function saves the business money by assisting in administrative and bureaucratic activities, a service should be actually saving employees time (hence, increasing productivity). NoIT is the approach that avoids offloading administrative functions on employees in the guise of services.

Read the original article at:

About Eric Anderson

Eric Anderson is a staff writer for CAI's Accelerating IT Success. He is an intern at Computer Aid Inc., pursuing his master's degree in communications at Penn State University.

Check Also

3 Misconceptions to Dispel about AI

AI used to be something exciting and futuristic, but IT organizations have already managed to …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time