<?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"
	>
<channel>
	<title>Comments on: How to give good feedback</title>
	<atom:link href="http://www.badlanguage.net/how-to-give-good-feedback/feed" rel="self" type="application/rss+xml" />
	<link>http://www.badlanguage.net/how-to-give-good-feedback</link>
	<description>How to communicate</description>
	<pubDate>Wed, 20 Aug 2008 07:58:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Bad Language / Why good writers (occasionally) produce bad copy?</title>
		<link>http://www.badlanguage.net/how-to-give-good-feedback#comment-25985</link>
		<dc:creator>Bad Language / Why good writers (occasionally) produce bad copy?</dc:creator>
		<pubDate>Thu, 04 Jan 2007 18:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=221#comment-25985</guid>
		<description>[...] Editorial structure.&#160; Good writers need good editors and good proofreaders.&#160; Remedy: see my post How to give good feedback. [...]</description>
		<content:encoded><![CDATA[<p>[...] Editorial structure.&nbsp; Good writers need good editors and good proofreaders.&nbsp; Remedy: see my post How to give good feedback. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bad Language / Want a good website, on time? Prioritise content.</title>
		<link>http://www.badlanguage.net/how-to-give-good-feedback#comment-1054</link>
		<dc:creator>Bad Language / Want a good website, on time? Prioritise content.</dc:creator>
		<pubDate>Wed, 09 Aug 2006 21:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=221#comment-1054</guid>
		<description>[...] Train yourself to give better feedback. [...]</description>
		<content:encoded><![CDATA[<p>[...] Train yourself to give better feedback. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Jacobsen</title>
		<link>http://www.badlanguage.net/how-to-give-good-feedback#comment-956</link>
		<dc:creator>Roy Jacobsen</dc:creator>
		<pubDate>Thu, 03 Aug 2006 12:45:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=221#comment-956</guid>
		<description>This is gold. Thanks for posting it.

Can't recall the number of times I've handed someone my carefully polished draft to have them return it laden with jargon and gobbledegook, rearranged, and with the formatting "improved" (without the use of styles, of course).

I may have to steal this and append it to all of my proposals.</description>
		<content:encoded><![CDATA[<p>This is gold. Thanks for posting it.</p>
<p>Can&#8217;t recall the number of times I&#8217;ve handed someone my carefully polished draft to have them return it laden with jargon and gobbledegook, rearranged, and with the formatting &#8220;improved&#8221; (without the use of styles, of course).</p>
<p>I may have to steal this and append it to all of my proposals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pamela Slim</title>
		<link>http://www.badlanguage.net/how-to-give-good-feedback#comment-945</link>
		<dc:creator>Pamela Slim</dc:creator>
		<pubDate>Tue, 01 Aug 2006 21:21:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=221#comment-945</guid>
		<description>I have lived through the opposite of #1 in more cases than I care to admit.  When I was designing  global training programs for large corporations, I often found myself in the role of lightning rod/mediator for different factions of the organization who couldn't agree on anything.

I finally learned to do careful planning with new clients in advance to ensure that we had a single point of contact for feedback who had (and this is the critical thing) actual decision-making power in the organization.  Often the client who brings you in is not this person, so work with them to find out who is before you put pen to paper and go through 32 excrutiating stages of drafts, only to end up something so incomprehensible or watered-down that you don't want to attach your name to it.

One moment I am not proud of ... walking through a document line by line in a live meeting with a global management team and fielding 12 different opinions on edits.  Agonizing is too mild a word to describe it.

This post should be required reading for anyone hiring a writer.  Amen to you.

All the best,
-Pam</description>
		<content:encoded><![CDATA[<p>I have lived through the opposite of #1 in more cases than I care to admit.  When I was designing  global training programs for large corporations, I often found myself in the role of lightning rod/mediator for different factions of the organization who couldn&#8217;t agree on anything.</p>
<p>I finally learned to do careful planning with new clients in advance to ensure that we had a single point of contact for feedback who had (and this is the critical thing) actual decision-making power in the organization.  Often the client who brings you in is not this person, so work with them to find out who is before you put pen to paper and go through 32 excrutiating stages of drafts, only to end up something so incomprehensible or watered-down that you don&#8217;t want to attach your name to it.</p>
<p>One moment I am not proud of &#8230; walking through a document line by line in a live meeting with a global management team and fielding 12 different opinions on edits.  Agonizing is too mild a word to describe it.</p>
<p>This post should be required reading for anyone hiring a writer.  Amen to you.</p>
<p>All the best,<br />
-Pam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roman Rytov</title>
		<link>http://www.badlanguage.net/how-to-give-good-feedback#comment-932</link>
		<dc:creator>Roman Rytov</dc:creator>
		<pubDate>Tue, 01 Aug 2006 12:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=221#comment-932</guid>
		<description>Great list. We've discussed recently this topic. David Maister posted "getting good at GETTING feedback" and I put my thoughts on the other side of the coin here: http://roman-rytov.typepad.com/miles/2006/07/seeking_and_pro.html</description>
		<content:encoded><![CDATA[<p>Great list. We&#8217;ve discussed recently this topic. David Maister posted &#8220;getting good at GETTING feedback&#8221; and I put my thoughts on the other side of the coin here: <a href="http://roman-rytov.typepad.com/miles/2006/07/seeking_and_pro.html" rel="nofollow">http://roman-rytov.typepad.com/miles/2006/07/seeking_and_pro.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen Lystrup</title>
		<link>http://www.badlanguage.net/how-to-give-good-feedback#comment-929</link>
		<dc:creator>Owen Lystrup</dc:creator>
		<pubDate>Mon, 31 Jul 2006 19:52:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=221#comment-929</guid>
		<description>I like number 5. It reminds me of a client I am working with right now on a presentation. 

Each time we get together to organize things, not write, the client wants me to figure out which phrases and which jargon sound best. And each time I tell the client, "Let's get organized first; then we'll figure out what sounds best."</description>
		<content:encoded><![CDATA[<p>I like number 5. It reminds me of a client I am working with right now on a presentation. </p>
<p>Each time we get together to organize things, not write, the client wants me to figure out which phrases and which jargon sound best. And each time I tell the client, &#8220;Let&#8217;s get organized first; then we&#8217;ll figure out what sounds best.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
