Voted Best Answer
Sep 13, 2019 - 02:35 AM
There are many benefits to standardizing your software catalog, but its not always easy shifting an organization from a culture of choice. For Software Asset Managers, standardization makes our lives easier because it narrows the scope of what we need to account for. The first step towards this practice is to get buy-in from leadership, and to do that you'll need to outline the benefits to the rest of the organization.
This blog will spotlight some of those benefits: 6 Reasons Standardizing Your Software is Essential.
Once you've been approved to begin this activity, you will want to create a policy and open a review board made of the appropriate decision makers. Security managers, Usability, IT Support Managers and others should be on this board.
I've also found that surveying the software user base is a good way to choose the frontrunners. You should take those surveys to the review board so that they will know what the community's preferences are.
In your policy, you'll need to have an exception clause. If somebody has a strong preference against the standardized software, or even an accessability limitation you shouldn't force them to use it. In these cases I would allow for a manager approval to allow them their software of choice. If their manager is okay with their use-case, then an exception should be made. I found that a lot of the time, if a user needs to ask for approval, they will settle with the standardized software if there isn't a massive incompatibility with their use case.