Mailbag: What should the success criteria be for a SAM project?
If you create a generic list, you’ll get a generic outcome. You’ll be shooting at success criteria that are potentially not business aligned and without the critical senior management support or budget required for success.
Success criteria should be business and IT department aligned.
The question of picking success criteria is a variation on a common theme around “What should I measure?” or “What metrics should I track?”.
From the start, you should measure your progression towards your business plan. You do have a business plan, right? That plan that was signed off and understood at senior management level which led to your team being well supported, funded and resourced.
If not – go and create a plan and measure your success against it.
In light of tough market conditions and our organisations mandate of cost saving and efficiency gains, the ITAM function will focus on removing software and maintenance waste without impacting service levels, and support the IT department’s goal of helping users help themselves etc….
The first was copied and pasted from Wikipedia, the second was formed by listening to the current focus of the company / market conditions and current focus of IT. Which one do you think is more likely to be listened to by busy executives with an endless list of priorities biting at them?
If you need some inspiration in terms of what elements of ITAM might help your company and it’s goals check out this article from 2016: Quick guide to building a three-year roadmap. Also see ITAM Metrics.
Finally, success criteria for a SAM project is not implementation of SAM technology.
Installing agents, installing software, connecting integrations, loading systems full of procurement data are all milestones but not success criteria. The success of a SAM tool should be judged based on the ability to deliver business outcomes. For example, I would consider a SAM tool successfully implemented if you are able to deliver a Microsoft ELP and maintain it on an ongoing basis.
I hope this helps – I would value the opinions of others on this, please leave a comment below.
I’m concerned about the terminology “SAM project”. Unless the questioner is referring to a short-term compliance project, SAM should be thought of as an ongoing business process covering the entire software lifecycle, not an event.