Comparing Products is More Than Analyzing Features, Performance and Cost

Posted on Saturday, October 18, 2008


We recently had to choose amongst multiple products one product that would suit our needs for processing a specific XML based business reporting format.

We shortlisted 2 products and started comparing them by implementing a prrof of concept in both of them. We analysed them on the basis of

1) Ease of use

2) Feature support

3) Support from the product team

4) Performance of tools

5) Cost

6) Integration with existing applications and products

So where did we make a mistake …

We selected one tool over the other on the basis of this. What we missed out in the final selection was the number of people working on and supporting the product. This becomes even more important when this product needs to be working in an enterprise environment with scores of applications. As the case may be the product that we selected was supported and being actively developed by one person. So imagine this if this person goes on a vacation so does your product support. You are at the receiving end of the moods and speed to address issues by this one person.

Again the product fared relatively better than others in the comparison that we did and the suppport that we received during the POC was amazing but at the end of the day if you are selecting a product which is being supported by one person or may be a small team then you are putting your enterprise at a bigger risk.

Consider the product team before making the final selection.