Author: Onit

Onit Customer Jaguar Land Rover is a 2018 National Women in Law Honoree

Onit is excited to announce that Anna-Lisa Corrales, General Counsel of Jaguar Land Rover North America (JLRNA) is a 2018 National Women in Law award honoree, a program sponsored by Corporate Counsel and InsideCounsel.

This is especially exciting for us since we partnered with Anna-Lisa and JLRNA for a major technology implementation last year. These awards honor general counsel, in-house leaders and law firm partners who have demonstrated a commitment to advancing the empowerment of women in law. These outstanding women will be recognized at an awards dinner on Oct. 3 as part of the Women, Influence & Power in Law Conference in Washington, D.C.

These awards spotlight North American women in-house and law firm leaders who have demonstrated extraordinary leadership and business acumen as they have guided their organizations through often treacherous roads to achieve success. These women stand out because they are business strategists, complex problem-solvers, and of course, great lawyers. And as important (especially to them) is that they are great people-leaders—they care more about the success of the team than their individual success.

The Women in Law awards recognize legal department leaders in the following industries: Banking & Finance; Insurance; Transportation & Infrastructure; Manufacturing & Chemicals; Technology, Media & Telecom; and Retail & Consumer Goods. The program is also highlighting extraordinary leadership by recognizing female general counsel and law firm partners in the following categories: Innovative Leadership; Thought Leadership; Collaborative Leadership; Transformative Leadership; General Counsel of the Year or Managing Partner of the Year; and Lifetime Achievement.

Learn more about the National Women in Law award.

IaaS, PaaS, SaaS Part I: Which is Best for My Organization?

Most of us are familiar with Software as a Service (SaaS), since it probably gets more attention and is more popular than Infrastructure as as Service (IaaS) and Platform as a Service (PaaS), for reasons we’ll get to later. Interestingly, there have been recent rallies to get rid of the term “SaaS” and simply call it software since virtually everything is done on the cloud now. It’s a fair point, but even so, we believe it’s still useful to retain the term in order to differentiate the three major models. Each of the models is a bit different than the others, based on just how much “control” the client (end user) wants over the service provider’s computing infrastructure, project budget, etc.

In a nutshell, the three most common models of cloud computing currently in use are:

  • Infrastructure as a Service (IaaS)
  • Platform as a Service (PaaS)
  • Software as a Service (SaaS)

IaaS is the pinnacle model for companies who want to rent servers, networking, storage and virtualization – these being managed by the service provider. The company itself will manage the O/S, middleware, runtime, data and ultimately, the applications. Of course, companies that choose to go this route need the technical expertise on hand to build applications themselves from scratch. Having ultimate control over the service has its advantages, but also drawbacks. Some companies have expressed concerns that their data is not as secure using IaaS as compared to other models. Amazon Web Services EC2 and Rackspace Cloud are two examples of IaaS.

PaaS is considered the mid-range model when it comes to the client’s level of control. Here, a company is renting not only networking, storage, servers and virtualization; but also an O/S, middleware and runtime – all being managed by the provider. The client company manages the data and applications. An important part of this is that PaaS provides tools the client’s developers can use to create applications. Amazon Web Services Elastic, Google App Engine and Microsoft Azure are examples.

SaaS is by far the most commonly used cloud computing model today. The service provider manages the entire ball game, so the client simply uses the applications on a pay-as-you-go basis. Pretty much everything that’s technical, including the hardware and O/S, are out of sight and mind for the end user. Many applications can be bought off-the-shelf, while others can be customized by providers per the client’s requests and particular business process problem. Some common examples of SaaS in current use are Microsoft 365, Docusign, Netflix, Google Apps and Onit.

So which model is best or your company? That’s a question only you and your team can answer, but we’ll give you more food for thought in the next part of this blog series.

In part II we’ll discuss the advantages and disadvantages of each model in more detail.

Onit Honored for Third Consecutive Year on the Inc. 5000 Fastest-Growing Company List

Inc. magazine today revealed that Onit is number 1431 on its 37th annual Inc. 5000, the most prestigious ranking of the nation’s fastest-growing private companies. Onit achieved a staggering three-year growth of 327%. The list represents a unique look at the most successful companies within the American economy’s most dynamic segment—its independent small businesses. Microsoft, Dell, Domino’s Pizza, Pandora, Timberland, LinkedIn, Yelp, Zillow, and many other well-known names gained their first national exposure as honorees on the Inc. 5000.

The 2018 Inc. 5000 is ranked according to percentage revenue growth when comparing 2014 and 2018. To qualify, companies must have been founded and generating revenue by March 31, 2014. They had to be U.S.-based, privately held, for profit, and independent—not subsidiaries or divisions of other companies—as of December 31, 2017. (Since then, a number of companies on the list have gone public or been acquired). The minimum revenue required for 2014 is $100,000; the minimum for 2017 is $2 million.

The Inc. 5000 is a list of the fastest-growing private companies in the nation. Started in 1982, this prestigious list has become the hallmark of entrepreneurial success. The Inc. 5000 conference & awards ceremony is an annual event that celebrates the remarkable achievements of these companies. The event also offers informative workshops, celebrated keynote speakers, and evening functions.

HBR Law Department Survey: A Great Benchmarking Opportunity for Onit Customers

As a valued Onit customer, we wanted to pass along an opportunity to participate in HBR Consulting’s 2018 Law Department Survey. This is a survey that many of our clients find valuable and have contributed to in prior years.

Recently, the survey has been expanded to include a number of technology questions to help provide a holistic view of the legal technology landscape. At Onit, we are especially looking forward to seeing the market’s feedback on how our customer satisfaction compares to others in the space as we strive for continuous improvement. Of note, Onit is listed in the e-billing, matter management, and workflow tools questions in the survey.

The survey has been a leading source of benchmarking data for general counsel and legal operations leaders for 14+ years, and over this time period has included 65% of the Fortune 500 across 22 industries. In addition to technology, the survey captures valuable data regarding legal spending, staffing, operations, and outside counsel management.

As a participant, you will receive a complimentary summary of the results in the fall of 2018, access to HBR’s regional benchmarking roundtables and discounts on the detailed results package.

If you haven’t already completed the survey in 2018, HBR has provided a link and extended the deadline to August 31.

Should you have any questions regarding the survey, please feel free to contact HBR’s survey team at [email protected] or visit www.lawdepartmentsurvey.com

3 Big Essentials to Look for in an Enterprise Solution Provider

The time inevitably comes when most legal departments need to enhance their process automation, while others may be looking for their first automation solution. There are many things to keep in mind when researching providers and doing due diligence, but we don’t want to overwhelm you with a long list right now. For the purpose of this blog, there are three critical things we wanted to share with you — three of the most basic things you should be looking for in a solution provider:

  1. Enterprise Solutions – The provider should be capitalizing on the broad applicability of workflow-based task management, and eager to expand into functional areas outside of legal and aggressively solicit customer needs to write custom applications for other corporate-wide departments. Whether it’s an off-the-shelf solution or a platform on which the client can create their own applications, a provider that is well-versed in developing solutions for both legal and non-legal applications could be the way to go.
  2. Process Automation –  A workflow-centric approach that seeks to deconstruct matter management into independent, collaborative functional lifecycles that lawyers and operations managers use on a regular basis is critical. An a la carte model can empower users to add capabilities and components as needed. The ability to scale your enterprise legal management system in a manner consistent with operational requirements is your key to success.
  3. System Architecture – The providers that are on top of their game offer a modern architecture that showcases class-leading technology and a decidedly Saas-based approach to legal business application management. It needs to be flexible and agile, and designed for rapid deployment, flexibility and agility. Last but not least, it needs to work the way your team works.

If these three things are at the top of your list when you begin your search for a solution provider you’ll be a huge step ahead of the game.

Legal Thought Leader Matt DenOuden Offers Insight on Enterprise Legal Management Space and Future of the Industry

We’re excited to announce our latest podcast! In this episode, Onit’s Matt DenOuden, VP of Global Sales shares his thoughts about our company and customers. After he relates his story of how he came to Onit, Matt discusses how Onit is unique and explains what it is that makes our enterprise legal solution successful and drive value. He mentions that Onit is also unique in that we were one of the first to really think about “intake” and to subsequently develop a software solution.

Matt then speaks about some of our recent successes, such as a SOX compliance solution out on the West coast, as well as solutions for employee onboarding, travel approvals and IT ticketing. He then talks about one of our biggest customer success stories: Archer Daniels Midland currently has Onit solutions up and running along with a new claims management solution that is currently being built. Matt then moves on to his thoughts on the future of legal technology by explaining that we need to have a more combined, coalesced platform to serve the legal community’s needs. Finally, he offers comfort to those who fear change and are perhaps wary of technology, “Our software is designed to enable the work that you are already doing…we try to be as non-disruptive and nonintrusive as possible. You should be in our software as seldom as possible. Our software should be following you around and helping you do your work.”

Listen to episode 4 on iTunes

Embracing Legal Department Transformation with Technology: Legal Service Requests

In our new white paper, Embracing Legal Department Transformation with Technology, we investigate the new legal department landscape and how a legal service request solution (LSR) is a key player in the makeover.

Legal departments have enough “real” legal work on their plates even without taking into account all of the daily administrative tasks. Now more than ever, legal departments are slowly changing the way they work. Their objectives can come slowly or quickly, and sometimes they get it right; sometimes it’s hit-and-miss. It’s crucial that the legal department be allowed to focus more on the real legal work, without sinking deeper into the administrative quagmire. In many cases, a well-chosen and effective technology solution is the best answer. But driving and implementing change is another key element in the solution. Keeping up to date with the latest technology is always good, but to implement a technology transformation requires buy-in from leadership and IT, as well as an unwavering commitment to see the project through.

A cutting-edge legal service request solution is key in bringing about transformation relatively easily and cost-effectively. By implementing an intelligent, self-service portal to initiate LSRs, the first phase of the battle is already won. The company will also be able to leverage their new system, since information can be shared across departments and systems. Fewer staff members will need to spend time entering data for the same client and matter, which saves money. All of this will allow the legal department to spend more time focusing on the needs of business consumers – not following up on paperwork and other purely administrative and time-consuming tasks.With a well-chosen legal service request solution, the legal department can provide higher quality services, operate more efficiently, and become a driving force in fueling the company’s success.

Download this this white paper to learn more about:

  • Legal service request market trends
  • Industry best practices
  • Benefits of the right solution
  • The mistakes of falling into the “consensual neglect” trap

Enterprise Legal Management Insufficiencies? Don’t Be So Hasty with that RFP

Some companies struggle with their current enterprise legal management (ELM) systems that focus on just core matter and spend management. But when the day comes that they discover there are other business processes that also need automated solutions, it’s time to issue another RFP and undergo another long, expensive and drawn-out path to implementation.

But we’d like to offer another solution. We believe we should be looking at the elements of enterprise legal management as processproblems instead of data problems. When we do this, we’re clearly taking more ownership in business process management (BPM), even though we may not immediately realize it. And in order for corporate legal to be a true corporate citizen, it needs to have a deeper stake in business processes. If you already use automated process solutions, congratulations. You already have a stake since business process automation is inseparable from business process management.

Again, ELM systems that are only capable of core matter and spend management have a clear disadvantage. But on the other end of the spectrum are systems that are loaded with features that will never be used; either because the company doesn’t need them or they don’t want to use them. These solutions were likely an outsize investment to begin with, which already puts the company at a distinct disadvantage. But the situation needn’t be so bleak, and it’s not even necessary to proceed on a quest to find a happy spot somewhere on the spectrum.

The ability to scale your Enterprise Legal Management System in a manner consistent with operational requirements is your key to success.

Seems simple, but how do we do it? By breaking up enterprise legal management into discrete, individual task-based processes, it becomes clear that an “app-based” solution is the most logical way to go. With these, users have the ability to develop and incorporate these discrete process capabilities into the larger enterprise system as they are needed – a la carte. The old “ELM as monolith” approach is, for the majority of legal departments, obsolete. The resounding answer is that we should be looking at ELM as a process problem, rather than a data problem.

Smart companies are now seeking core matter management and e-billing functionality that can be augmented with other process solutions as they are needed. With such systems, scaling could not be easier. In many cases, a company will already have an existing ELM installation, and augment it with process solutions from other providers. These add-ons will be completely compatible with their existing ELM system. There are off-the-shelf, focused solutions as well as platforms on which the company can build their own custom solutions. In any case, the ability to enhance and optimize your system without going the painful RFP route is always a good thing.

Staying the Course with Your Subpar Process Automation Strategy? Think Twice

In our new white paper, Embracing Legal Department Transformation with Technology, we investigate the new legal department landscape and how a legal service request solution is a key player in the makeover. But this blog focuses on one section in this paper, “The Case of Consensual Neglect,” which we feel deserves a bit more airtime.

Successful transformation with technology usually comes with a price tag attached. Those who are willing to put in the time, effort, research and money likely stand a better chance of success than those who skimp on any or all of these four factors. Which brings us to another point on the spectrum where we find people who insist on being committed to an irrational or failing strategy. In some cases, the strategy in question was once successful, which can add salt to the wound by means of the “sentiment” factor. In the Harvard Business Review Professors Freek Vermeulen and Niro Sivanathan detail a number of biases that explain why leaders stay committed to failing strategies. Dubbed “consensual neglect” by Karl Weick of the University of Michigan this is a very real phenomenon that hurts businesses in the near and long term:

In combination, these biases lead a company’s decision makers to ignore signals that their strategy is no longer working. It is what Karl Weick, of the University of Michigan, calls consensual neglect: the tendency of organizational decision makers to tacitly ignore events that undermine their current strategy and double down on the initial decision in order to justify their prior actions. 1

Here are six of the most common biases as described by Vermeulen and Sivanathan: 2

  1. The sunk cost fallacy, in which people focus on the investment already made in a particular course of action and hope that, if the approach is continued, invested costs will be recouped and the prior investment decision vindicated
  2. Loss aversion, in which people prefer to gamble on the future success of a previous commitment to a currently questionable strategy – even if it means the investment of additional resources – rather than to incur an immediate loss by changing direction
  3. The illusion of control, in which people regularly overestimate their ability to control future events, thus reinforcing the first two biases described above
  4. Preference for completion, the inherent bias of people toward completion of tasks, such as seeing a particular course of action through
  5. Pluralistic ignorance, in which people who might disagree with a particular course of action remain silent because they think they are the only dissenters and that everyone else is on board
  6. Personal identification, in which people perceive that their identities and social status are tied to their commitments and that withdrawing their support for a course of action they previously approved would risk loss of reputation or status

According to research, this phenomenon of consensual neglect is fixed deeply in our brains, making us more apt to stay the course with a particular strategy – even when it is clearly not the best, or even failing. Worse yet, some companies will double down on their old strategy instead of trying something new, sending them further into a downward spiral. This can easily apply to every facet of a company, but we’re focusing on driving technology transformations. Again, the right technology is readily available to those who genuinely want to avoid falling prey to consensual neglect.

1, 2  Freek Vermeulen and Niro Sivanathan, “Stop Doubling Down on Your Failing Strategy – How to Spot (and Escape) One before It’s Too Late,” Harvard Business Review, Nov.-Dec. 2017, at 110-17.

Your Guide to Seamless Legal Tech Implementation: Part 2 — Get Project Stakeholders on Board

Part two of a three-part “Guide to Seamless Legal Tech Implementation” Parts one and three are below.

Part 1 – Scoping the Project Before Buying
Part 3 – Change Management Before and After Implementation

The importance of stakeholder engagement is vital, both during technology project definition and implementation. So how can you identify key project stakeholders and get the buy-in required?

As you read in part one, collecting and analyzing stakeholder and end users’ requirements is a crucial enabler of success when designing and implementing a new system. It is possible to outline solution requirements without considering stakeholder needs, but to do so presents a real but avoidable risk of project failure.

Some of these stakeholder groups or individuals may be fully on board and require little management regarding expectations. However, there are likely to be key stakeholders who will have other priorities or may be resistant to the change that a new software tool brings.

When software projects fail to deliver expected benefits because of stakeholder/end-user issues, these projects fall into two categories:

  • Those that do not independently verify stakeholder requirements (“one of the users said this, so that’s what we must do”)
  • Those that treat project stakeholders and their requirements as a kind of inconvenient truth (“they exist but we don’t really agree with them/want to listen to them”)
  • Neither of these positions are desirable or helpful. However, it is possible to mitigate them.

WHAT ARE YOU TRYING TO ACHIEVE?

Effective solution selection requires understanding the needs of all stakeholders and the ultimate users of the application.

As learned in part one, producing a scope document helps eliminate confusion within the project by managing expectations from the start. With the users’ needs captured, you can define the objectives of the software purchase and identify additional project stakeholders.

IDENTIFYING THE PROJECT STAKEHOLDERS

After defining the project objectives, identify the relevant stakeholders. Gather their requirements and learn the solution’s impact on their teams. A successful project requires the buy-in from not only the legal department, but of the entire management level. If you miss the input of some project stakeholders can seriously affect the successful implementation of your software. Stakeholder identification can be time-consuming as it may include parties beyond immediately obvious ones. Who are typical stakeholders? There are immediate system users (for e-billing, this would be accounting and legal/legal operations), but there are also legal service providers and law firms, sales, IT, and procurement users.

A structured and consistent approach can help you identify stakeholders and their roles. Tools and techniques include focused interviews, multi-media communications, surveys, role-playing, and follow-up action workshops. This will ensure stakeholder groups are fully engaged and supported.

USING THE INFORMATION

Once you capture the stakeholder requirements, the next stage is interpreting the results and choosing what to act on. At this stage, achieving balance is vital; keep the stakeholder who shouted the loudest from dominating the requirements. Remember what the legal department is trying to accomplish and select only those items of feedback that will help. Try to prevent the project scope from becoming too broad. Remember that the best solutions are both effective and efficient and that a positive ROI will measure success.

If you have access to an experienced project manager/analyst, they can record and interpret the results of the stakeholder and user sessions and feed the conclusions into the overall project requirements.

ONGOING COMMUNICATIONS

Finally, it is essential to let stakeholders know what you have done with their feedback and why. This is vital to engage them in the project.

You cannot always please all project stakeholders, so use data-based justification for the decisions taken when you can. Stakeholders, particularly the primary users, can make the new process sink or swim. When it comes to implementation, you will need their support to encourage their teams and peers to use the new system. While they may not like what they hear, they value the reach out (and will find out in the end anyway).

Finally, you will need to continue using the stakeholders for validation of the project as it progresses, primarily to ensure that the delivered system does not “drift” from the agreed objectives and to check that the original requirements are still valid as they may change time. This is also a benefit of having a scope document. Plenty of applications have gone live to a user population that says, “great, but that’s not what we need now!”

THINGS TO CONSIDER FOR EFFECTIVE STAKEHOLDER ENGAGEMENT

So, what lessons are there for those involved in system selection and implementation?

  • Be clear on what the project is trying to accomplish?
  • Identify the project stakeholders in context; what are their roles and responsibilities?
  • Use relevant capture methods; keep them consistent and unbiased.
  • Incorporate the feedback into the solution requirements. Maintain balance and remind yourself of the project objectives.
  • Keep the stakeholders informed of the consultation outcomes and be prepared to adapt the project if it doesn’t achieve the agreed objectives.

Part 1 – Scoping the Project Before Buying
Part 3 – Change Management Before and After Implementation