Voted Best Answer
Feb 24, 2016 - 01:10 AM
Whether or not we feel the end user needs to know 'why SAM' is (unfortunately to the extent that it adds extra work and cycles to an already-busy SAM manager's life!) largely irrelevant. Without their buy-in and support, the SAM function of today simply can't perform to its optimum. We certainly believe that the future of effective Software Asset Management lies in empowering every end user to play their part in optimizing the cost, availability and productivity of software.
And that means you must communicate WHY the employee should care, WHAT they want to know and HOW to play their part (and indeed, HOW doing so will benefit them directly).
That means teaming up with those in the organization that know the best ways to deliver these messages. We're still just under 500 employees at Snow, but we've appointed our first Internal Communications manager, because we recognise both how important this is but also how it is a special skill.
To expect a SAM team to intuitively know how to communicate with the rest of the organization is perhaps the greatest mistake in this process. Far better, I would suggest, to seek the support of those in your organization who are charged with internal communication. With all the proven benefits that Software Asset Management has to bring (be mindful both that you focus on the positives and that you need to focus on the benefits to the users, rather than the organziation's bottom-line), I would be saddened if any internal communications professionals were not enthused to work with the SAM team to communicate that will ultimately benefit both the organization and the individuals within it.
I'm mindful that I don't want this response to become an essay, but my final point would be to pick up on Martin's "end users will bother to read". A lot of your end users don't "read" much at all these days. That's why video, infographics and other easily-digested communications vehicles are becoming more and more important. My advice: don't limit yourself to just writing a SAM policy or document and then get upset when the users don't read it; embody your SAM goals and requirements in a format your users will engage with and you might be surprised how much more attention you get!