An often overlooked reporting methodology in SAM is to track lost savings. Why this could be important?
- Reporting on missed savings opportunities enables organizations to implement corrective measures and enhance efficiency.
- Highlighting areas for improvement fosters a culture of continuous optimization within the company.
- By pinpointing where potential savings were overlooked can help to review accountability and authority questions.
- These insights serve as valuable feedback loops, guiding strategic decisions and resource allocation for future software asset management endeavors.
- Could raise the level of stakeholder buy-in to gain higher authority of SAM for fostering change to optimize costs.
- Revealing lost cost savings emphasizes the critical role of software asset managers in driving financial accountability and optimization efforts.
- Providing detailed reports on missed savings opportunities enables informed decision-making at both tactical and strategic levels within the organization.
- By quantifying the impact of overlooked savings, software asset managers advocate for resource allocation alignment with business objectives.
- Their analysis serves as a catalyst for proactive measures to prevent future revenue leakage and maximize returns on software investments.
What do you think are good example for reporting lost savings?
e.g.
-
The most obvious is to invest into SAM tool for transparency on cost savings potentials. If you only save 3% with a SAM tool in a 3 year business case from the overall software budget, how much it would be?
-
Implement use-or-loose policy for Autodesk licenses? Do you suspect that you would save 5% to 15%, however the service owner does not like the idea? How much savings would that generate in 3 years?