A contract playbook is a document that tells your colleagues -- whether they are lawyers or not – how to handle the entire lifecycle of a contract by using a playbook. Learn how to create a playbook and leverage friendly, user-experience criteria.
One well-known expert defines a contract playbook as a document that “breaks down the company’s standard contract terms, sets out an explanation of each clause along with fallback clauses (i.e., variations of the standard clauses that the company would accept if the customer wants to negotiate a standard clause), and notes when the company will ‘walk away’ from a contract…A properly prepared contract playbook allows the legal and business teams to stay aligned and close contracts faster or (or know when it’s time to walk)”1
For the planning meeting, you’re going to need more than just your laptop and a notepad. In fact, you’ll have to put your laptop and other electronic devices away. You can ask people to leave them at their desks or to have them turned off or on silent if they need them in the room. There are a few reasons for this.
Stick with a two-hour limit. You’ll need about two hours with the legal team to fully “bake” an MVP. If you only have one hour, you can still start the process. But for more complicated agreements and contract types, you’ll need a meaningful chunk of the day. Give everyone who’s included advance notice so they can plan accordingly and don’t go over the two-hour time limit.
Remember, you’re only designing an MVP. You can reiterate later. The point isn’t to have a long meeting but to have a productive one. You’ll need enough time to run through the exercise, and talk about all the major points, but you don’t need to overanalyze everything.
Using tangible supplies is a great way to bring people out of their screens and into an interactive environment. We’ve also found that this type of environment is different from what legal teams are used to -- and it’s a great way to rearrange an otherwise boring meeting.
Large yellow sticky notes
A playbook design involving a complex contract playbook requires several heavily negotiated legal concepts and provisions.
From here, let the meeting flow naturally. Engage the team and allow the moderator to guide the discussion in the right direction. Stack the sticky notes, identify opportunities to streamline, and extract! After the meeting, outline the results, take photos of the board, and share. Remember the goal: In a limited amount of time, ask as many questions as possible and encourage the team to share.
Review all high-level issues first and follow up by digging into each issue. Working each issue one by one can be difficult, especially if you want to image the forest (big picture) now. Looking at the forest and then the trees can help correlate related legal concepts. Many organizations are available that can help you create the contract playbook once you’ve conducted your planning meeting.
Lots more to share here - we love meeting with our customers to configure algorithm-enabled playbooks. Our team of lawyers meet with clients to moderate a playbook design session and offer a method for implementing a playbook.
At this point you need to add meaningful user experience criteria to contract playbooks that puts words above into action.
Remember, the planning session should be relatively short (no more than two hours) and engaging. This gives everyone involved an opportunity to have a say in what should be included in the playbook.
Even though creating a playbook an exercise and an important goal, the tangible results of the playbook will be determined by how often it is used and how much time it saves your team.
Therefore, your final goal shouldn't be creating a playbook but implementing a playbook as a tool to save time. So, once you have built a contract playbook, you're halfway through the process. After your playbook is complete, the next step in the workflow is to implement and operationalize it to fit into your strategy and save time without sacrificing quality or accuracy. It all points to users!
The helpfulness of your playbook comes down to your specific user experience criteria which defines how the playbook is to be used day by day. An unfriendly playbook will not be useful and will obviously become pointless.
Don't worry if you are unsure of how to design your playbook for the best user experience, because the design help should come from a legal engineer or designer.
Legal engineers do many things for legal teams, including ensuring that the documents and playbooks they use employ the right user experience. In addition, some legal teams may have a legal engineer responsible for user experience and other operations or processes -- such as automation, data storage, or document processing.
Other teams might rely on a legal designer who is dedicated explicitly to designing legal documents in a way that benefits all stakeholders.
So, whether you call on a legal engineer or a legal designer, you should expect that person to ask and answer several key questions when creating the user experience criteria of your playbook, including the following:
These are just some of the elements that legal engineers and legal designers need to consider when developing user experience for a playbook.
END NOTES:
See how DocJuris can automate your legal, procurement, and sales operations.
✅ Contract review from 8 weeks to 5 minutes
✅ Mitigate risk faster with dynamic playbooks
✅ Become a valued partner