In the IT world, we tend to view end users as an occupational hazard—a perilous yet inescapable part of our jobs. After all, it seems employees will install just about any application they can get their hands on without regard for the potential licensing implications, compatibility issues, security holes, or bandwidth consumption. But who can blame them? They’re trying to do their jobs just like we all are, but without the benefit (or curse) of understanding the potential implications of their actions.
What we rarely acknowledge is that the onus is on IT leaders to ensure workers have the information they need—and are held accountable—to make good decisions. It all begins with a clearly articulated and effectively communicated software usage policy that educates end users about the importance of complying with a set of basic standards. Such a policy shouldn’t be long and infused with technical mumbo jumbo. In fact, the shorter and more straightforward the guidelines, the greater likelihood it will be read, understood, and, most importantly, adhered to. Not only can a properly developed software usage policy serve to curb risky behavior, but it will also generate goodwill among software publishers when and if they decide to audit you. If a vendor sees your organization making a conscientious effort to prevent the use of unlicensed software, they’re more likely to treat you as a partner rather than a criminal throughout the software audit process.
The nature of your software usage policy will (and should) depend on your organization’s size, geographic dispersion, and diversity of your software estate, as well as the sophistication of your end users and their technology needs. If you run the IT department of a small community college, for example, you may wish to prohibit anyone but the IT staff from purchasing or installing software on school-maintained systems. On the other hand, if you work for a technology company with software developers that rely on a variety of commercial and open source solutions to do their jobs, you may need to build more latitude into your usage policy.
(more…)