<?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: Live Happily With a Great Designer</title>
	<atom:link href="http://www.designers-who-blog.com/index.php/archive/seth-godin-designer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designers-who-blog.com/index.php/archive/seth-godin-designer/</link>
	<description>A Design blog for designers, photographers, writers, marketeers, etc., who blog</description>
	<lastBuildDate>Thu, 23 Dec 2010 15:32:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Designers who Blog: Design, Illustration, Photography, Web, Advertising, Branding &#8230;</title>
		<link>http://www.designers-who-blog.com/index.php/archive/seth-godin-designer/comment-page-1/#comment-3356</link>
		<dc:creator>Designers who Blog: Design, Illustration, Photography, Web, Advertising, Branding &#8230;</dc:creator>
		<pubDate>Fri, 21 Jul 2006 08:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.designers-who-blog.com/?p=308#comment-3356</guid>
		<description>[...] A client having their say at any stage of a job is obviously good business practice (and common sense). But face it, at certain stages of a project it creates tension. And in my experience, a jog mid job does not always improved a project. At times it changes from what was a smooth creation, to one with a zerky flaw. But for me, what releases some of the pressure is knowing that it&#8217;s their dime, their project, therefor their right to have a say. And like mentioned in a previous post, you can always  leave it out of the portfolio. [...]</description>
		<content:encoded><![CDATA[<p>[...] A client having their say at any stage of a job is obviously good business practice (and common sense). But face it, at certain stages of a project it creates tension. And in my experience, a jog mid job does not always improved a project. At times it changes from what was a smooth creation, to one with a zerky flaw. But for me, what releases some of the pressure is knowing that it&#8217;s their dime, their project, therefor their right to have a say. And like mentioned in a previous post, you can always  leave it out of the portfolio. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

