3 ways IT causes Shadow IT (and how to fix it)
Suppose your car’s “check engine” light turned on. What do you do? Do you take it to the mechanic and ask him to find the problem? Or do you ask him to remove the light?
Of course, you fix the problem. Everybody knows the light isn’t the problem–it’s a sign of a larger problem.
I mention this example because it ties in nicely to the growing “Shadow IT” problem. For those unfamiliar with the issue, Shadow IT is the term used to describe IT systems and solutions built within an organization without the IT department’s knowledge or approval. The IT department cannot control these systems, which creates all types of data security problems.
CIOs and IT managers around the world are asking the same question: How can we stop Shadow IT? I’ve seen some companies try threats. Others try to limit procurement budgets. Unfortunately, these types of approaches rarely work.
Why? As it turns out, they’re asking the wrong question. Asking “How can we stop Shadow IT” is the equivalent of asking a mechanic to remove your “check engine” light.
Why? Shadow IT is not the problem. Like a “check engine” light, Shadow IT is a sign of much larger problems. When business users aren’t satisfied with the services and support they receive from IT, they look for other solutions. Users aren’t maliciously trying to harm the company. They just aren’t getting what they need from the IT department.
So, if you want to fix the problem, you must first identify what’s causing the problem. Rather than asking “How can we stop Shadow IT?”, perhaps IT departments should be asking, “How are we causing Shadow IT?” Why would end users want to bypass the IT department in the first place? To help identify the problem, I’ve created a short list of the most common ways IT departments unwittingly create Shadow IT: …