How it all happened
Join thousands of organizations that use our standard template to streamline and automate the NDA process.
Why oneNDA?
Our mission has always been to improve the efficiency of Legal teams through smarter processes, standardisation and technology. NDAs, which are almost always the same but written in different words, fly in the face of that. In fact, in 2020, we discovered that reviewing NDAs for our clients represented 63% of our workload but only 7% of our revenue.
Beyond not being profitable for us, we know from experience how problematic NDAs are across the industry; they’re hugely time consuming for both lawyers and businesses and although low risk, they can be damagingly adversarial at the start of a commercial relationship.
So, on 16 February 2021, we launched an idea: oneNDA. Since our fateful first LinkedIn post, we’ve received an incredible amount of support. To date we have 10,000 people who have engaged with the initiative, spanning 44 countries across the globe.
What happened next
From there, it kind of snowballed... We received an incredible amount of messages from people around the world urging us to go ahead and create oneNDA. So we went ahead and created a simple website over the weekend and invited people to sign up to say that they'd support the initiative if we went ahead. We said that if we could get 100 lawyers to sign up within two weeks we'd go ahead and do it.
We hit that number 12 hours from launch. And the rest is history.
Project timeline
100 signup within 12 hours of site launch
SteerCo created
SteerCo decided what goes into oneNDA
DraftingGroup created the oneNDA language
28 pages of feedback from onNDA community
Version 0 published and out for community feedback
SteerCo voted on their favourite language
Version 1 ready for launch
Over 2,000 downloads in the first week
.svg){kind=icon}
Feedback and iteration for continuous improvement
Our approach
We approached the project in 3 phases:
Baseline NDA
We created and agreed on the text of the oneNDA document itself.
Operationalisation
We determined how to put oneNDA into practice and created the rules to govern its use and protect its integrity over time.
In parallel, we collated feedback from the wider community on the first version of oneNDA.
The Launch
We launched oneNDA alongside a suite of other artefacts that explain how it should be used, when to use it and why not to redline it if you’re on the receiving end. We also asked organisations to formally adopt oneNDA as their internal template.
Phase 1: Baseline NDA
Agreeing the text of one single NDA within 3 months was an ambitious target. To make Phase 1 a success, we needed to call on a subset of the oneNDA community to help craft oneNDA and steer the project.
SteerCo
At the beginning of March 2021, we opened up applications for a small number of in-house counsel to come on board as the oneNDA Committee and a group of law firms to join as the oneNDA Drafting Group. Together, the Committee and Drafting Group were to make up the oneNDA Steering Committee (SteerCo).
We pulled together a group of top in-house counsel from some of the largest and most innovative companies in the world, including Google, Airbus, Adidas, Barclays, Coca-Cola, Deliveroo, UBS and others as well as representatives from globally recognised law firms - including Allen & Overy, Ashurst, Gilbert + Tobin, Linklaters and Slaughter & May.
To ensure oneNDA would be broadly applicable, it was essential that our SteerCo be representative of the entire legal community. To achieve that goal, we made sure to include organisations of varying sizes and industries.
Equally important was taking a consensus-led approach. Other standardisation projects in the past have been less successful because they have sought to disseminate their own template - which, good as it may be(!), doesn’t have the buy-in of the broader legal community. It was key that we were led by the community in the creation of oneNDA.
Research Group
Finally, to inform the creation of oneNDA, we formed a group of Research Partners to provide insights into standardisation, litigation and points of contention in NDAs.
Founding Club
The SteerCo was supported by a broader-still group of early adopter organisations known as the Founding Club, who were passionate about standardisation in the industry. These c.100 Founding Members acted as a sounding board to make sure we were moving in the right direction.
oneNDA Community
The oneNDA community includes all other people who signed up to be a part of the initiative after the 1 March deadline and have interacted with the initiative. This very important group helped us collate community thoughts and feedback and supported the decisions made by the SteerCo by offering a broader view.
Over the months that followed, we worked together to determine what should and should not be included in oneNDA, drafted the clauses and voted democratically on the final result. Here’s how it went down.
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.
%20(1).webp)
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”).
.webp)
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 therefore carefully considered both the business user and the legal user when creating our NDA.
%20(1).webp)
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: Testing v0 of oneNDA
After compiling all of the ‘winning’ clauses into one document and aligning the drafting to make sure they worked as a cohesive document, we sought feedback. First, from the SteerCo, then, from the Founding Club.
Phase 2: Operationalisation
In June 2021, we began Phase 2 of the project. We built off the successes of Phase 1, namely a version0 template version of oneNDA.
There were three main pillars to the Operationalisation phase:
- Protect
- Adopt
- Iterate and Maintain
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’.
- 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 including the Law Society in England.
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.
Phase 3: The Launch
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.
What happens now?
Our objective is to reduce NDA negotiations as much as possible and to do that we need to continue to improve the template, the way it's operationalised and how it's actually utilised on the ground. To do that, we need your input. Head over to the Feedback page and share your thoughts, ideas and suggestions.
Without you, oneNDA wouldn't exist so please continue to support us with your valuable input. Together, we can make this happen 🚀
Sign up to our newsletter
Get all the latest oneNDA news straight to your inbox. Don’t worry, we don’t spam.
