TAG | Precise
Over the years working in the field of IT I’ve seen many products come and go. Some weren’t all that good in the first place, while others were very promising but ultimately failed to deliver on expectations. When I was working in the large enterprise world, we (those of us who cared) compared notes on what small companies were ripe for takeover and which of the much bigger software companies would buy and ultimately ruin their product. Basically we were betting that some software giant (usually companies with 2 or 3 letter acronyms) would buy a useful product and kill it over time.
How Do You Kill Software?
What do I mean by “kill it”? It’s not like software is a living, aware entity (yet). Here is what it means to me to “kill” a software product:
- Let it stagnate so that it falls behind the times and becomes outdated
- “Integrate” it with your other products in a loose (i.e. crappy) way such that it is a pain to configure and provides little value anyway
- Ignore the needs (new features and functionality) of the majority of your customers and focus solely on the needs of a few large customers who spend the most money and scream the loudest
- Provide poor customer service after the sale (slow response to issues, unresolved support calls, etc…)
Time to take a trip down memory lane…
- Remember Cyanea? They were founded in 2001, bought by IBM and rename ITCam in 2004. Currently a high ranking member of my “Promising Tools that Went Nowhere” list. Thanks IBM!
- And who can forget Mercury and HPs brutalization of Performant Diagnostics? So very young. So very sad.
- Then there was the absolutely horrific beat down of Precise i3. Precise was bought by Veritas, who was then bought by Symantec. Then when Symantec had brought i3 to the brink of death they sold it to a VC company which brought back the Precise name but did little to revive i3. Another promising tool ruined.
There have been other similar acquisitions in the past few years and only time will tell if the trend of large companies snuffing out promising tools will continue. You can see a list here.
Why does it always seem to happen? Why can’t a large software vendor keep a product they purchased relevant? I really believe that it is not so much a case of “can’t” as “won’t”. “Can’t” implies that the company is incapable from a technical perspective. “Won’t” has a much worse connotation. “Won’t” is a calculated decision that the company can realize more net profit by selling a product based upon what it once was than by investing and keeping that product current and relevant (more risk). “Won’t” is about putting Wall Street expectations for your next quarter ahead of the needs of your paying customers. “Won’t” seems like a good idea in the short term but ultimately leads to the death of a product in the long term.
I really hope your favorite software products are not in the process of being killed by a giant software company. It’s really a shame to watch it happen over and over again.
When you’re deciding which software products to purchase it is important to understand what type of company you are dealing with. Look at their history, look at their customer satisfaction and Net Promoter scores, ask about their corporate goals and direction. If you choose the wrong company to do business with your new favorite software product might be headed toward an early demise.Link to this post:
Interest in the Application Performance Management (APM) category is very high right now. To stay one step ahead of their clients, the Industry Analysts who cover the category and write research to advise their clients have been very busy. In December alone, there were six different analyst reports being researched by the major analyst firms.
Forrester published the results of their research in the 2nd week of December with the report: Market Overview: Application Performance Management, Q4 2011. Forrester clients can access the report at www.forrester.com. In this report, Forrester provides very sound advice on why APM exists and what it should do for clients. Forrester has created their own “Reference Model” for APM and evaluated the vendor landscape against those criteria.
Raison d’etre for APM
Forrester VP and Principal Analyst, JP Garbani, gives readers very pragmatic advice on the raison d’etre for APM. Simply put, APM’s job is to:
1) Alert IT to application performance and availability issues before a full-scale outage occurs
2) Isolate or pinpoint the problem source
3) Provide deep-diagnostics to enable IT to determine the root cause
For several years now, JP Garbani has been on the forefront of proclaiming that modern APM solutions should enable IT organizations to manage apps not by gauging the heath of their servers or servlets, but instead by assessing what the customer or end-user cares about most – whether their Business Transaction completes quickly and doesn’t make them wait. He states that this has become even more critical as applications have gotten more distributed and complex.
One of our partners recently outlined a logical framework for evaluating Application Performance Management (APM) vendors to help prospects and customers choose the right APM solution for their needs.
Below is an extract along with a link to the full article:
“We work with a lot of customers helping them with performance and scalability of their mission-critical web applications. One of the common requests we hear, is to have a logical framework around how to evaluate the different commercial Application Performance Management products in the market. We have a very easy strategy with our tools and partners at codecentric: We are always partner with the best available solution in the market! We have been a partner with Quest Software (PerformaSure, Foglight), then Wily (Introscope) until they were acquired by CA, then dynaTrace and now AppDynamics is our main partner for APM solutions. We have a lot of knowledge on all of these tools and competition and try to be as neutral a possible. With this article I will try to give my view of how to compare APM solutions for production environments and also my view on how some of the available solutions compare.”
Read the full post by Mirko Novakovic at Code-Centric: