<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chris Webb&#039;s Publishing Blog &#187; non-compete</title>
	<atom:link href="http://ckwebb.com/tag/non-compete/feed/" rel="self" type="application/rss+xml" />
	<link>http://ckwebb.com</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 15:40:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Author Advice: The Non-Compete Clause</title>
		<link>http://ckwebb.com/publishing/books-and-writing/author-advice-the-non-compete-clause/</link>
		<comments>http://ckwebb.com/publishing/books-and-writing/author-advice-the-non-compete-clause/#comments</comments>
		<pubDate>Fri, 01 Jun 2007 00:25:25 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Books and Writing]]></category>
		<category><![CDATA[author-advice]]></category>
		<category><![CDATA[non-compete]]></category>
		<category><![CDATA[non-compete-clause]]></category>
		<category><![CDATA[publishing-contracts]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.ckwebb.com/books/author-advice-the-non-compete-clause/</guid>
		<description><![CDATA[I&#8217;ve been having a great discussion with a new author about the non-compete clause and I thought I would share my thoughts on the subject.  Let&#8217;s start with the reality of the non-compete:

Most publishers have one in their contracts
Most publishers will not remove it from their contracts

So end of story, right?  Well, not exactly.
Let&#8217;s start [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been having a great discussion with a new author about the non-compete clause and I thought I would share my thoughts on the subject.  Let&#8217;s start with the reality of the non-compete:</p>
<ol>
<li>Most publishers have one in their contracts</li>
<li>Most publishers will not remove it from their contracts</li>
</ol>
<p>So end of story, right?  Well, not exactly.</p>
<p>Let&#8217;s start with the Publisher&#8217;s viewpoint.  Look, its tough out there &#8211; the competitive nature of the marketplace continues to increase, online content is eating away at opportunities for traditional publishing models, and with nearly 200,000 new books published each year we have enough competition to worry about without our authors pitching in.  We need the non-compete in place as a reasonable measure to protect our business interests, and the investments we make in our authors.</p>
<p>And from the Author&#8217;s perspective:  Look, its tough out there -  the advent of blogging, user-generated content and accessible tools makes it easier than ever for almost anyone to publish content.  Be it online, in journals, magazines, subscription-based websites or any number of other venues, Authors have many opportunities to write and generate income and can&#8217;t be hamstrung by a non-compete clause.  Besides, the non-compete is only one way &#8211; the publisher can still publish whatever they want so why can&#8217;t I?</p>
<p>There are valid arguments on both sides, and I certainly understand both viewpoints.  I also understand that Publishers need to continue to create new content models to replace the current ones to remain competitive or even valid in the post Web 2.0 landscape.  However, the non-compete clause in today&#8217;s publishing contracts is (or should be) considering books and books alone.</p>
<p>If your non-compete clause is so broad that it effectively prohibits you from doing anything around the subject of your book without getting your publisher&#8217;s approval, it&#8217;s probably too general.  The language of the clause may look something like:</p>
<blockquote><p>The author shall not produce any work similar to the proposed Book that may in the Publisher&#8217;s judgment be competitive with or harm the sales of the Book.</p></blockquote>
<p>Pretty restrictive, huh?</p>
<p>Here is my opinion,  and how tend to treat the non-compete in my contracts (my company does allow it&#8217;s editors some flexibility in this respect.)  <strong>I want you </strong><em><strong>writing </strong></em><strong>about the topic of your book.</strong> I want you blogging, writing articles for magazines, websites, and any other place you can.  I want you speaking at conferences, giving lectures and teaching.  Heck, I&#8217;ll even grant you the rights to use a portion of the materials from your book in most of these situations as long as you give it credit.  Ill supply you with cover images, flyer&#8217;s to hand out and in some cases Ill even have a poster or banner made for you for a big conference if it will help you sell your book.  I want you to tell the world about what you do, and about the great book you wrote all about it.</p>
<p><strong>But, I don&#8217;t want you writing a<em> book </em>about it for someone else</strong>.   Not exactly like it anyway, and here is where the flexibility comes in.</p>
<p>When dealing with non-compete clauses, ask to work with your publisher to try and narrow the breadth of the clause in such a way that the publisher&#8217;s interests are still reasonably addressed, but allows you to continue to do what you do.  Discuss the fact that you are really talking about book-length works, not smaller articles.  Be sure to mention the work you do on your blog, or in the course of your normal business that you need to address.  I have language I can use in my contracts that addresses all of these things as necessary, and I generally rework the non-compete in such as way before I even present it to an author.</p>
<p>Authors should not want to compete with their own books &#8211; that&#8217;s not good for anyone involved in the partnership.  But if you do think you will write other books, or want to be open to other opportunities be sure to  discuss that with your editor.  For example if you are writing a beginning level book on JavaScript you might want to discuss limiting the non-compete to other beginning level JavaScript books.  Could you write an advanced JavaScript book, or perhaps an Ajax title?  Maybe, if you and your publisher agree to rework the non-compete a bit, but it has to be agreed upon by both parties.</p>
<p>A publishing agreement should be a partnership, and if an editor is doing his or her job it should be part of an ongoing relationship with the most valuable asset any publisher has &#8211; its authors.  If both parties are reasonable and understand the other&#8217;s viewpoint a compromise can often be made that works for everyone.</p>
<p>By the way, I worked with the new author I mentioned at the beginning of this post exactly as I described above.  We now have a non-compete clause that we are both comfortable with, a new book to work on, and a new partnership to grow.</p>
]]></content:encoded>
			<wfw:commentRss>http://ckwebb.com/publishing/books-and-writing/author-advice-the-non-compete-clause/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
