<?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: The Forthright Negotiator Principle and Creative Ambiguity</title>
	<atom:link href="http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/</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: AdamsDrafting &#187; Blog Archive &#187; A Voice in Favor of Ambiguity?</title>
		<link>http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/comment-page-1/#comment-94702</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; A Voice in Favor of Ambiguity?</dc:creator>
		<pubDate>Fri, 22 Jan 2010 15:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/#comment-94702</guid>
		<description>[...] In particular, that&#8217;s very different from what I refer to as &#8220;creative ambiguity&#8221;—intentionally adding ambiguous language to a contract so that you can, if it works to your advantage, reopen an issue that the other side assumed had been settled. That&#8217;s something I discussed in this January 2009 post. [...]</description>
		<content:encoded><![CDATA[<p>[...] In particular, that&#8217;s very different from what I refer to as &#8220;creative ambiguity&#8221;—intentionally adding ambiguous language to a contract so that you can, if it works to your advantage, reopen an issue that the other side assumed had been settled. That&#8217;s something I discussed in this January 2009 post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamsDrafting &#187; Blog Archive &#187; Contracts as a Relationship-Building Tool</title>
		<link>http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/comment-page-1/#comment-81240</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; Contracts as a Relationship-Building Tool</dc:creator>
		<pubDate>Mon, 09 Feb 2009 16:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/#comment-81240</guid>
		<description>[...] the other side in a deal. When the other side is the enemy, you&#8217;re free to indulge in &#8220;creative ambiguity&#8221; and other [...]</description>
		<content:encoded><![CDATA[<p>[...] the other side in a deal. When the other side is the enemy, you&#8217;re free to indulge in &#8220;creative ambiguity&#8221; and other [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/comment-page-1/#comment-78196</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Thu, 15 Jan 2009 22:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/#comment-78196</guid>
		<description>Ken:

There a tactic that relies on this rule and that is useful when confronted with a counter-party who won&#039;t negotiate away an ambiguous statement. Simply send an email to them confirming that the such-and-such clause means X, not Y, then print their answer confirming that fact and file it with your copy of the contract. It&#039;s almost as good as changing the words in the document, but most people won&#039;t think twice about the email.

Chris Lemens</description>
		<content:encoded><![CDATA[<p>Ken:</p>
<p>There a tactic that relies on this rule and that is useful when confronted with a counter-party who won&#8217;t negotiate away an ambiguous statement. Simply send an email to them confirming that the such-and-such clause means X, not Y, then print their answer confirming that fact and file it with your copy of the contract. It&#8217;s almost as good as changing the words in the document, but most people won&#8217;t think twice about the email.</p>
<p>Chris Lemens</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/comment-page-1/#comment-78055</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Wed, 14 Jan 2009 18:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/13/forthright-negotiator-and-creative-ambiguity/#comment-78055</guid>
		<description>I agree Ken - creative ambiguity is bad lawyering. No client will ever thank you for getting them involved in litigation over a contractual misunderstanding. If the client thinks it means Y, and the other side thinks it means X, you have messed up badly. If you know this is the case, or if you engineer it deliberately to avoid a negotiation, you deserve to be sued - however difficult you think that negotiation will be and however long it make take.

My only caveat is that if your client is aware of the ambiguity and the potential consequences, then they are free to take that risk - it may be a very small one. I would never advise a client to take that route though, because the &quot;positive&quot; result still involves litigation. I don&#039;t think they would be impressed by my professional standards if I suggested it, either.

Also, does anyone have any views about whether the doctrine of mistake would apply to this kind of scenario (assuming it applies in the US as it does in the UK)? It would seem generally relevant, but perhaps it does not apply if there is a contract that can be interpreted objectively?</description>
		<content:encoded><![CDATA[<p>I agree Ken &#8211; creative ambiguity is bad lawyering. No client will ever thank you for getting them involved in litigation over a contractual misunderstanding. If the client thinks it means Y, and the other side thinks it means X, you have messed up badly. If you know this is the case, or if you engineer it deliberately to avoid a negotiation, you deserve to be sued &#8211; however difficult you think that negotiation will be and however long it make take.</p>
<p>My only caveat is that if your client is aware of the ambiguity and the potential consequences, then they are free to take that risk &#8211; it may be a very small one. I would never advise a client to take that route though, because the &#8220;positive&#8221; result still involves litigation. I don&#8217;t think they would be impressed by my professional standards if I suggested it, either.</p>
<p>Also, does anyone have any views about whether the doctrine of mistake would apply to this kind of scenario (assuming it applies in the US as it does in the UK)? It would seem generally relevant, but perhaps it does not apply if there is a contract that can be interpreted objectively?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

