Do you know that?
- “93% of the organizations are wasting piles of money on unused or underused application software, otherwise known as « shelfware ».
- “20% of the organizations reported a loss over 1m$.” (source: Flexera)
In the real life:
CIO: We have the shelfware syndrome! Is it bad, doctor?
Doctor: it could have been worse: it is not vaporware… The shelfware syndrome is common and can be cured.
CIO: what can we do?
Doctor : Shelfware means that you acquired and sometimes installed software, that is not used any more. It is a big loss, but it has been lost already… There is nothing we can do about it: Try to understand where and how you caught it to avoid any relapse in the future.
Do you know that the troubleshooting, visibility, NPM, APM and monitoring are directly impacted by this plague?
Performance Vision pays special attention to making sure the disease does not infect its partners and customers, we thought it would be worth sharing some of that thinking with you!
Top 5 reasons for monitoring tools to end up on a shelf
1- Not used often enough
se case is obsolete and / or is
so unfrequent that your team does not have enough practice to fluently use the solution.
2- Too complex
3- One person business
mostly used by one person (for a niche utilization), beware that in case this person moves on to another role, job or company, there is a huge chance no one will pick up on the administration of the solution soon enough to maintain its use.
4- Focused on one project
purchased for a specific situation (critical issue with a key application roll out, infrastructure migration, merger). In that case, there is a huge risk that once this project has been released… the solution is not used any more.
5- IT pace of change
- They are not fit for next generation infrastructures (e.g. physical appliances in virtual and cloud data centers) and cannot easily be redeployed in these environments.
- They work on configuration that requires many man hours and … should be changed frequently.
- They do not easily scale up (upgrading requires a new integration, changing the complete installation, losing history, etc…)
Best practices: Focus on the later stage of the lifecycle of your solutions
You need to develop a
Vision of how the product will live, benefit to your operations and by whom it will be used day-to-day.
How to Stay safe from shelfware
1- Used by teams / across teams
2- Easy to use – easy on boarding
- What is the effort required for a user / administrator, to learn to use the solution and become efficient in delivering his/her tasks with it? What are the skills required to leverage the solution?
- Do you have to be an expert? Will there always be experts of that field in-house?
- What is the cost of restricting the use of a solution to experts only?
3- Minimize the configuration work required
- Instantly (you get that visibility without any prior action)
- 1-5 minutes
- 1-4 hours
- Several days
4- « Doing the job » is not enough: should make the job easier and minimize workload
in the end abandoned after a long time investment.
5- From a one-off fire-fighting to daily operations
6- Temporary need, use a temporary service
buying a service from a specialized service company rather than investing into something your team will not exploit at its maximum.
7- Vendor’s focus on customer success
how the vendor / integrator will help on making sure the solution is actually delivering ROI.
You should ask questions on how your vendor / integrator can help overcome the challenge of
- How can you help us train newcomers?
- How can you make sure our solution remains aligned to new use cases and new infrastructure / application configurations?
- How much effort will this require? how about costs?
- What pourcentage of your customers renew their maintenance and keep using your solutions?
- What processes have you got in place to maximize this?
- How can I upgrade? revamp the solution for a newer configuration? what are the conditions and costs attached to that?
For every project, we ask ourselves these questions; do not hesitate to engage with us to discuss this further.