Skip to main content

Select the worst product in the Short List

The title of the post summarize the bottom line of my recommendation to a customer. 

The Short List included three software products. Two of the products were owned by the same vendor.
Let call the best product product A, the worst product product C and the third product product B.


Why I recommended not to select the best product?

In my opinion, product A was better than the other two technically and conceptually.
However, the same vendor was selling product B as well.

Due to overlapping products in companies acquired by the vendor he owned two competing products.

The key question was: Which product is the vendor's strategic product?
My answer to this question was: product B is the strategic product.

My customer was buying a significant product for Long Term. For the long term, the vendor will invest in Research and Development in product B. 
He will invest as less as he can in product A. The support to this product's customers will be minimal. 

Vendors do not tell you that one product is strategic and the other is maintenance fees engine. 
The vendor told me both products are strategic.
I had reasons to believe that product B was the strategic products.

A friend of mine working in the IT Department of a large US based company, confirmed my opinion.

The company he worked for was probably one of the largest customers using product A.

According to my friend, the maintenance service was not good. No solutions for bugs were provided for long time.

The Bottom Line for product A:
Expect minimal future product development and low quality maintenance service. Do not select product A. 

Comparing Products B and C

Product B's vendor was a large global vendor, who develops, maintain and sells variety of software products. 

Product C's vendor was a lot larger. He has producing maintaining and selling many software and hardware products.

It is not the size that matters: Product C's vendor actually owned the Proprietary Platform the selected product should be deployed on.

This vendor was the leading hardware provider, the only Operating Systems provider for that hardware, The leading Integrated Development Environment (IDE) provider and the leading Database provider.

Many Customers prefer buying all strategic software from a single vendor and not Best of Breed approach. Product C's market share was higher than product B's market share.   

The product selected should interface with Infrastructure Software products. 
My prediction that for the Long Term product C will integrate better with other products built by the same vendor than product B built by another vendor, was gradually confirmed.

Historical perspective also supported selection of product C.
Five years before my customer selected a product, product C's functionality was very limited and the number of its bugs resembled the number of holes in a Swiss cheese. 

During the five years until the selection process took place the gap between product B and product C was systematically narrowed.

The Bottom Line: 
In the Long Term product C will be better than Product B and probably will dominate the market. Product C should be selected and implemented despite its functional and conceptual inferiority in comparison to product B.

After ten years

More than ten years after my recommendation it is quite sure that my recommendation was correct.

Product C's enhanced integration with the Operating System and the de facto standard Database is a huge advantage.
Product C's functionality and features are broader than product B's functionality and features.

There were no new product B's customers and many users included in its installed base migrated to product C.

   
  


  



Comments

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...