8 Ways To Judge Collaboration Technology Vendors
By Jacob Morgan
InformationWeek
Vendors know this, and customers know it too. A common challenge for many companies is how to evaluate the various vendors out there. Too often I hear about companies that choose a vendor only to realize that they picked the wrong one, usually because they never went through a scoring or evaluation process.
I'll discuss the actual evaluation process in an upcoming post, but first let's look at eight variables that all vendors in the enterprise collaboration space compete against. You might want to add other relevant variables to this list, and I strongly encourage you to do so. Your list should make sense for you and your company.
1. Price
The basis for this is simple: How much does the vendor charge for use of its platform?
The two most common ways vendors charge are per seat (user) and per page view. Thus it's important to understand how many users you want to include. Consider this question in a few different timeframes: what it will cost now, in six months, in one year, in two years, and beyond two years.
You don't need to have exact numbers, but it will help you think in terms of cost. Perhaps for the first year, you want to try piloting this concept to a small team of 100 employees. After two years, you might want to roll out the platform to thousands of employees -- this is something you need to consider. Another price factor to consider is whether you can add or remove users without incurring any penalties or altering the cost of each seat purchased.
[ Need to narrow your choices? Read our Enterprise Social Networks: Must-Have Features Guide. ]
2. Features
What exactly can this platform do for you, and what makes it different from the others?
As mentioned, many vendors seem to offer similar feature sets. The best way to determine whether a particular vendor offers the features you need is to develop a set of use cases and then map them to feature requirements. Some vendors offer collaboration solutions specifically for employees, while others support external customer communities. That's why it's important to consider several different timeframes. If you start off working with a vendor that offers only employee collaboration features and then decide you also want to collaborate with employees, you could be forced to work with an additional vendor.
3. People
You want to be sure you're working with a vendor that offers not only a great product but also people who will treat you well. I've referred vendors to several clients in the past, only to find that the vendors were rude or promised things they never delivered. This is not the type of vendor my clients -- or anyone else's clients -- want to work with.
Since the emergent collaboration space is constantly evolving, you're likely going to be growing and learning along with whatever vendor you go with, so it's important to be sure you're on the same page. Ask for references, and ask previous customers what they found easy -- and what was frustrating -- about working together. If the vendor typically works with enterprise clients and you are a small or midsize business, make sure you are treated with the same respect and care as the big enterprise customers.
Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).

Jacob Morgan's The Collaboration Organization is a comprehensive strategy guide on how to use emerging collaboration strategies and technologies to solve business problems in the enterprise. It has been endorsed by the former CIO of the USA, CMO of SAP, CMO of Dell, CEO of TELUS, CEO of Unisys and dozens of other business leaders from around the world.
More by Jacob Morgan
1 |
| To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
InformationWeek Reports
Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.
Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.
Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.
The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.




Subscribe to RSS