Software and apps exist in the workplace to enable employees to get their jobs done, and they should inherently make their day-to-day easier. However, there is a fine line between helpful applications and having too much software that feels burdensome to employees and finding that limit falls on IT leaders. Reducing IT budgets is a priority for most teams as fears of a recession continue, and a simple, yet vastly overlooked method to reduce spend and redundancies is becoming more vigilant of your actual software license usage.
Recent research suggests that many organizations are paying for more software than they need. If organizations are looking to reduce IT spend, leaders should take a closer look at the tools being offered to employees, as not all software is essential.
Half of Purchased Software Goes Unused by Employees
50% of software licenses go unused by employees. This is a shocking realization for the leaders who pay for these tools to improve efficiency and overall quality of work.
Generally, the most unused licenses fall under Business Information and Integrated Development Environment categories, which include apps like Tableau and PyCharm. These platforms are most often seen as redundancies of tools from juggernaut providers like Microsoft or Slack, or they serve such a niche purpose that often do not see the use that justifies the cost.
How did this happen, and why isn't employee application usage more obvious to IT teams?
A staggering 5% of IT leaders claim to have "complete visibility" of the total number of software licenses being used by their employees. Lack of visibility from leadership has created an environment of increased waste and confusion among employees on the tools they should be using and when, and it prevents IT teams from asking the right questions to understand what is going on. For example, 37% of employees use three browser applications to access their SaaS tools and the internet.
What benefit does this insight offer IT Pros? It allows them to think more about why — are there certain browsers that work best with specific SaaS tools?
Should IT teams be recommending one browser for all employees?
Do employees even know why they have all these browsers together?
These are all important questions that IT teams wouldn't think to ask without software insight which can drive long-term value and workflow efficiency. Job number one of a software delivery team should be provisioning, and job number two should be reclamation.
Staying Vigilant is Still Key to Preventing Software Waste
As vigilance is the linchpin to reducing software waste, there are several steps IT teams must take to ensure they are seeing everything they should. Step one is conducting audits of software usage, ideally before negotiating agreements with vendors. Leaders will be able to find key usage attributes for the applications deployed in their enterprise, primarily the licenses that go unused, those that are used very little, and those used regularly.
While vendors attempt to sell a full suite of tools, it is important for IT to enter into negotiations with the knowledge of which licenses are or aren't bringing value to ensure they only pay for what is truly needed. The only way to do so is by asking the right questions.
While audits show IT leaders what they are missing visually, they usually focus only on provisioning vs purchased licenses to find the gap. However, internal routine analysis of usage will allow for teams to elaborate on that knowledge and put it to use in their organizations. While one-time data in an audit is helpful, as software licenses are updated and employees come and go from the company, the apps that are used and are providing value can always change depending on user preferences, business needs, and new options that become available. IT leaders must foster open communication with the business and employees they support to know what works best for them — there is no one-size-fits-all approach to building a software mix.
Scaling software usage for an organization requires a level of persona building — creating profile for specific job functions and departments to understand the employees that need specific software. And that persona should be dynamic, changing with user and business habits and needs.
For example, some in the marketing team may need Trello (one of the most underused applications in the recent survey) to stay on track with deliverables, while others in marketing may never need it. Relying purely on numbers would indicate to an IT team that because Trello is used in marketing, that they all need it. But in analyzing usage and in conversations with employees, they would realize that a specific segment of the organization desperately needs it while others can be removed. Rather than paying for company-wide licenses or canceling licenses completely, the IT team is now able to scale purchasing based on the area of greatest need while still driving cost savings. In leveraging both qualitative and quantitative data from employees, leaders can build the right package of software for each team member, while also reducing waste.
What Next?
While software waste should be a primary concern for IT leaders, it is an opportunity for cost optimization. As a recession looms and the C-Suite possibly considers difficult decisions to reduce spending, IT teams can offer data on a key area of waste that can potentially save organizations millions. With increased vigilance and a more personalized touch, businesses will be able to have a full understanding of how their employees prefer to work, where there is room for improvement, and where costs can be more optimized.
Through a more hands-on approach, leaders can reduce both costs and confusion alike as they create a more streamlined and synergistic experience. However, the decision to act on this ultimately falls on IT leaders and C-Suite members to look within and find where they can reduce waste.
