What does the future hold for search in law firms? How far will legal knowledge management push the search envelope beyond documents, matters and expertise? Further than you think! Let’s explore the future of search, including integrating search-enabled applications, broadening the search scope available to the mobile professional, incorporating artificial intelligence, enhanced visualization and the use of predictive analytics, and the use of machine-generated metadata to improve search results. See how search can fulfill its promise of making your lawyers more effective and firm-client relationships more collaborative.
Identify possible search functions
Visualize the future of search in your law firm
Learn how you can prepare for the future of search
Hear Case Studies from two law firms to improve search
- Doug Freeman, Knowledge Systems Manager, White & Case
- Peter Wallqvist, VP of Strategy, iManage/RAVN
- Todd J. Friedlich, Senior Manager of KM Technology and Innovation, Ropes & Gray
- Glenn LaForce, VP of Knowledge Management, Aderant
[These are my notes from the International Legal Technology Association’s 2017 Conference. I’m publishing them as soon as possible after the end of a session, so they may contain the occasional typographical or grammatical error. Please excuse those. To the extent I’ve made any editorial comments, I’ve shown those in brackets.]
- Drive User Adoption.
- Maximize points of contact — Don’t put search under a separate tab. Instead, put a search box on every page of the intranet, on the laptop, on their desktop, on their Citrix desktop
- Reduce user “click” – Enable type ahead so users don’t have to type too much
- Understand Adoption Stats — look at content usage (are the lawyers looking for legal documents or specific tools?). Plus tie in other data sources. For example, combine financial stats with your user stats to see if there is a correlation between high users and profitability.
- User adoption — is the “document” the primary container of knowledge? Lawyers and professionals don’t think only in “documents”. There are other containers of knowledge that are natural for users. So deconstruct documents into their constituent parts, such as clauses. Focus first on the business problem they are trying to solve in their search.
- Provide an Intuitive Search Experience.
- On the web, search seems intuitive. Unfortunately, it is too often a completely different experience inside the enterprise.
- To improve the search experience, move from keyword counts to contextual understanding to determine relevance. Google did this by using hyperlinks to validate relevance. Because you may not have hyperlinks within the firm, you will need to bring other internal and external data to bear. (White & Case uses internal and external (from vendors) data to help determine relevance.)
- Make it easier to find your content by increasing the refinement options beyond those provided by the system that is the source of your data. Ropes & Gray merges data from a variety of sources to provide more ways to refine/filter their search results.
- Leverage search intent to provide customized refinement options/weighted results. For example, increase the weight of rankings based on the identity of the searcher.
- Provide a More Complete Set of Information.
- How to bring in more external sources to augment search results? Earlier, the only way was to use federated search. Then some external vendors (e.g., Practical Law Company) allowed firms to index PLC content, which drove much higher levels of PLC use. Now some external data sources are allowing firms to index on premises subsets of their vendor content (e.g., treatises).
- When bringing in vendor data, also bring in snippets that allow the user to preview the content.
- These techniques really drive higher levels of usage of vendor content.
- Lowering the Cost of Custom Search-Based Applications.
- A search platform is in the unique position of being a universal portal/repository of information. It can show data from disparate systems in a single interface.
- New search systems should have a flexible API to enable creative uses of their search tool.
- As vendors provide more flexible APIs, it will be possible to combine/recombine those APIs without a developer
- Ropes & Gray is prototyping tools for non-developers/power users:
- Data Dictionary and Custom Aggregation Tool to allow joining of data by end/power users
- RAD tools such as SharePoint/ Nintext so power users can create workflow-enabled, dynamic forms to power search.
- The more you can lowering these barriers, the more you lower the cost of development by enabling work by non-developers.
- Trends for the Next Five Years.
- Chat bots — for example, Do Not Pay is a chat bot for fighting tickets. It guides the user through a process online. Can we extend this to other operations? It allows the computer to figure out what you are looking for and then deliver it to you. It allows you to “go on a journey” just like you do when you speak with a person.
- Cloud — if you have applications in the cloud, how can you access and index them efficiently in your on prem system? But going beyond this, should search be a cloud service? (Where the document is on prem but its text is “represented” and indexed/searched in the cloud.)
- Search will have to “follow the data” where it lives. Then we will need appropriate policies/governance so clients are confident about security and confidentiality.
- One day, clients may ask to search their documents on your system by using your index.
- Time and Billing — use AI to determine key characteristics of time records, then use those results to enrich search. In the next five years, there will be a convergence between AI and search.
- Security and Rights Management.
- This has been a perennial challenge for search.
- A proper enterprise search engine should respect your security rules. But the humans in charge need to specify those security rules for the search engine.
- GDPR is an incredibly onerous data protection law that is coming into force in Europe. Now it is a criminal offense to expose data that should not be accessible. On the other hand, a properly-implemented search engine that respects security rules should help address this problem.
- When a firm is required to lock content down on a need-to-know basis, you can still derive value from search because sometimes the metadata exposed by the search engine is as important (or more important) that the underlying hidden document.