Category: Semantic technologies (Page 39 of 72)

My last blog was in reaction to two recent vendor experiences. One had just briefed me on an enterprise search offering; the other had been ignoring my client’s efforts to get software support, training and respond to bug reports. The second blogged a reaction with a patronizing: “So Lynda should not feel too bad. I know its (sic) frustrating to deal with vendors but not all vendors are the same and she certainly hasn’t tried us all.”

With dozens of vendors offering search tools, it was fair to assume that I haven’t tried them all. However, having used search engines of all types since 1974 both as a researcher and analyst I have a pretty good sense of what’s out there. Having evaluated products for clients, and for embedded use in products I brought to market for over 20 years, it doesn’t take me long with a new product to figure out where the problems are. I also talk to a lot of vendors, search users, and read more reports and evaluations than I can count. The evidence about any one product’s strengths and weaknesses piles up pretty quickly. “Searching” for stuff about search has been my career and I do make it my business to keep score on products.

I’m going to continue to hold my counsel on naming different search tools that I’ve experienced for the time being. Instead, in this blog I’ll focus on keeping buyers informed about search technologies in general. My work as a consultant is about helping specific clients look at the best and most appropriate options for the search problems they are trying to solve and to help guide their selection process. Here is some quick generic guidance on making your first search tool choice:

• If you have not previously deployed an enterprise search solution in your domain for the corpus of content you plan to search, do not begin with the highest priced licenses. They are often also the most costly and lengthy implementations and it will take many months to know if a solution will work for you over the long haul.
• Do begin with one or more low cost solutions to learn about search, search product administration, and search engine tuning. This helps you discover what issues and problems are likely to arise, and it will inform you about what to expect (or want) in a more sophisticated solution. You may even discover that a lower cost solution will do just fine for the intended application.
• Do execute hundreds of searches yourself on a corpus of content with which you are very familiar. You want to learn if you can actually find all the content you know is there, and how the results are returned and displayed.
• Do have a variety of types of potential searchers test-drive the installed product over a period of time, review the search logs to get a sense of how they approach searching; then debrief them about their experiences, and whether their search expectations were met.

It is highly unlikely that the first enterprise search product you procure will be the best and final choice. Experience will give you a much better handle on the next selection. It is certainly true that not all vendors or products are the same but you need to do serious reality-based evaluations to learn your most important differentiators.

I received an unsolicited email from jetBlue yesterday, one of many that I routinely receive from various travel providers. This one was different. I was not one of the thousands stranded by them last week and I have only traveled on jetBlue for one trip. They could have omitted this mea culpa letter to me in hopes that I had not already noticed all the media hype around their operational breakdowns and plans to recover from a faulty infrastructure. However, by calling attention to their lapses in such public ways this week, they have insured that I will include them in future travel planning.

Years ago as the President of a software company, I received a truly disturbing email lashing from a client sent after 6 PM on a Friday. The accusations about my company’s service were vitriolic and uncharacteristic of client reactions. I stayed at the office late gathering all the information I could find from the customer support database to learn what might have precipitated the outburst because I wanted to send a thoughtful, accurate and timely response. Without attacking the client I sent a chronology of inquiries and responses with a copy of a remedy sent to them weeks earlier. Then I went home with hopes that Monday would bring a more constructive dialog between the client and my company. The issues were amicably resolved, the client remained a good client, gave us high marks in referrals, and the matter was never mentioned again.

Unfortunately, personalization of client vendor relationships is missing in too many business relationships. A great amount of marketing copy appears describing how software tools and search interfaces support “personalization.” We know that SaS (software as service) or ASP (application service provider) models have come into their own. We also see the major search software vendors posting record growth and grand projections for even more. What this all adds up to is the convergence of a perfect storm of client disappointment as we experience a total disconnect between what vendors mean by “personalization” and “service,” and what customers want. Customers want software that is intuitively simple to personalize, and service that places the responsibility for software problems squarely with the vendor.

Based on my recent experiences with vendors, I see huge industry problems ahead. These are being exposed at all levels: discussions with sales representatives, exchanges with search company executives, deployment of software issues, documentation and training quality, and exchanges with customer support personnel.
Here is my list of vendor weaknesses:

• Lack of understanding by company representative how their software works
• Failure to really understand prospect needs, environments, and requirements
• Poorly written documentation and training giving no context for how the software might be deployed
• Technically sophisticated features delivered with no coherent path to deployment
• Inability to communicate honestly with clients
• Lack of clarity on what industry standards and terminology mean to clients
• Failure to use their own products by all employees in vendor organizations
• Inattention to building quality support infrastructures to service clients

I am not calling for a “customer bill of rights” for the enterprise search software industry. Instead, I am calling for you who procure software to take control of your own experience by doing a lot more than looking under the hood for technical specifications, features and functionality. You need to:

• Look inside the vendor’s organization to see what kind of personnel it has, what the turnover is, how many people are supporting service functions compared to developers, etc.
• Listen to what you are being told; do serious validating research, on your own, to discover customers using the software. Talk to as many as you find; look at blogs and chat rooms to discover where the pain points and good experiences lie.
• Read documentation to understand how much time, effort, and expertise the deployment and maintenance will really require.
• Test drive products with your own data.

Every search company can’t grow 100% year-over-year for years on end. You will be suffering mightily for a long time if you make a big investment in one of those who ignore the customer experience. There is also a good chance they’ll be sold off to the lowest bidder once they realize their inability to service their clients and remain profitable. Take your destiny in your own hands; take enterprise search on in slow and measured increments so you will know what you are getting into.