Quoth the RAVN: How iManage’s RAVN Acquisition Will Affect the Legal Market

25 May

By Joshua Fireman and Ron Friedmann, Fireman & Company 

The document management, search and AI spaces have seen accelerated activity and innovation over the past two years. iManage’s acquisition of RAVN, announced May 24, 2017, brings these three streams together. Integrating all three categories into a single product likely will have a significant impact well beyond the deal. We discuss here the potential impact on document management (DM), search and artificial intelligence (AI), and how this new platform approach validates both emerging and maturing trends. For context, we start with an overview of how the market arrived at this point.

A Decade of Change: Trends in Legal Tech

After years of relative inactivity on the vendor side in both search and document management, we now see a generational, if not a once-in-career, shift in the market. Many factors have led to this major point of inflection.

  • Lawyer needs have changed significantly versus a decade ago, with better collaboration, real (not just stated) information governance, more value for clients, mobile work (from anywhere), and cybersecurity.
  • Technology has changed dramatically with the rise of cloud computing, mobile devices and apps, and enterprise-quality open source code.
  • Artificial intelligence needs to be considered separately. The rise of machine learning and other AI creates many opportunities. While the AI hype concerns us, we do see tremendous potential.
  • Client demands have increased. General Counsel want more efficiency, more security, and more transparency in how their outside counsel work. With 1000 people attending the CLOC conference earlier this month, it is clear clients are organizing and improving their game.

Accelerated Market Innovation in DM and Search

Prompted by these changes, we have seen major advances in the two leading providers of document management systems.  As a partner of iManage and NetDocuments, Fireman & Company has extensive experience with both and here is what we see.  NetDocuments, which started as a cloud-based system, has gained significant market share in the last few years as it has upgraded its features, functionality, and back-end architecture. iManage, now back to a stand-alone company with the ability to invest and plan its own future, has invested significantly in developing the next generation of its flagship product.

We have also seen substantial change in the search market. Recommind, long the dominant provider of enterprise search for law firm KM, is rapidly losing market share. Multiple new or newly improved options now vie for mind and market share. We see that most firms buying or replacing existing search installation are looking at Handshake Universal Search and RAVN (again, Fireman & Company partners with both). But other choices are available, including the industrial-strength Sinequa.

The Acquisition’s Impact on DM, Search and AI

So, with all the changes, what should we make of iManage’s acquisition of RAVN? As noted above, this is a bold move. It brings together DM, search and AI in ways that may that well affect all three. What this means for law firms, both those comfortable with their current tech stack and those evaluating significant changes, is important to consider:

Document Management

Foundational Platform. Both iManage and NetDocuments have been innovating at a rapid pace over the past few years. Both companies have invested in advanced data analytics, entity extraction and other services that add significant value to matter management, pricing analysis and knowledge management. What RAVN brings to iManage is a powerful analytics, machine learning and visualization platform, in addition to solid enterprise search capabilities. With iManage planning to integrate key RAVN tools (auto classification and clause banks, for example) into its platform, iManage is doubling down on a vision of the DMS as a legal service delivery foundation. NetDocuments has also been developing similar capabilities with its sizable investment in SOLR and Lucene open source search tools.

Adoption. We discuss AI in a separate section below but, for DM purposes, we expect that with the addition of AI and other extraction / classification techniques, adoption will grow. (As a side note, we see many law firms across size ranges where lawyer use of the DM ranges from under 50% to typically no higher than 75%.) With the potential for automatically classifying document type and extracting key metadata, the effort involved in saving documents may go down. And, finding documents in the DM – even without search – likely will be easier with more fields and facets available to filter content quickly.

Information Governance. In the age of regular and massive cyber breaches, every law firm now takes cyber and data security seriously. Beyond hardening the perimeter and detecting intrusions, today most firms assume that at some point a breach will occur. To minimize damage when an intruder gains access, documents must be properly secured to those who need access. Consequently, firms are rapidly moving to gain wider adoption of DM and better lawyer compliance with information governance policies. Gaining that compliance remains a challenge because it requires lawyers to take extra manual, tedious steps. The addition of AI for automated entity extraction and document classification will almost certainly ease IG challenges.

Search

Search as Platform. Legal-focused search platforms have evolved significantly over the past two years. We see the RAVN acquisition as validating the “search as a platform” approach that RAVN, Handshake Universal Search and Sinequa had adopted. Search is no longer a black box bolt-on tool to other law firm IT infrastructure. Each of the above platforms offers APIs and developer tools to build search apps, leverage personas and deliver information in context based on client work, time entry and more.

Almost all firms have DM, but only some have enterprise class search. The iManage acquisition of RAVN signals that search has now become a core part of DM. (NetDocuments has also made search core to its platform by using SOLR and LUCENE open source search tools.) We believe the integration of search into the DM and the addition of AI to search will eliminate many of the past challenges with search, such as auto-classification and relevance ranking.

Artificial Intelligence

Mainstreaming Legal AI. As noted at the outset, we have observed a bit too much hype around legal AI for our taste. But, we do believe that the acquisition of RAVN signals the validation of legal AI. As important, it reflects a more complete “productization” of AI. Most legal AI products to date tend to be stand-alone solutions. With AI integrated into a core platform, it will become a tool lawyers use regularly. That is, instead of “going to an AI tool” for a specific task, the “AI tool will come to lawyers” as part of tools and workflows already in place.

Competitive Hotbed. NetDocuments has told us that they too have looked at AI companies to acquire and, in parallel, is considering a build rather than buy strategy. With Google, Facebook, and Amazon all having open sourced their AI tools, building AI into other systems at relatively low cost and effort is now possible (compared to what it would have taken even two years ago).  iManage’s RAVN acquisition will likely push improvements in this area to even more law firms, lawyers and clients. Beyond DM, we think this acquisition will accelerate the already vibrant development of use-case specific AI tools. The list of AI tools grows longer by the month. Prominent acquisitions are always a good motivator for budding entrepreneurs. Moreover, so many types of AI and potential legal market use cases for it exist that we think other products will continue to thrive.

In Sum

Regardless of the deal’s details, we see this as a turning point for the market. Document management will move from what had been almost an afterthought utility at many firms to being deeply integrated with the business and practice of law. Likewise, both search and AI will become core parts of law firm infrastructure.

We have long focused on identifying and understanding law practice and law firm business problems and then turned to technology as part of the solution. For us, this deal heralds two exciting advances in solution design. First, many good solutions will now be easier to design and deploy. And second, the deal’s validation increases the awareness and likely willingness of lawyers and firms to embrace more sophisticated solutions.

How to Survive Complex Projects, Part 6: Countdown to Launch and the Rule of Seven

3 May

By Andrea Alliston, Partner, Knowledge Management, and Nicola Shaver, Director of Knowledge Management, Stikeman Elliott LLP

In part 5 of this series, the wonderful world of user acceptance testing (UAT) was explored. Ed.

Now, you have tested your platform and you are satisfied that you have a product ready to release to your users. How do you manage the launch?

Get the message right

An old adage of marketing, the Rule of Seven, proclaims that prospective buyers need to see or hear the product’s marketing message at least seven times before they will be persuaded to buy it. While some argue that the rule is outdated in today’s digital world, the message behind it remains unarguably valid: to succeed, a marketing effort must be repetitive and consistent. This maxim applies equally to prospective buyers of new products in the world at large and prospective users of a new platform inside an organization or firm. Absent repetition, buyers and users will not recognize – and therefore not trust – the product on offer. Running a few advertisements or sending out a few communications and never speaking about the product again simply will not work. Only continuous effort ensures success.

Repeated, consistent promotion was central to our launch and training plan during our enterprise search project and it was broadly successful. In a global firm with eight offices and several thousand people, we wanted to be certain that no one could say they had not heard of our new platform by the end of our launch campaign.

Vary the format

We also kept our audience at the forefront of our minds. Knowing that lawyers get massive volumes of email, we understood that they would not read unnecessary messages. How then could we ensure that each and every person in the firm would be touched seven times by our message without overwhelming – or worse, annoying – them? Our answer was variety or, in marketing-speak, we took a multi-channel approach. People are less likely to protest if the message is received in different ways, at different times. So we planned to rely on all of the following:

  • Email
  • Intranet posts
  • Telephone displays
  • Presentations at practice group meetings
  • Promotional posters
  • Launch video
  • Branded swag
  • Treats
  • Elevator chat

We tried to think of every audio, visual, and tactile method we could use to deliver our message.

Plan, plan, plan!

The combination of our intended quantity and variety of messaging meant that, as with all other parts of the project, being prepared was essential. We had our strategy, now we needed a plan. Months before our pre-launch communications rolled out we developed a launch plan detailing the timing, content, and format for each communication. We captured the lead time needed for ordering our swag and for scripting, shooting, and polishing our video. Like any other project plan, each task was assigned to a specific person and checked off as completed.

Figure 1. Map for our search project

Be prepared for setbacks

A launch and training campaign informed by a well-considered strategy and supported by a detailed plan, is primed for success. Nevertheless, hiccups inevitably will arise along the way. During our search project, we developed a bold plan for our promotional video to play automatically as soon as people logged on to their computers on launch day. This was more complicated than we had anticipated. Many people do not log off their computers before leaving the office each day, so the video play was unintentionally staggered (in spite of an email circulated asking everyone log off the night before). And, we had no way to thoroughly test whether the automatic video-play would work on everyone’s computers given the variance in individual set-up. Many people were surprised by the video when it suddenly played a day or two late, and some complained that when the video started playing they were not sure what it was or how to get rid of it. Our intentions were admirable, but the execution taught us that something that cannot be tested properly beforehand should not be part of the launch plan. Needless to say, we would not do this again.

Train your users

Like our communication strategy, our training strategy rested on offering variety. We knew that partners in our large offices would not sit through an hour-long session on search. We also knew that our assistants prefer formal training over less-structured training. In the end, we offered formal training sessions geared to administrative people, drop-in sessions for everyone (but mainly geared to associates), and one-on-one training for partners. We engaged our IT training team for administrative people, but trained the lawyers ourselves. In our smaller offices, we leveraged lunch-and-learns targeted at everyone in the office.

You will know and understand your own firm well enough to choose the kind of training that works best for your user groups. Accept that one kind of training may not work for everyone and build flexibility into your approach.

Lessons Learned

Promotion never ends: We discovered that the launch and training phase of a project never ends. Six months after launch, we were rolling out new training courses, planning “Summer Camps,” and offering non-traditional learning opportunities with games like Scavenger Hunts to tap into lawyers’ natural competitiveness. If you are promoting a tool internally, your efforts will need to be repetitive and continuous.

You will never reach everyone: Although we likely did touch everyone in the firm during our promotional outreach, we still come across lawyers who become excited when we show them subtleties of our search platform and eagerly suggest we promote and teach people about it. Our efforts passed some people by and this taught us that work always remains to be done. On the other hand, keeping yourself from getting discouraged is important – if you have properly implemented a tool that works, you should be able to see from usage statistics that people are using the platform. Our enterprise search statistics are very healthy and this keeps us motivated.

Celebrate: You have done it. Your complex project is finished and you have released a new tool to your users. Take a moment for celebration and acknowledge the help from everyone on the project team. After our enterprise search project, we held a celebratory dinner and gave out spirit awards that included “Best Facial Expressions” and “Most Patience” during the project. The team will appreciate the thought and this will help everyone re-group for the next big project.

How to Survive Complex Projects, Part 5: Getting Your Testing Right

20 Apr

By Andrea Alliston, Partner, Knowledge Management, and Nicola Shaver, Director of Knowledge Management, Stikeman Elliott LLP

In part 4 of this series, the authors guided us through implementation and development. Ed.

Once your platform has been implemented and handed over to your team, you will need to make sure that everything works the way you want it to work. After all of the effort and time you have put in, the last thing you want is to fail now. This is where testing comes into play.

What is User Acceptance Testing?

Unfortunately, we know from experience that if KM does not conduct the testing, you can never be certain the product you hand over to your users will work as they expect it to. This is true regardless of how comprehensive the IT department’s quality assurance testing is. The hard truth is that IT professionals see things differently than most users. IT people are not lawyers and do not think like lawyers. As a KM professional, your job is to operate between the technical and legal realms to evaluate whether your users will be able to incorporate into their daily practice the new platform as designed. This crucial step is called user acceptance testing (UAT).

The form and quantity of UAT the KM team performs varies enormously from firm to firm and project to project. We have worked in firms where very little testing is done before launch and in firms where massive testing is done. In truth, the proof is in the pudding – the more effort you put into UAT, the better your outcome will be.

Where do you start?

Our first step in UAT always is to create a test plan. We find this so indispensable that we now create plans even for testing the most minor upgrades to a platform. When creating the test plan, return to your requirements and use cases developed for your business case. You should plan to test every element of functionality a user would touch, understanding the desired outcome based on your requirements. For example, in our search system we determined that ensuring that a filter worked when applied to a set of search results would not be sufficient. Instead, we also needed to check that the list of values for each filter was correct, we could both exclude and apply filter values, the “or” (rather than “and”) logic of the filter values was in place when multiple filter values were applied at once, and we could both scroll through and search for filter values.

Our test plans usually outline a process where each team member mimics a user’s journey through the platform based on our use cases. Depending on what we are testing, we may allocate roles to different testers, with everyone following a slightly different journey through the platform. For example, partners likely use most platforms differently than legal assistants and you need to ensure the functionality works equally well for both. Role-based testing helps you to confirm that your new technology is ready to be released to everyone in the firm.

People doing the testing should note failures in not only pure functionality, but also design. An IT professional testing a grid view may feel that clicking on a column heading and having the results sort is just fine. But, a KM professional will likely recognize that unless a symbol indicates that sort functionality is available, most users will not know the option exists. Your requirements likely included this need early on, but testers should be on the look-out for its having made its way into the actual build.

Because our firm is Canadian and has a major office in French-speaking Quebec, testing bilingual functionality is vital. Recognize and prepare for the fact that your firm may have its own unique jurisdictional requirements or other complexities that must be addressed through a customized UAT process.

Allow sufficient time for UAT

Depending on the complexity of your project and testing, UAT may take some time. In our experience, no test phase ever goes without hitches. Assume you will have multiple issues to report and some elements of the functionality will not work properly on first review. Also prepare for substantial back and forth with IT and the vendor as you work through the issues that testing reveals. During our enterprise search project, we completed several rounds of testing for each component of the project.

Improve inter-departmental communication

Perhaps the most important takeaway from our major projects has been the importance of communication. Communication is critical during testing and it is hard. Communication among team members and between KM and IT, the firm, and external vendor all are critical. Most communication challenges that arise between your team and IT likely can be improved through mutual empathy and understanding.

As observed, most IT professionals speak a different language than legal professionals and you must account for this in the communication style you adopt between departments. For example, during testing, it is tempting for individuals who find major issues to want to report them to IT at once to be addressed quickly. Of course, in some instances this may well be appropriate. But, we have found that waiting to report all issues together generally works better. One of our team members collects feedback from everyone else, consolidates it into a single spreadsheet, and sends it to IT. Every piece of feedback is numbered and, wherever possible, accompanied by screenshots. We have found that the words we used to describe the problems we find often are insufficient to communicate those issues to IT. In fact, we have been tempted to sit beside our IT colleagues and show them what we have experienced on our screens. This rarely is the best use of anyone’s time, nor should it be necessary as visual props should abate confusion and frustration.

Lessons Learned

Engage multiple testers: People have different aptitudes for testing and technical detail. In the same testing round, we have had someone report that everything looks great, while another person reports over 25 issues. So, you will need a team of testers for UAT. You simply cannot do this on your own.

Understand your team’s limitations: During our enterprise search project, the KM team tested the system’s ethical walls compliance. Even though we managed to do it, it was needlessly time-consuming and, in retrospect, this should more properly have been handled by IT. We would not take this on ourselves again. So be realistic – some things are better left to IT.

Know when to stop: After you have signed-off on a component of the project, stop testing that component’s functionality. It sounds simple, but letting go and trusting that the fixes really are in place can be difficult in practice.  Now, if in using the platform you stumble across new issues, these of course must be reported. Otherwise, encourage your team to trust your firm’s IT and the vendor and move on to the project’s next stage.

Coming up in part 6: In our next post, we get to the exciting part – how to prepare for launch and take-off.

How to Survive Complex Projects, Part 4: A Marathon, Not a Sprint

5 Apr

By Andrea Alliston, Partner, Knowledge Management, and Nicola Shaver, Director of Knowledge Management, Stikeman Elliott LLP

In part 3 of the series, the authors walked us through the key steps in planning complex projects. Ed.

With a plan of attack in place, it finally is time to start on development and implementation. The complexity of your project will depend on several factors; but, no matter whether you are implementing an out-of-the-box or highly customized solution, substantial KM technology projects usually involve an intensive period of technology development.   Enterprise search – aggregating information from multiple sources and presenting it in a user friendly way – is inherently complex.  So, we knew that implementing our project would not be easy.

KM Involvement in Development and Implementation

Even with an out-of-the box solution, you will have options for how different aspects of your project can be implemented. This becomes more complex if you wish to customize the solution.  In our case, we increased the complexity by deciding to implement a new taxonomy tool and KM content management tool in parallel with our search implementation.

In the throes of a complex project, forgetting what you have decided and why is easy to do.   Combined with developers bombarding you with questions regarding the functionality you want, this can quickly overwhelm you.  As observed in an earlier post, having documented detailed requirements was our saving grace in these situations again and again.

A difficult reality in development and implementation is making compromises. Even with the most careful planning, nothing goes perfectly and being told that the design you have envisioned cannot be achieved is frustrating.  What do you do?  You go back to your design principles.  You may recall that in our search project our overarching theme was a relentless focus on user experience.  So, we always chose options that would best support the user experience, even if those options were not perfect.

Data Integration

Because very few KM projects involve stand-alone technologies, a heightened demand for tighter integration across multiple platforms and data integration become key aspects of most projects.   In our implementation, we integrated as many data sources as possible into search, which proved critical to improving relevancy. Those data sources included our InterAction contact management platform, Aderant financial system, matters and experience database, website, blogs, document management system, and KM content management system.

But, integrating data from multiple sources brings its own challenges. In our case, data was sometimes populated from the wrong system or from the wrong field in the right system, which required a bit of detective work to sort out. Another challenge was working with the owners of some of the data to address inconsistencies that the search project revealed.   Enterprise search and other technology projects cast a giant magnifying glass over your data (and its warts). You need to be prepared to address issues that might arise.

Lessons Learned

Manage expectations:  Highly visible, significant technology projects often lead to high expectations.  Throughout our development stage, we managed stakeholders’ expectations with regular updates and early demonstrations.

Tune and tweak: Do not be afraid to spend time making small tweaks that have a big impact.  One of the most valuable efforts we put into our project was fine-tuning relevancy.  Although taking the time mid-implementation to focus on relevancy was difficult, doing so significantly improved the user experience.

Master your metadata:  One reason we were able to identify incorrect data was that we had prepared a detailed data map listing all of the metadata appearing in the search application, including what it should look like and where it was expected to come from.  We revisited this (and other) documentation throughout the development stage.

Coming up in part 5: In our next post, we look at the role KM can and should play in testing complex KM technology projects.

How to Survive Complex Projects, Part 3: Chunking to Completion

21 Mar

By Andrea Alliston, Partner, Knowledge Management, and Nicola Shaver, Director of Knowledge Management, Stikeman Elliott LLP

In part 2 of this series, the authors examined how to develop requirements and focus on them throughout complex projects. Ed.

Now that you have your business and functional requirements in hand, how do you to turn them into reality? It is time to start tackling the practical aspects of the project.   While it may be tempting to jump in and just get going, spending some time up front on planning is well worth it.

Get Past the Fear Factor

Where do you start?   With high-stakes, complex projects, the pressure to get it right is daunting and thinking about all of the tasks that need to be accomplished can be overwhelming. In considering the challenges that lie ahead, you may feel too many hurdles will impede implementation. You may also wonder if you have sufficient resources to tackle all parts of the project or worry about the change management required after the platform is implemented.  How to do you go about rationally planning under these circumstances?

One approach is to start your planning by looking first at your desired outcome and working backwards. Ask yourself what needs to be done to achieve your goal?   Another approach – our favourite – is to break the project into chunks – components, phases, and finally detailed tasks.

Identify the Moving Parts

Think about each major component of the project and set these down on paper. We like to use something visual like a process map or post-it notes.   For the search project we developed a visual setting out the various components of our project, the main phases for each component and the dependencies between them. Each project component was colour-coded and each phase was numbered.  This was less about the detail (that is what the plan is for), and more about keeping a big-picture perspective on the project.

The major components of our enterprise search implementation included the following.

  • Taxonomy Management Tool
  • Taxonomy Development
  • KM Content Management Tool
  • Technology Development
  • Content Migration
  • KM Content Clean-up
  • Launch and Roll-out
  • Within the broad components of any project lie many phases and discrete tasks. You need not identify all of these at the beginning, so create a project plan that allows you to add detail as the project develops. If you have no preferred vendor at the outset, your project plan will likely include demonstrations of various products and a proof-of-concept before a purchase decision is made and implementation can start.

Assign a Project Manager

Your plan is nothing without a strong project manager at the helm throughout a complex project.   If you do not have project managers at your firm, consider asking your vendor for assistance or hiring someone on contract.  You can also look within your own team for someone with good organizational skills who could perform basic project management, like plotting the tasks of each phase of the project against a timeline and keeping track of what has been completed.

The project manager should attend the project meetings with your team and take notes, adjusting the timeline as needed and acting like a human “tickler system”, sending reminders as particular tasks come due. Becoming embroiled in the project’s details and losing sight of the bigger picture is all too easy. An effective project manager can prevent you from getting lost in the weeds by reinforcing your original strategy and perspective; this will help keep your team focused.

Expect the Unexpected

In any large project, issues inevitably arise that push back the project timeline. Knowing at the start where delay will come from is nearly impossible; but, be ready for hurdles and, if possible, build some flexibility into your timeline.

We found that the key to dealing with delays is to communicate, among not just the project team, but also the stakeholders. If the original launch date no longer looks feasible, try to set a realistic new launch date and strive to meet that goal. Adapting as issues arise allows you to keep moving forward, rather than being knocked sideways by every complication.

Lesson Learned

Plan, plan, and plan: The importance of planning cannot be understated. Remember Henry Ford’s words: “Nothing is particularly hard if you divide it into small jobs.” Have your project manager hold regular meetings with the core project team so everyone understands what they need to be doing. During major projects, we meet inter-departmentally at least biweekly and more frequently if we enter a particularly intense phase of the project. We also hold weekly meetings with the KM team to keep the project on course.

Take pleasure in small successes:  We used our diagram of the project to keep us engaged.  We felt a sense of great satisfaction each time we could cross off one of the task bubbles as completed. Celebrating the small successes along the course of a project helps keep your team motivated for the long haul.

Communicate: Any complex project involves stakeholders from multiple departments, raising all kinds of communication challenges. We have found it critical to ensure that the information coming from our own team is consistent. In our enterprise search project, we met as a team before but on the same day as our meetings with IT to ensure were all on the same page before reporting to the other department. By maintaining our lines of communication and ensuring that the messaging coming from KM was clear, we were able to improve the flow of information between departments. Having said that, we know we still have some way to go. We can only hope that our next major project will be the one where we get the balance right.

Coming in part 4: In our next post, we look at the development and implementation phase of a complex project. Rest up.  You are going to need it.

AI Round-up: A Guide to ILTA’s Artificial Intelligence Content

17 Mar

Joe Davis has graciously allowed us to cross-post his recent compendium of ILTA content on artificial intelligence.  So, don’t miss this second opportunity to catch up on some of the latest thinking on this hot topic. Ed.

By Joe Davis, Project Consultant, Prudential Financial, Inc.

OK, so Watson won “Jeopardy!” back in 2011. That’s ancient history in technology years.  ILTA provides a wealth of programming about the current state of affairs in Artificial Intelligence that will benefit law firms and corporate legal departments.  In the future, I’m sure we’ll have a bot to curate all this content for us.  In the meantime, below is a sampling of some of ILTA’s best AI-related content from ILTACON, Insight, webinars, white papers and Peer To Peer.

Webinars

Beyond the Hype: Artificial Intelligence in Legal Research
This webinar, sponsored by ROSS Intelligence, features ROSS CEO and co-founder Andrew Arruda discussing how the company was born out of a desire to get from questions to answers more quickly.  He points out that even though AI is still in its “Model T phase,” the Model T still beat the horse in many ways.  Bill Caraher from von Briesen & Roper talks about what made his firm interested in the technology, and shares with moderator Beth Patterson the kind of firm culture that is required for this technology to catch on.  Be sure to listen for the last question to hear about how ROSS is practical for small firms, solo attorneys and pro bono work.

Nothing To Fear: How Artificial Intelligence Can Benefit Law Firms
Peter Wallqvist of RAVN Systems offers this solo take on AI, including a look at which kinds of AI RAVN and other AI companies focus on. This webinar offers the most in-depth explanation of AI on this list, so be prepared for an academic, but very thorough, treatment of the subject.

Articles

Reframing the AI Question in Law by John Alber
ILTA Futurist and retired Bryan Cave partner John Alber makes the case that the legal world should focus on using AI (and technology in general) to improve its service model. Tame Regulatory

Chaos with Cognitive Technologies by Eric Laughlin
Sanctions for improperly managed compliance requirements cost corporations more than $20 billion per year.  Author Eric Laughlin of Thomson Reuters offers a perspective on using AI to manage regulatory complexities.

When Machine Intelligence Joins Your Professional Services Team by Mark Noel
Mark Noel of Catalyst Repository Systems provides a good introduction to the advantages of using Technology Assisted Review (TAR) as part of your e-discovery process.

Artificial Intelligence Systems and the Law by Andrew Arruda
ROSS Intelligence CEO/co-founder Andrew Arruda offers a primer on the different categories of AI, along with a brief introduction to the ROSS platform.  Also included in this article are 10 predictions excerpted from a 2014 ABA Journal article by Paul Lippe and Daniel Martin Katz about the way Watson will affect the legal profession.

Audio

The Exponential Law Firm: Unlocking the Growth Potential of AI and Disruptive Thinking
Technology isn’t necessarily the key to being exponential, according to Fast Future’s Rohit Talwar.  In this session from Insight 2016, Talwar talks about how the legal profession needs to focus on three things: what is vital in the next 12 months, where innovation will come from in the next 3 years, and the an “early warning system.”  Overall, he is confident that “there has never been more opportunity for the legal sector than there is being created by science and technology today.”

Legal Innovation: More Than Just Artificial Intelligence
As the name implies, this Insight 2016 panel session is about more than just AI.  Panelist Jan Van Hoecke, CTO and Co-Founder of RAVN Systems, outlines the challenges to innovation and discusses a case study in which the risk and compliance department of a top-50 financial services company leverages AI to reduce its risk.  Could this be a potential new line of business for law firms?

Choosing the Right Artificial Intelligence for the Job
Panelists Sylvia Leblanc, Dera Nevin, Noah Waisberg, Julian Tsisin and Peter Wallqvist cover a lot of ground in this ILTACON session, including weak vs. strong AI, the trailer for the film Morgan, getting rid of “the ugly bits of lawyering” and Sharknado.  One conclusion: it is rocket science.  Tip: check out this video and this follow-up before listening to the session.

The State of Play of Artificial Intelligence in Law?
Michael Mills of Neota Logic discusses the current state of affairs and the players within the Legal AI space.  Be sure to take a look at his slide deck, which contains some useful diagrams.

Face Your Fears: Embracing Change in the Legal Environment
Consultant Ann Gorr leads this panel featuring Dennis Garcia from Microsoft, Matt Blaine from Davison Eastman & Munoz, and Jim Merrifield from Robinson Cole in a lively discussion on “how to be a grown up law firm.” Along the way, they cover “conversation as a platform,” augmented reality, driverless cars and Pittsburgh vs. Scranton.  Two resources mentioned in this session: Klaus Schwab’s The Fourth Industrial Revolution and UC Hastings’ Disruptive Innovation: New Models of Legal Practice.

Grading Susskind: The State of Legal 20 Years After the “Future of Law”
While these panelists probably shouldn’t give up their day jobs to pursue a career in comedy, they do get credit for putting together a creative alternative to the standard panel discussion.  In the style of NPR’s Wait Wait… Don’t Tell Me!, this session evaluates the predictions Richard Susskind made 20 years ago in his book The Future of Law.  Host Ryan McClead of HighQ (now with Neota Logic) and panelists Susan Hackett of Legal Executive Leadership, Sam Nickless of Gilbert + Tobin and Dan Lear of Avvo discuss the present and future of legal technology.  You’ll also learn what three lawyers and three MBAs on a train, two lions, and one elephant may or may not have to do with the founding of the American Corporate Counsel Association.

Mutual Challenges and Successes: A Large Firms Discussion Forum
This session, moderated by Tim Golden of McGuire Woods, features three CIOs from large firms (Doug Caddell of Mayer Brown, Ash Banerjee of Hogan Lovells and Curt Meltzer of Chadbourne and Parke) covering a variety of issues that pertain to large firms.  The discussion turns to AI at the 17-minute mark.

Using the Right Data To Drive Your KM Program
Kingsley Martin and Karl Haraldsson examine the journey from Profiling to Search to Analytics to Predictive Coding and Machine/Deep Learning.  This session starts with a strategic view, but includes some very tactical ways to start quantifying legal practice.  Highlights include “don’t start with the Death Star,” “If I knew… I would do…”, buying a car (in four acts) and insight into the importance of data visualization.

Watson, I Need You! Augmented Intelligence for Legal

IBM’s Kyla Moran offers a broad perspective on Watson.  While this ILTACON session is light on legal-specific applications, it does offer insight into how Watson works.  Ginevra Saylor, National Director of Knowledge Management for Dentons, asks some interesting questions as moderator, including why the other Jeopardy contestants were able to answer any questions at all.

How to Survive Complex Projects, Part 2: Commitment to the User Experience

7 Mar

By Andrea Alliston, Partner, Knowledge Management, and Nicola Shaver, Director of Knowledge Management, Stikeman Elliott LLP

In part 1 of this series, the authors discussed how to decide whether to pursue a major project and convince leadership of its value. Ed.

With decision making and project approval behind you, the next step is to start work on the design and detailed requirements.   In our enterprise search project, the research from the decision-making stage made it clear that we had much work to do to improve our user experience.  As a result, the theme we wanted to capture in our design and requirements was a relentless commitment to user experience.   The underlying theme for your projects may be different.  The point is to understand your theme and focus on it throughout the project.

Design for Success

The design phase of a software development project can be defined in many ways. In KM projects, design usually is about matching your users’ needs with the applicable technology’s functionality (and constraints).  Our strategy of putting the user experience first required us to engage a UX expert to help us to create user journeys, identify desired outcomes within the limits of our technology platform, and make tough decisions about our KM content and its management.  Do not underestimate the value of specialized expertise at this point in a project.

In addition to seeking expert advice, now is the time to engage your users and have them get their hands dirty. We used two techniques with our users.

  • We held card sorting workshops for lawyers to determine the system’s structure from a content perspective.
  • We convened focus groups to gather feedback on our wireframes and proposed functionality.

A set of design principles that set the tone of the project should come from the design exercise, along with the details needed to prepare the requirements. As one designer notes, “Design principles articulate the fundamental goals that all decisions can be measured against and thereby keep the pieces of a project moving toward an integrated whole.”  Your design principles should reflect your particular project; ours were the following.

  1. Keep the interface simple and intuitive
  2. Restrict filters to a maximum of 7, plus or minus 2, per page
  3. Avoid customization where possible
  4. Allow for flexibility in accessing content
  5. Provide a bilingual interface
  6. Include all filters as part of the search snippet

Business and Functional Requirements

Projects are more successful when a clear set of business and functional requirements are documented; they ensure that the business stakeholders, the internal technology team and the vendor are on the same page. Where do you start?

Some of you will be fortunate enough to have a business analyst in your firm. Indeed, engaging business analysts in law firms either on a contract or permanent basis seems to be on the rise.  But, what if you are not so lucky? Not having a business analyst role, we used the KM/UX consultant we were working with and our internal KM resources to create the needed documentation.

Our business requirements were comprised of annotated wireframes, descriptive narrative, and spreadsheets (see screen shot from one of the pages).   However, depending on your project, you will also need detailed functional technology requirements for the developers.  Once a draft is ready, the requirements should be circulated and reviewed in detail with both your technology team and vendor.

Lessons Learned

Stick to the design principles: We needed to simplify various aspects of our search implementation to be responsive to user feedback.   Our mantra became “less is more.”  While it sounds easy, it was very difficult to give up certain content management practices we had used for years.  We constantly second guessed ourselves and worried about making a mistake, getting it wrong, and losing what we once had.  We needed to be quite disciplined with this part of the project and, so far so good.  No one misses anything we took away and the benefits of sticking with our design principles are paying off.    

Discuss with the vendor: Once we had a sense of our desired design, we had early discussions with the vendor to explore options for some key functionality and get the vendor’s input on design elements we were considering.  The goal was to tap into the vendor’s expertise and address any potential issues early on in the project.

Get into the details:  Our business and functional requirements were developed when we had time to be thoughtful about what we were trying to achieve.  Being able to go back to those requirements when we were later under pressure gave us confidence about our decisions and the right path forward.

Coming up in part 3: In our next post, we look at project planning as a critical step in putting your design and requirements into action.