Shelfware or Not? The discussion continues…
Part 2 – In this second part of a 2 part article, we will further explore a basic reason that software becomes shelf ware; total cost of ownership.
In this second part of our discussion on software and shelf-ware, we continue expanding on the reasons that the overall cost of a business software project must be in context with the value obtained from solving or easing business issues. If low cost software is selected, purchased (downloaded) and installed the business system will most likely require a list of supplementary tools in the form of spreadsheets, external databases and speciality departmental solutions to complete the implementation.
When a fully integrated solution is procured with its accompanying implementation process and guidance, the expectation that external systems are required should be minimal at best. Most purchasing professionals are more than aware of the concept of ‘total cost of ownership.’ This should not necessarily equate to a need for a large IT department (or any at all) to manage an integrated system. Nor, should it lead the purchaser to assume that new staff will be required to manage the data entry and processing in an integrated package. Unfortunately, this is the conclusion that sometimes can be arrived at when being compared to smaller solutions that can be downloaded at a fraction of the price.
An integrated solution that best supports the way that employees perform most or all of their tasks while executing defined business processes will generally point to a solution that is not niche oriented or incomplete in terms of functional modules. When comparing a low end, low cost software to a more complete integrated solution and the entire project costs are tallied, the total integrated solution will most often yield the best return on the investment.
When there is a realization that low cost software does not offer a total solution, the decision to not move forward and thereby create ‘shelf-ware’ is a simple one. An integrated solution should be purchased with intent and with defined business issues to be addressed. This allows the main drivers for not ending up with shelf-ware to be created. Then, when added to a good support team and a focused internal champion, only the level of success will be left to be determined. We will continue with this series and discuss more about project implementation approaches in upcoming articles.
