I have a mixed relationship with the law-school world. On the one hand, an increasing number of instructors use MSCD as a course text. On the other hand, people from law schools are among the most ardent defenders of traditional contract language that I have encountered.
So I was interested to see this post on ContractsProf Blog by Nancy Kim, professor at California Western School of Law. She uses her post to bring to our attention two “great new resources,” only one of which is relevant, namely a law-review article entitled Say the Magic Word: A Rhetorical Analysis of Contract Drafting Choices (here). It’s by Lori Johnson, assistant professor at the William S. Boyd School of Law, University of Las Vegas. Nancy’s post and Lori’s article gave me the opportunity to consider the mindset of the law-school traditionalist.
First, let’s consider some of what Nancy has to say:
One of my pet peeves is when contract drafting stylists advocate the modification or even wholesale deletion of contract terms without understanding their underlying purpose simply because it “sounds better.” Johnson explains why it’s important to distinguish between legalese without substance (words such as heretofore, whereas, etc.) and legal terms that have a substantive purpose. I found this article to be refreshing because it focuses on the substance of contract clauses, not just drafting style, with the ultimate goal of protecting the client’s interest.
The next time Nancy trashes someone’s work, it would be helpful if she were to name names. It might be grandiosity on my part, but I’m confident that I’m one of the “contract drafting stylists” that Nancy is referring to. And the readers who sent me a link to Nancy’s post were evidently also under the impression that I was one of Nancy’s targets. After all, there aren’t many of us out there who focus on contract language, and I plead guilty to advocating doing away with plenty of traditional usages. And Nancy is certainly aware of me, as I posted a comment on her 2013 post about the traditional recital of consideration (here) and she posted a comment on my 2013 post about represents and warrants (here).
It’s bemusing to have Nancy dismiss me and others as “contract drafting stylists,” and to have her say that we offer analysis of contract usages “without understanding their underlying purpose simply because it ‘sounds better.’” Anyone who thinks that what I do is limited to prettying up contract prose hasn’t been paying attention. And aside from a few stray references in MSCD, nowhere do I invoke the “sound” of a usage as being relevant. How, for example, does “sounding better” factor into my 10,000-word analysis of represents and warrants? And does that analysis suggest to anyone that I don’t understand the issues involved?
Nancy could have done a methodical critique of my work, pointing out all its weaknesses. If she had wanted a model for how to do that, she could have done worse than consult my article on represents and warrants (here). Or my recent article about a Second Circuit opinion (here). Or my review of Gulati and Scott’s The Three and a Half Minute Transaction (here).
But apparently Nancy has no credentials as a commentator on the building blocks of contract language and has no interest in acquiring any. Instead, she’s the sort of person who’s willing to offer advice on the law of consideration without even knowing how that law relates to guaranteeing someone else’s debt (see my second comment to her post on the traditional recital of consideration).
***
Now, let’s move on to Lori Johnson. Last year Lori contacted me to ask if she could speak with me in connection with an article she was writing, namely the one Nancy mentions. So I spoke with her, and in the article she thanks me for my time and insight.
A little less than a year ago I noticed that the article had come out, but I didn’t get around to looking at it until a few months later. When I did, I was surprised to find that my works were cited copiously, but with the aim of showing that my approach to contract language is wrongheaded.
At the time, I briefly contemplated doing a blog post about Lori’s article, but I quickly decided against it. For one thing, under normal circumstances I pick targets with a substantial presence in the marketplace of ideas. But more to the point, her article is a hot mess, a farrago of … something. It would have taken a lengthy blog post to explain why, and such a blog post would have been a chore to write and, more importantly, a chore to read. And that hasn’t changed. If you want to read Lori’s article, complete with Coleridge epigraph, “the Burkean pentad,” Michel Foucault, and the rest, go right ahead, but unless forced to, I don’t plan on spending any further time on it. Coming from me, that’s saying something.
And I suggest to Lori that in law-review articles, it’s best not to attempt to bolster one’s reasoning with invective. In her article, we advocates of a more modern approach are guilty of “touting the manifest benefits of ‘plain English.’” Ours is a “blinkered focus” that lacks “thoughtful analysis.” We “cling to plain language.” She has me “bemoaning” something. My skin is plenty thick enough to withstand such stuff, but it undermines a writer’s credibility. In my articles, I try hard to be clinical.
***
Faced with having my work denigrated by law-school traditionalists, one offering nothing by way of analysis and the other offering a lot of nothing, I thought it might be helpful for me to summarize my approach to use of terms of art.
Yes, contract language is full of terms of art. Some are unavoidable; some are more trouble than they’re worth. To determine in which category a given term of art falls requires analysis. It’s not for the faint hearted—hence, for example, the length of my article on represents and warrants.
In any such analysis, I assess how confusing a term of art is, how coherent the explanations offered for its function are, and what the alternatives are. If a term of art is sufficiently confusing, and if a plausible alternative presents itself, it makes sense to ditch the term of art in favor of the alternative. What courts have had to say about a confusing usage is of limited relevance. If courts are regularly faced with having to decide what a given usage means, it might well be self-defeating to insist on keeping that usage in contracts. I don’t want to build contracts with confusing usages; I want to avoid fights, not win them.
That’s why it’s a canard to suggest that my work isn’t concerned with “the client’s interest.” Clarity isn’t a nice abstraction. If your contracts aren’t clear, you waste time and money and you get into fights. It’s that simple. Clarity, saving time and money, and avoiding risk go hand in hand.
Given how much I’ve written over the years about the obvious usages—including represents and warrants, best efforts, and indemnify and hold harmless—and given that no one has offered meaningful counterarguments, I’m comfortable that in terms of scholarship, those battles have been won.
But we’re dealing with trench warfare, usage by usage. The Trademark Reporter recently published my article on use of inures to the benefit in trademark licensing (I’ll put it on my blog before the end of the year). In the next couple of weeks I have to write another article about a different kind of provision. And I’ll probably keep producing such analyses for a good many more years. Doubtless I’ll get some stuff wrong, initially. When that happens, I welcome those of you in the marketplace of ideas—even Nancy and Lori, if they have the urge—to tell me exactly where I’ve gone wrong.
Ken writes: “[Professor] Nancy [Kim] could have done a methodical critique of my work, pointing out all its weaknesses. *** But apparently Nancy has no credentials as a commentator on contract language and has no interest in acquiring any.”
Whoa — easy there, hoss. Nancy Kim’s implicit mention of you (which I agree it probably was) was just a lead-in to her citation of Lori Johnson’s piece; it didn’t demand to be supported by her own “methodical critique” of your work.
As to Kim’s having “no credentials as a commentator on contract language,” her c.v. suggests otherwise — see https://www.cwsl.edu/faculty-staff-and-campus-directories/faculty-and-staff-directory/n/nancy-s-kim
————–
Ken writes: “Doubtless I’ll get some stuff wrong, initially. When that happens, I welcome those of you in the marketplace of ideas—even Nancy and Lori, if they have the urge—to tell me exactly where I’ve gone wrong.”
I think Lori Johnson tried to do just that in her piece. Sure, in a couple of places she uses language suggesting that she really does disagree with you on some points. But I don’t think it’s fair for you to “suggest to Lori that in law-review articles, it’s best not to attempt to bolster one’s reasoning with invective”; I didn’t read her piece as doing what you claim.
True, on first reading (which is all I’ve done so far), I’m baffled by Johnson’s discussion of the “Burkean pentad,” with which I’m not familiar. But then my brain just doesn’t grasp literary theory, so for all I know I’m like the tone-deaf guy who will never “get” the beauty of music.
The marketplace of ideas, which you’ve mentioned before, can be like one of those tumbling-cylinder rock polishers: Collisions will happen.
What a surprise to see you here, D.C.! ;-)
I’m not suggesting that as a general matter you can’t offer an opinion about someone’s work unless you bring all your resources to bear on it. But what she had to say was so off the mark that I thought it worth noting. Furthermore, as a practical matter, you can’t begin to tackle contract language without immersing yourself in detail.
As to her qualifications, I was referring to the sort of thing I do, not the wide world of contracts generally. To make that clear, I revised that sentence to refer to “the building blocks of contract language.”
Regarding Lori’s article, I’m a commentator but I’m also a plain old reader, and after a point I don’t have the time or patience to figure out what an author might have said instead of what they actually did say. Perhaps I’ll return to it with more patience when I next write about time is of the essence. Others might make more headway.
Regarding Lori’s turn of phrase, my point is a relatively subtle one. I’m not suggesting that she was gunning for me; I’m sure she wasn’t. But invective is different from argument, in fact detracts from it. I’m careful about when I wield “bemoaning.”
Add me to those who can’t hack literary theory. My accomplished brother-in-law traffics in the stuff, and he long ago learned that I didn’t make for an informed audience. But to my mind, it’s best to think of contract language as analogous to software code and not as a vehicle for rhetoric. It would take more than Lori’s article to show me that I’m mistaken.
Yes, the marketplace of ideas is a contact sport. But I have a sentimental attachment to the notion that it’s best that it operate efficiently. Anyone who shows me, rationally and in a way that I can understand, that I’m wrong will find me truly grateful.
Ken, from my perspective, your work provides a benchmark of drafting guidelines against which to judge contract drafting. I don’t always follow that benchmark, eg in the heat of negotiations. Nor do I always follow the values that underly the benchmark, eg if I want the drafting to “win” in court rather than focus on avoiding disputes. But none of this detracts from the great service you provide to the contract drafting community by offering your drafting guidelines and their underlying set of values.
Given how long you have been working on these principles, and the skill with which you have done so, it is rare that one will find a situation where you can be shown to be “wrong” within the parameters that you have established.
Others are entitled, of course, to put forward different benchmarks and different underlying values, though few have done so with such expertise.
I happen to think that it would be very difficult for an academic lawyer, as distinct from someone with experience of practice, to offer a credible, alternative set of benchmarks and values.
I don’t think Lori Johnson’s article surmounts those difficulties. I am not qualified to comment on whether it is successful when judged by the values of the academy, but from a practitioner perspective I think its value is limited.
Intending no disrespect to her, I wonder whether you realise how senior and respected you are within the legal community? You are the practitioner equivalent of the Dean of a prestigious law faculty, compared with someone who is, I imagine, at a fairly early stage of their career in a respectable law school (ranked 67th in the US). I don’t think it undermines your credibility to have junior academics write articles of this kind.
Thank you. I don’t regard any of this as a threat. I’m simply an incorrigible commenter on the contract-drafting scene. I also like an efficient marketplace of ideas. As I mentioned in my post, I hadn’t intended to say anything about Lori’s article, but once it made its way into the marketplace, it didn’t seem out of place for me to say what I thought about it, without any malice (but with a good measure of bemusement).
That said, I’d much rather write about within.
Having been forward that reading Ms. Johnson’s article may be less than a fruitful use of my time, I started to wade into it. I quickly had flashbacks from college literature classes where, earnest grad students turned the grandiloquent words of Proust and turned them into equations. No, really. Ms. Johnson should spend a year in government contracts to see just how desperately the concision and precision of contract drafting advocated in this blog are needed.
*Having been forwarned . . .
It seems to me the disagreement simply is broken down to pragmatist v idealist. Sure, Lori’s spreadsheets full of case law canvassing all the terms of art in a contract might increase the likelihood of winning a case by a few fraction of a percent, but 9/10 clients are going to be far more impressed with a clearly written and accessible agreement that will reduce the likelihood of a costly dispute.
On various levels, Lori’s notion of a caselaw roadmap is a fantasy.