OneNDA

The design of organisations and products →Go uptown Why did it take the legal community two thousand years to come up with this idea? Index: Click ᐅ to expand: Design Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

Quote|SYNOPSIS: Some cheeky little Hobbits form a fellowship and set out on a perilous adventure to confront the fearsome dragon Smarkup made entirely out of boilerplate. First act goes well.}}

In Bozo Baggins’ burrow, there was a carefully hand-painted by his uncle Dildo: The quotidian is a utility, not an asset.

Now, no legal form has more boilerplate than an NDA. To read one is to behold pure, abstracted, essence of boilerplate. Boilerplate is all there is. Yet generations of legal eagles have dug themselves into slit trenches to argue the toss over this quotidian contract. It has been some kind of insane compulsion: not one of them enjoyed it; not one of them saw any point in it; they found themselves compelled to do it; drawn to it like moths to a lamp.

“I must negotiate this NDA, because this is what I do. It is in my nature.”

Kudos, therefore, to the team at TLB for doing something about it.

The JC put his sclerotic old shoulder to the wheel, for whatever that was worth, and commended his friends, relations and readers to do the same; especially those who occupy places in the firmament, or up the fundament, higher than his own.

Start with the NDA, who knows where it may lead?

Later ...

Well, readers, against his darkest suspicions, it looks like this OneNDA thing might work! The working group managed to defend against the inevitable special pleading, committee drafting, the pedantic culpa in contrahendo-style commentariat to which we agents of the tragic commons resort by irrepressible force of habit: through sheer willpower OneNDA generated a nice, simple, pleasant first edition. Not perfect — nothing is — but absolutely good enough.

It’s too early to stand on the poop-deck with a mission accomplished banner, but OneNDA is getting there. So, in a gentle further shove, here some observations about what it could all mean.

Simplification beats technology

A counter-intuitive proposition: if you simplify, you may not need technology. There is no need for automation, document assembly, even a mail merge is probably over-engineering. This is to observe that the conundrum facing modern legal eagles is not one of service delivery, but service in the first place. Fix the content, and the delivery challenges fix themselves.

This leads to a paradox: if you simplify properly, it is easier to apply technology. To design for technology, design for no technology. The fewer options, subroutines, caveats and conditions precedent in your legal forms, the easier you will find it to automate them. You will get all kinds of second order benefits too: fewer complaints, fewer comments, less time auditing your monstrous catalogue of templates.

The JC’s handy aphorism here: first, cut out the pies.

It’s not the form, or even the content, but the consensus that matters

Once upon a time — until 2021 —if you devised your own short-form NDA, however elegant, you could expect it to be rejected or marked up to oblivion by the rent-seeking massive.

Once — okay, if, but here’s hoping — the short-form NDA achieves wide-spread community commitment the dynamic will be different. Those who built it would use it, sure. But those who didn’t would look upon it not with suspicion, but with trust: “this is a community standard: I can get comfortable using it too”. No-one got fired for following the crowd.

OneNDA is a community effort: interested people came from far and wide to help; everyone checked their agenda at the door. This was what Wikipedians call “barn-raising”. The community came together for the greater good of all.

Now once a barn is raised and community feels ownership in it, it is the very fact of the barn, rather than how it was built or what it is made of, that is its value. Community assets accrue to the benefit of everyone. The structure, day one, might not be perfect — is anything? — but nor is there any interest in undermining it, much less setting fire to the roof: it is in everyone’s interest that the barn does the job it was built for. Everyone has skin in the game. The more people use it, the more they are incentivised to make sure it stands. The more people use it, the more “good enough” becomes “perfection”.

Thus, technical complaints that, for example, it refers to “the public domain” and not just “public” — I mean, what a zinger — fall away because (if they didn’t already) everyone knows what it means. If there are ten thousand standard NDAs out there that use the expression “public domain”, then no court (and, frankly, no plaintiff) is going to side with a pedant against the weight, and interests, of community consensus.

The hard lines discourage rentsmithing around the edges

Once that common standard exists, with the hard lines OneNDA has drawn around itself, there is a further subtle advantage: it will dampen peripheral legal-eaglery around small, irritating edge cases (not to mention out-and-out pedantry).

We all know the common fripperies thrown into negotiation of an NDA by way of a dominance display between legal eagles: indemnities; exclusivities; non-solicitation; licencing and so on. Where notices these will quickly be rejected out of hand, the courtship display required to remove them is still tedious and it takes time.

But it is hard to rentsmith without a “host” contract. By drawing hard lines around itself, the OneNDA makes itself unavailable to act as that host. It frustrates the rentsmith. The party wanting them has to create a new agreement for the purpose, but it is not likely to do that for fear of looking stuipid. The standard template discourages peripheral negotiation. This is an additional, unintended benefit.

The knee of the curve

The more a contract costs to negotiate, the fewer of them you can do. There’s no free option if everything is negotatiated.

Adding a free, no-negotiation option creates a range of customers you couldn't afford to onboard, but incentivises marginal cases to take the free option too

Creating a simple and standard alternative has a nice effect, too, on the legal complexity curve. It pulls it down and to the right. These are the directions you want it going in. These fancy charts are stimulations of a real-life situation. The problem: a broken contracting process. Our solution: standardise and automate just the simplest, lowest value contract, leaving the process for the rest untouched. The intention was to reduce the workload of the negotation team, giving them more time to focus on the higher value, more difficult contracts.

The experiment was successful. Ovvernight, half the contract volume was automated. Additional benefits we did not expect were the following:

• Volumes in the automated contract doubled overnight: now it was cheaper, easier to execute, and with guaranteed no errors, the marginal cost went down, so the capacity to execute went up.
• Some “marginal” customers in the adjacent negotiated contract categories elected to move to the free model too: they were happy with the trade off of ”no custom terms” but “contract executed for free and immediately”. Thus the “knee” of the curve deepened and shifted to the right.
• volumes in the higher value negotiated contract categories increased, as the negotiation team had more bandwidth, processed the contracts more quickly and with fewer errors.
• As a result, total output of the team doubled.

The one thing that did not happen was the forced redundancy of the team. They were busier than ever, only on more challenging stuff.

See also

• Confidentiality agreement
• Perfection is the enemy of good enough
• The quotidian is a utility, not an asset