A new year is upon us and with that, the word “resolution” comes to mind…
res-o-l-u-tion – [rez-uh-loo-shun n] - noun
1. a resolve or determination: to make a firm resolution to do something.
2. the act of resolving or determining upon an action or course of action, method, procedure, etc.
3. the mental state or quality of being resolved or resolute; firmness of purpose.
4. the act or process of resolving or separating into constituent or elementary parts.
5. the resulting state.
6. a solution, accommodation, or settling of a problem, controversy, etc.
7. reduction to a simpler form; conversion.
Taken from: Dictionary.com Unabridged (v 1.1)
Based on the Random House Unabridged Dictionary, © Random House, Inc. 2006.
“Well, there’s always next year…”
Some people call this time of year the “holiday season.” Others just call it winter. And then there are those of us who call it the “end-of-the-year-crunch”—that special time when it seems there are far too many things to do, and way too little time to get any of them done. Some things just can’t wait, like putting the snow tires on your car before the first big blizzard (too late now, for people in most parts of Canada). Other things can get put off indefinitely, even when you know they have to be done—whether for deadline or not.
One of those things that can get put off indefinitely just might be your enterprise’s software selection project.
You’ve already obtained executive approval for the acquisition of a new XYZ software solution. Maybe a projected deadline has even been set for its implementation. And you’ve recently found out that you’re the lucky chump delegated to take charge of what can often be a rather complex and time-consuming task.
But you have your usual responsibilities, so this software selection thing… well, there’s always next year to get a start on it…
Well it shouldn’t come as a surprise to you, but next year is mere days away. Before you know it, you’ll be standing at a party, counting down the minutes to midnight, champagne in hand trying to mumble your way through “Auld Lang Syne.”
So maybe you’d better start making your Software Selection Resolution list now (and maybe even check it twice) so that you’ll be ready to set the process in motion the minute you sit back down at your desk on January 2nd, hangover remedy in hand, to start your software selection process.
Software Selection Resolution # 1
I promise to gather and prioritize my requirements, and to create a working document that defines all of my requirements.
Imagine it: sitting down to create an extensive spreadsheet that you send around to every department, imploring the employees to define exactly what they need from a software solution. And imagine waiting for all of them to send those lists back to you, so you can cross-check and collate those requirements to avoid any duplication.
Or, you could save yourself some time and use a request for proposal (RFP) template. An RFP template lists hundreds of criteria for each type of software solution; RFPs are often sent to vendors later on in the software selection process, in order to elicit from the vendors which features and functionality their solutions support. But you can use an RFP like a checklist, making quick note of the functionalities you require, and even rating how important each is to your business activities.
Software Selection Resolution # 2
I promise to research all possible solutions, identify those that are relevant to my enterprise and industry, and eliminate those that are unsuitable, in order to create my long list of possible solutions.
The Internet is a great research resource. But there’s so much information out there, it’s sometimes hard to know where to begin—and how to sort out the reputable from the not-so sound. And when it comes to making a decision that involves a major financial investment, you need to ensure your information is irrefutable, up-to-date, and unbiased.
To start your research, browse through some white papers and case studies published by the software vendors themselves. This can be a great way to compile information about different solutions, and can form the basis of an effective comparison.
But, you probably won’t have tons of time to read a legion of white papers. So, how can you cut to the chase? Are there any resources available with ready-made comparisons of software solutions?
As a matter of fact, Software Evaluation Reports are a good way to get comparative reviews of several vendors’ software products. Software Evaluation Reports consist of two or more vendors compared side by side to demonstrate whether or not they support each criterion in a list of available functionalities. (Sample evaluation reports, with two vendors and up to 50 criteria, are available as free downloads.)
Once you have done these things, you will have a long list of potential vendors.
Software Selection Resolution # 3
I swear that I will, in timely fashion, send a request for information (RFI) to all the vendors on my long list (and I swear that I will be patient in waiting for their responses).
What more needs to be said, really? Unless, of course, you don’t know why you’re sending RFIs to your long-listed vendors… (Here’s a hint: this gives them the opportunity to confirm that they do indeed support your prioritized criteria, and how well they do so. All of which is the first part in the process of creating your short list of vendors and solutions. (But more on that shortly.)
Software Selection Resolution # 4
I hereby vow to build a decision matrix…and to dutifully rate each solution against the requirements of my organization.
A decision matrix is a decision support tool that uses algorithms to examine a set of metrics, in order to create a quantified comparison. A decision matrix provides a score based on an evaluative comparison of each prioritized criterion. Doing this will help you to more quickly determine your list of potential solutions.
(Imagine if Santa used a decision matrix to decide who’d been naughty or nice. Or if your boss used one to determine your performance on such tasks as, oh, choosing a new software solution.)
Software Selection Resolution # 5
I pledge to analyze the strengths and weaknesses of each solution, so that I will be able to rank them and create my short list.
This step is essentially an extension of Software Resolution # 4. Once you determine that the selected vendors’ products do support your criteria, you need to know to how well each one meets your requirements, according to your established priorities.
Doing all of the above steps can take a lot of time and effort. You could spend the entire week between the 24th and the 31st going through spreadsheets. Or, you could set aside twenty minutes of the last day of the year to perform the same effective comparison. Find out how easy it can be to create your shortlist with TEC’s eBestMatch decision support system.
Software Selection Resolution # 6
Furthermore, I promise to let all rejected vendors down easy, so as not to upset their sensitive little hearts.
And even if their hearts are lumps of coal that even the Grinch wouldn’t touch with a ten-foot chimney brush, it’s still good business sense to be diplomatic and professional. You never know when you might require a vendor’s services in the future (or meet them in an awkward social setting). So don’t assume they’ll be pleased as spiked punch if you figure that not sending them any response is adequate rejection. If you don’t call—or, better yet, send an official letter—to tell them why they didn’t make the cut, they’ll probably call you. And it won’t be to chat about what a nice holiday you had.
In spite of your diplomatic and professional approach, it is possible that disputes will arise. The vendors’ sales representatives may try to give you a slew of reasons why you should reconsider their products. In order to make it clear that your decision is final, you should specify why their solutions were rejected (without actually using that word), while not coming across as overly critical of their products.
Software Selection Resolution # 7
I agree to undertake the responsibility to issue a request for proposal (RFP) to all short-listed vendors.
On your company’s formal business letterhead, write a cover letter inviting the vendor to submit a proposal. Your RFP should define the entire project’s requirements, and allow the vendor to propose a number of things: contractual terms, technical specifications, delivery terms, time frame and strategy for implementation, training services, support, and of course… the price quote.
Preparing a proposal can be a lengthy process. So, you should give your short-listed vendors some time to complete and return the RFPs (two to three weeks is generally enough—about the same amount of time it takes most people to start smoking again, or let the stationary bike start collecting dust). And you should probably wait until you have received all the vendor proposals before going ahead with the next step of the process.
Software Selection Resolution # 8
I declare that I will create a comprehensive demo script according to my specifications, and then invite my short-listed vendors onsite to show them my enterprise’s current system, as well as provide them with the opportunity to do a demonstration of their solutions.
A scripted demonstration is an essential part of the software selection process. (A software selection without a scripted demo is like a New Year’s Eve party without the stupid hats, noise-makers, and cheap champagne). By providing vendors with your own demo script, you can more clearly see how the vendors’ solutions address the factors that are important to you. Your scripted demo should cover: supplier introduction, system overview, menus and features, system navigation, customization capabilities, security features, and more.
Software Selection Resolution #9
And I attest that I will rate the vendor’s demos, assemble their RFP proposals for consideration, and revisit the analysis steps, in order to select the one and only solution that best fits my enterprise’s needs.
Not knowing how to assess vendor demos is kind of like Santa not knowing why a child is naughty versus nice—which makes the whole idea of rewarding good behavior—good demos—moot.
Each member of your project team attending the demo should participate in scoring the scripted vendor performances. Break down the demos into different sections in order to facilitate the scoring process. You might consider the solution’s functionality or performance, ease of use, process and flow, flexibility, and adherence to your script. Score each section using a rating scale (you can decide how precise you want the scale to be, but “0” to indicate that the factor was not presented in the demo, and “3” to indicate an excellent performance or capability—with according values for “1” and “2”—should suffice).
And then, you also need to know how to rate the RFPs responses. Keep in mind that although these responses can tell you a lot about the vendors, the RFPs are essential sales pitches, designed to persuade you to buy the vendors’ products. Ask your self the following questions:
Vendors should also provide you with the contact information for a few references, from organizations that previously installed the software and can answer questions about the quality of the vendor’s implementation services, ongoing maintenance support, and the quality of the training provided. Compile a list of these questions and send each referee a copy. When these questionnaires are returned, you can use them to help you further weed out the unsuitable candidates.
And now you’re ready to go back to the analysis steps discussed above, in order to take your short list of vendors down to the one single vendor that best fits your needs. (Just a reminder of the things you should revisit in order to determine your best match:
Software Selection Resolution #10
And finally, I swear to prepare for the full implementation process, so that the new software solution I have so carefully selected does exactly what my enterprise needs it to do.
How extensive your implementation is may depend on whether or not you specified in your selection criteria that the solution should fit with your existing hardware. If so, then you can move straight into the installation phase of implementation. To begin with, the vendor should test and refine the application.
You have now arrived at one of the most important parts of the implementation: educating users and administrators. This involves not only the usual training; the training team must also provide a complete explanation of how the solution will affect business processes, what people’s new roles will be, and all other aspects of the new system that may cause users to resist acceptance. Training is the crucial ice-breaker that can make the difference between reticent and enthusiastic software users.
After further tests, to ensure that users are “on board” with the new system, the system is ready to “go live.” But the implementation doesn’t stop there. In order to make the most of the new software application, you must manage and measure how it is benefiting your enterprise, and keep in mind that continuous business alignments are necessary in order for you to make the most of the solution’s potential.
If you want to ensure the vendor adheres to the stipulations for implementation as agreed to in the contract, you can hire a consulting firm, such as Technology Evaluation Centers (TEC), to conduct an implementation overview. Learn more about TEC’s evaluation and selection solutions.
And there you have it! You’ve just resolved to do the most effective software selection process ever! Now, you can sit back and breathe a little bit easier over the holidays (so long as you clean out your chimney, and remember to open the flue before lighting a fire, and don’t catch a cold).
But before you get all weepy-eyed that all the fun of learning about software selection is over, here are a few more resources to help you, just to make sure nothing is overlooked:
Good luck and happy holidays!
This is the best advice on software selection. It would be nice if you included some website links to some of the white papers and case studies. Others very insightful article.
Thanks, Sybil. Glad it was helpful.
The link to the white papers and case studies (in Software Selection Resolutions 2) is there, and active. But I do have to offer my apologies that the text isn’t blue, as it is for other links in other sections–I’m sort of new at manual html coding. I’ll try to fix it ASAP. Meantime, just roll over and click on the words “white papers and case studies” and it should bring you to the right place. (But please let me know if it doesn’t!)
I am unable to open doc file. Help
Install free peactree software