Legacy search tools failing. My colleague Ken O’Reilly completed TSIA’s first “knowledge management practices” survey in December, and the results will be published in the next couple of weeks. I shared a couple of proof points in the webinar today to illustrate how existing KM implementations aren’t keeping up. The lion’s share of respondents to the survey have had both their customer-facing and employee-facing KM platforms in place for 4 or more years, which should indicate they are mature, highly adopted, and delivering value. But, when asked to rate their current KM implementations, the largest percent of respondents indicated the worst option: “Needs a lot of work.” So why are these mature implementations failing? In my experience, inadequate search is often at the root of the problem. Legacy search tools don’t do well outside a proprietary knowledgebase, and according to my annual tech survey, SharePoint is now the top installed knowledgebase tool used by service organizations. Not a specialized tool built for support knowledge, a generic content warehouse. With customers and employees now expecting to search content anywhere in the enterprise, in any format, requirements for search have evolved dramatically. Today, companies need a search tool that provides context, intelligence, dynamic taxonomies, and multiple filtering options.