Articles
July 19, 2023
Process mapping is a widely accepted practice in the broader business context as a common tool for improving efficiency and preventing loss when delivering a product. Legal departments, however, can be reticent to requests from vendors and corporate officers when asked to map their legal workflows. That friction comes from perceptions of legal process mapping as a burden on the already limited time of busy lawyers and general counsels. The frustration is understandable but also misses the mark on unpacking the true value of process mapping. Let us explain.
Key Takeaways
Legal operations are inarguably different from other processes, like the production and delivery of a widget, because they involve a high degree of abstract, intellectual work. Sometimes that work results in a finished product, such as an executed contract, and other times it doesn’t (e.g., a simple email responding to a query from HR or sales).
This variance makes standards difficult to capture in a process map because you, as a lawyer, know the deliverable but also realize that facts and events will change your approach. A process map exists in a vacuum. The practice of law does not, and you know that better than anyone. However, legal process mapping is less about the direct benefit to you and your team and more about the indirect benefits from over-communicating and detailing workflows. In other words, you might think of the value as more like the famous line from Jerry Maguire. It’s about finding new ways to “Help me, help you.”
Legal process mapping forces you to visualize every stage of your work as well as the work of those you must engage in completing a project. The benefits can be surprising as you:
To some degree, every legal operation in your department will be worth mapping because it creates a baseline for starting and finishing projects. However, the better question might be how granular should you go with your legal process mapping? You may think of most mapping as a way of showing the big picture, but you may find that more value comes from the most microscopic levels of mapping. You want to articulate clearly the scope of every stage in a process. For example, instead of saying, “send contract to sales team for review,” your map would benefit more from answering the following:
Image from https://americanlegalengineers.org/technical-areas/
The specific workflows and operations you map will depend on the structure and function of your legal department. Remember, it’s not just about what your team does internally but also the legal workflows you manage through external parties (e.g., specialty litigation). Some common use cases could include:
Image from https://www.smartsheet.com/essential-guide-business-process-mapping
As you go about your legal process mapping, here are some considerations to make the most effective use of the experience:
Legal departments are not static entities, and your processes are bound to change as core functions evolve, added compliance obligations arise, and new people enter the department. When significant changes occur, it’s important to see if the situation warrants a modification of your legal process maps. Some possible signals for a good time to review your maps could include:
Outside of special circumstances, you may also consider incorporating reviews of your legal process maps into other standard review periods annually. Even if you don’t think your process changed, glancing at your map may spark a realization about how operations have shifted.
Morae aids the busy and resource-constricted needs of GCs and their legal departments through various key legal operations. We believe in taking the time to understand a legal department by identifying its structure via legal process mapping. By taking on the burden of this administrative task for our clients, we can offer customized solutions in contract management, eDiscovery, and a host of other workflows vital to a legal department’s success. Find out what makes us unique as an ALSP and schedule a consultation with our representatives today.