After I wrote last month's column on why CIOs don't have more influence with "the business," I participated in a fascinating conversation with a group of big-company IT operations directors that perfectly illustrated how we in IT undermine our own influence.
The discussion turned to rogue IT, with a general consensus that it was pervasive. One estimate, which was not greatly scoffed at, was that rogue IT might constitute 15% of the average large company's IT spending.
But while nearly all of the IT leaders agreed that rogue IT was widespread, they showed little interest in exploring why that was. They didn't want to talk about what might drive line-of-business managers to bypass the IT department. They didn't want to try to understand what the experience of their business partners might be like. They weren't interested in examining whether those partners felt a lack of control, a mistrust of the department or the need for speed. By staying silent on these topics, the group seemed to be dismissing the experiences of business managers as irrelevant excuses for bad behavior.
It was another story when they were asked how to manage the situation. Silent no more, nearly everyone was suddenly spilling over with advice like this:
Threaten the vendors. If vendors take meetings with the line-of-business executives without inviting IT, they should get blacklisted.
Require IT sign-off on purchases. Tell the purchasing department to divert any technology-related requests to IT.
Refuse to integrate. Insist on IT taking control of any systems, data and/or people that need to work with IT-controlled systems.
Of course, IT departments have good reasons for wanting to centralize the control of technology assets; among other things, they want to control costs and ensure that data is kept secure and managed responsibly. But notice the theme in the suggested responses to rogue IT: They all involve exercising coercive power and preventing business managers from doing what they want to do. If these IT managers had been willing to examine the experience of their business partners, they might have realized that while these techniques might control rogue behavior in the short run, the long-term effect will likely be quite the opposite.
These sorts of power moves do nothing to reduce the demand for rogue IT or to address the root causes, which often stem from negative assumptions about the experience of working with the IT department. If anything, they reinforce the beliefs that inspire business managers to go rogue and strengthen their determination to do so, ultimately driving rogue IT further underground.
Controlling attitudes and heavy-handed policies will likely undermine the efforts of CIOs who want to increase IT's influence within the business. No matter how good their personal relationships in the C-suite, their efforts to become influential will be doomed if IT is seen as an obstacle rather than a helper at every level below.
Power is about changing other people's behavior; influence is about changing other people's minds. For IT to become more influential, we must learn to examine, with empathy, the thoughts and experiences of those we want to influence. And then we will have to decide whether we want to be powerful or influential. Ultimately, we need to ask ourselves, "Are we willing to put in the effort it will take to change people's minds?"
Paul Glen, CEO of Leading Geeks, is devoted to clarifying the murky world of human emotion for people who gravitate toward concrete thinking. His newest book is 8 Steps to Restoring Client Trust: A Professional's Guide to Managing Client Conflict. You can contact him at firstname.lastname@example.org.
Read more about management in Computerworld's Management Topic Center.
This story, "Rogue IT, and power as an obstacle to influence" was originally published by Computerworld.