How it all happened

Phase 1, Step 1:
Deciding what oneNDA should include and exclude

As a starting point, we took an NDA provided to us by international contracting standards organization the World Commerce & Contracting (WCC). The WCC applied natural language processing and pattern recognition to approximately 2000 NDAs to come up with a balanced template which included all of the clauses which passed a certain frequency threshold. We shared the WCC NDA template (and a research paper outlining their methodology) with the SteerCo, and on 21 March, brought them all together to get to work.

‍

To prepare for the meeting we broke the WCC NDA out into its composite functions. As lawyers, we tend to take a words-first approach and consider the function of a clause later. We flipped that on its head to ensure we focussed on what should and should not be included from a functional perspective and avoid any drafting hang-ups.

‍

Splitting the SteerCo into small teams of 4 or 5, we provided them with an online kanban board containing each of the composite functions (e.g. “tells us what the governing law is”). In their groups, we asked them to decide which functions should be:
   a) Included in the baseline document
   b) Included but variable
   c) Optional
   d) Excluded

‍

Behind the scenes we gathered all of the results and calculated the percentage of votes for each function. The results showed a general consensus of 80% or higher amongst SteerCo members as to what should and shouldn’t be included. Where there were contentious points, further more in-depth discussions were had before final decisions were made.
The result? After starting with a total of 57 functions we ended up with just 24. The excluded functions were sent to the oneNDA Graveyard.

Phase 1, Step 2:
Drafting the clauses and voting

Once we had our list of functions we held a Design Workshop with the Drafting Group to put these into clauses in a format that we thought would add the most value to the predominant users of the document. Prior to the workshop, we conducted a survey that informed us that in 75% of the respondent organisations, the main NDA users were business stakeholders with no legal background.

‍

We ended up with a total of 5 clauses and a firm decision to keep the drafting plain and simple to serve the relevant audience. The Drafting Group was then tasked with writing the wording for each clause, according to the following drafting principles:

‍

• Plain English, no legalese - to secure the widest adoption, this NDA needed to be understandable to as many people as possible.
• Modular: no interdependencies - to make the final document easy to follow and to enable oneNDA to be iterated on and added to in the future, each clause needed to be capable of working independently of the others.
• Active voice: to make it as clear and concise as possible e.g. ‘lawyers love law’ not ‘law is loved by lawyers’.
  
• User-centric: this whole initiative is underpinned by design thinking. Given that the main users of NDAs are business stakeholders, this document needed to work for them first and foremost.

‍

Once drafted, the clauses were put to the rest of the SteerCo, who were asked to vote for their first and second choice version of each clause. To remove any potential for bias, we anonymised all of the Drafting Group’s submissions so the Committee voted without knowing which firm had drafted which clause.

Phase 1, Step 3: finalising v0 of oneNDA

Phase 1, Step 3: finalising v0 of oneNDA

Pillar 1: Protect

Pillar 1 was about creating a set of rules that would govern the usage of oneNDA, to make sure the integrity of the document and the oneNDA brand is maintained. We wanted to make sure that when someone signs a oneNDA, they can feel secure knowing that they are signing a fair agreement from a trusted source.

‍

After much discussion we came up with only one rule - leave it be.

‍

That means:

• Don’t change anything in the body of the agreement, just the ‘variables’. If you change any of the text in the rest of the agreement, you’re no longer able to call it ‘the oneNDA’.
• If you change the branding or add your own, you’re no longer permitted to call it ‘the oneNDA’.
• You also agree that oneNDA comes as is, without any warranty at all. No one involved in writing, reviewing, or improving oneNDA will be liable to you for any damages related to this license or use of oneNDA, for any kind of legal claim.
  
• By using oneNDA you also agree to be bound by the Creative Commons License. You may share, copy and redistribute the material in any medium or format as long as you don’t change it.

Pillar 2: Adopt

oneNDA can only be successful if people and organisations buy in, adopting the document of internal use. We decided to encourage organisational adoption through brand awareness, transparency in all our processes and getting endorsement from credible established bodies. 

• Brand awareness: You can’t use something you don’t know exists. We used various forms of media to spread the word. Our SteerCo oneNDA champions amplified our reach, with the help from many other proponents of the initiative, eager to see change and be a part of it.
• Transparency: To make adoption as easy as possible, and pre-empt reservations, we maintained complete transparency about the document and the process that we took to arrive at the current version by creating this Project Summary report, keeping a "graveyard” of excluded clauses, and creating a user guide.
  
• Endorsement: We reached out to a number of key bodies in the industry to get their accreditation for oneNDA.

Pillar 3: Iteration 

We invited the legal community to provide feedback and suggestions on v0 of oneNDA on a community feedback board. Using a system where participants could suggest feedback, or as we called them “snags”, vote on suggestions made by others, and comment on suggestions to join the conversation, we gathered an incredible amount of comments (over 28 pages from 1200 contributors) and discussion from the oneNDA Club members.

‍

We aggregated this feedback, paying special attention to those suggestions with considerable support (or votes), and fed them back to the SteerCo for another round of revisions.

All of the work outlined above led us to the final phase of the project - Phase 3: The Launch.

On 2nd August we launched version 1 of oneNDA with the supporting documentation to the wider oneNDA Club and the general public. 

The enthusiasm and commitment of the oneNDA community has been a real driving force to get us to where we are today. And so, we’re asking one more time for everyone's support to get oneNDA officially adopted in their organization. 

‍

It is a no-brainer that the more companies that adopt oneNDA, the less time everyone has to spend on pointless negotiations, the more time we’ll all have to add true value to our companies and to the legal community as a whole. Likewise, the more organizations use oneNDA, the more validity it will have in the legal community, in turn leading to further adoption by others. 

‍

Standardisation practices have been successfully working for years. An iPhone will look like an iPhone no matter where in the world you are. Why can’t the NDA be the same?

‍

Remember - this is just the beginning. Together, we’ve shown how much can be achieved when the legal community pulls together toward a common goal. After this, we’ll be gearing up for the next standardisation challenge so watch this space!