<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Simplifying Contracts</title>
	<atom:link href="http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Eric Goldman</title>
		<link>http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/comment-page-1/#comment-2529</link>
		<dc:creator>Eric Goldman</dc:creator>
		<pubDate>Wed, 14 Feb 2007 21:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/#comment-2529</guid>
		<description>I agree with Mike F., but I also think this issue is linked to your recent post on termination for convenience clauses.  As a vendor, give me a few key paragraphs (termination for convenience, liability limits) and I can dispense with lots of other provisions without any loss of clarity or certainty.  Viewed from this perspective, many contracts are horribly, unnecessarily bloated, resulting in unnecessary transaction costs (and lost deals).  Eric.</description>
		<content:encoded><![CDATA[<p>I agree with Mike F., but I also think this issue is linked to your recent post on termination for convenience clauses.  As a vendor, give me a few key paragraphs (termination for convenience, liability limits) and I can dispense with lots of other provisions without any loss of clarity or certainty.  Viewed from this perspective, many contracts are horribly, unnecessarily bloated, resulting in unnecessary transaction costs (and lost deals).  Eric.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fleming</title>
		<link>http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/comment-page-1/#comment-2508</link>
		<dc:creator>Michael Fleming</dc:creator>
		<pubDate>Tue, 13 Feb 2007 16:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/#comment-2508</guid>
		<description>I think Mike&#039;s comment has much merit.  That said, my thinking is that we&#039;ve still not done enough to prove that the cost of obtaining certainty does not outweigh the costs imposed on the client&#039;s overall business goals. Even if one contract out of a hundred goes really bad, does the litigation from that one kill all of the benefits obtained from the other 99?  If we&#039;d sought certainty in all of our contracts, would we have ended up with only 50 deals instead of 100? If we&#039;d gotten 50 incremental more deals by using small contracts, are the profits from the extra deals going to outweigh the litigation costs from the one bad deal? In all, why is retaining risk &lt;i&gt;necessarily&lt;/i&gt; a bad thing for every one of our clients?

(Clients are just as guilty as the lawyers in many aspects of the above -- I&#039;m not blind.  I toss the questions out for debate though...)</description>
		<content:encoded><![CDATA[<p>I think Mike&#8217;s comment has much merit.  That said, my thinking is that we&#8217;ve still not done enough to prove that the cost of obtaining certainty does not outweigh the costs imposed on the client&#8217;s overall business goals. Even if one contract out of a hundred goes really bad, does the litigation from that one kill all of the benefits obtained from the other 99?  If we&#8217;d sought certainty in all of our contracts, would we have ended up with only 50 deals instead of 100? If we&#8217;d gotten 50 incremental more deals by using small contracts, are the profits from the extra deals going to outweigh the litigation costs from the one bad deal? In all, why is retaining risk <i>necessarily</i> a bad thing for every one of our clients?</p>
<p>(Clients are just as guilty as the lawyers in many aspects of the above &#8212; I&#8217;m not blind.  I toss the questions out for debate though&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/comment-page-1/#comment-2506</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 13 Feb 2007 13:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/02/13/simplifying-contracts/#comment-2506</guid>
		<description>It&#039;d be interesting to see the contracts.  Whenever I see &quot;contract simplification&quot; arguments made, I can&#039;t help but think, &quot;what they&#039;ve done is not made it simpler, but rather difficult to know anything with any certainty.&quot;  While they&#039;re certainly right that &quot;certainty&quot; in some things is &quot;illusory,&quot; how often is that really the case?  But, really, people don&#039;t draft contracts because they like to draft contracts.  People draft contracts to avoid 1) mutual assured destruction of the relationship (contra the foundational principle of the simplified approach) and 2) really, really expensive time spent arguing the details in litigation.

In any event, this contract simplification scheme seems to essentially be a &quot;master&quot; + &quot;statement of work&quot; arrangement.  The master agreement, rather than being negotiated, is derived from 1) common law 2) standard contract rules (UCC, various treaties, etc) 3) course of dealing 4) good faith.  To me, that&#039;s a litigator&#039;s dream (or is it nightmare) come true.

One last point.  It&#039;s been my experience that where there is already a good working relationship, contracts don&#039;t matter much at all anyway.  The problem is getting to that point in the first place (and contracts are usually necessary at that point).  Those previous contracts then become the foundation for the course of dealing and essentially foster the scheme they describe.  If that&#039;s there point then nothing new.</description>
		<content:encoded><![CDATA[<p>It&#8217;d be interesting to see the contracts.  Whenever I see &#8220;contract simplification&#8221; arguments made, I can&#8217;t help but think, &#8220;what they&#8217;ve done is not made it simpler, but rather difficult to know anything with any certainty.&#8221;  While they&#8217;re certainly right that &#8220;certainty&#8221; in some things is &#8220;illusory,&#8221; how often is that really the case?  But, really, people don&#8217;t draft contracts because they like to draft contracts.  People draft contracts to avoid 1) mutual assured destruction of the relationship (contra the foundational principle of the simplified approach) and 2) really, really expensive time spent arguing the details in litigation.</p>
<p>In any event, this contract simplification scheme seems to essentially be a &#8220;master&#8221; + &#8220;statement of work&#8221; arrangement.  The master agreement, rather than being negotiated, is derived from 1) common law 2) standard contract rules (UCC, various treaties, etc) 3) course of dealing 4) good faith.  To me, that&#8217;s a litigator&#8217;s dream (or is it nightmare) come true.</p>
<p>One last point.  It&#8217;s been my experience that where there is already a good working relationship, contracts don&#8217;t matter much at all anyway.  The problem is getting to that point in the first place (and contracts are usually necessary at that point).  Those previous contracts then become the foundation for the course of dealing and essentially foster the scheme they describe.  If that&#8217;s there point then nothing new.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

