Thursday, December 17, 2009
Posted by Jeff Lipshaw
I've been asked to teach our six credit contracts course here next year, and have been puzzling (far ahead of time) about book adoption and teaching philosophy. Contracts is the often the bane of the first year experience, and I am thinking about hitting the reasons head on.
I spent 26 years in practice, as a law firm litigator and then transactional partner, and then as the general counsel of two different companies. I have written fairly extensively on contract theory (perhaps teaching the course will be impetus to combining my various pontifications into a book), but I am generally disdainful of contract doctrine as a means of explaining what is actually going on in the business world. (See my article Models & Games, for example.) Although there are some admirable contracts casebooks out there that attempt to do so, if I don't use one, it will be a result of my concern that pushing traditional contract doctrine into a real business setting is a square peg in a round hole (the metaphor is apt for all sorts of reasons). You don't really teach the business world, and you don't really teach traditional doctrine.
No, were it not for the bar exam and inertia (i.e., Langdell was a contracts teacher), we probably wouldn't bother with most of contract law as we presently teach it. Or, as I have often said, practice is 5% doctrine and 95% interpretation; the course is usually 95% doctrine and 5% interpretation.
I've concluded instead that the way to approach the subject (and relieve some student angst at the same time) is to reject at the outset the idea that what they are learning maps on the real world. It is more helpful to think of contract law as most casebooks begin - with the idea of the objective law of contracts, or, as we say more explicitly in areas like partnership, the default rules upon which the legal consequences of a binding promise will be imposed on parties after the fact when indeed there is no subjective evidence of an intent to be bound at all, or legally, or on what specific terms. (As I have made clear in the past, I'm a skeptic on subjective intent altogether when even the interpretation of the contract is the subject of colorable litigation positions.) Hence, teaching the subject, by my way of thinking, requires a jurisprudential approach, one that says "what you are about to learn is a particular way of modeling human interaction." Said with more jargon, contract law may or may not map well onto the reality of private ordering, and the mistake most students make is to try to make the map work. No - an integrated law of contracts, if one exists, is a figment of the Langdellian or Willistonian or even the Corbinian or Llewellynian imagination, a way of trying to make unified sense of the whole of private ordering, whether that sense-making is by way of formalism or contextualism (or efficiency or the promise principle, to bring the debate forward in time).
Put otherwise, if the reality of private ordering is metropolitan Boston, contract doctrine is a map, based on the mapmaker's view of what is important. But you could have a road map of major highways, a topographic map, a detailed street map, a map of population densities, etc. This is merely one map, or several competing maps. (Think about the classical view of offer and acceptance, for example, versus the UCC's view. Does either one really map onto a singular underlying reality of the making of an agreement? Even "the meeting of the minds" is a metaphor (and, in my view, an unfortunate one)). (I think the Macaulay/Macneil relational contract school falters on this point, by the way. It gives up on the map altogether and tries to go straight to the reality of the relationship. That may explain the relationship, but it may not make for the best way to explain the law. I have a similar reaction to Omri Ben-Shahar's longstanding proposals (now with Lucian Bebchuk) on liability arising out of preliminary negotiations - we're trying to fine tune the map (or model) beyond its usefulness as a model.)
Finally, the difficulty with putting aside whatever sense of reality we might have, and reconstructing the rules of the model (or game?) on their own is a little like trying to master the rules of cricket without making analogies to baseball, or the rules of rugby without making analogies to American or international football. Let's say you are playing cricket, and you do something that cause the other team to cry "foul!" You have to make your argument why what you did was legal in cricket terms, not baseball terms. That doesn't mean there couldn't have been other ways to play cricket, or that the world would be better off if we interpreted the rules of cricket differently, but to win the argument we have to fashion it in a way that appears to be consistent with cricket. Contract law is the set of rules making up the objective contract litigation game, and some arguments based on those rules are cricket, and some are not.
Anyway, that's my current thinking. Responsible opposing (or helpful) views are always welcome.