<?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: Rain Making Problem #19: Using Client Information in Blog Posts</title>
	<atom:link href="http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/</link>
	<description>Ford Harding's Blog on Rainmaking and Business Development</description>
	<pubDate>Mon, 15 Mar 2010 05:15:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy Heys</title>
		<link>http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/comment-page-1/#comment-36628</link>
		<dc:creator>Andy Heys</dc:creator>
		<pubDate>Fri, 03 Jul 2009 08:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=377#comment-36628</guid>
		<description>This is a tricky one as it applies to any reference to client issues in any sales materials or thought leadership papers. If the article is well written and the issues are generalised, many clients and non clients will see themselves in what you write. For this reason, unless it is an agreed case study, I never write directly about a specific client.</description>
		<content:encoded><![CDATA[<p>This is a tricky one as it applies to any reference to client issues in any sales materials or thought leadership papers. If the article is well written and the issues are generalised, many clients and non clients will see themselves in what you write. For this reason, unless it is an agreed case study, I never write directly about a specific client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Buckshon</title>
		<link>http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/comment-page-1/#comment-36611</link>
		<dc:creator>Mark Buckshon</dc:creator>
		<pubDate>Fri, 26 Jun 2009 22:48:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=377#comment-36611</guid>
		<description>In my case, I start with one simple rule, I never identify anyone publicly where the identification could cause negative responses.  When speaking positively, I will often post without asking permission first but also email the person involved and offer to remove or delete the post if it would cause problems.  Obviously, if the post results from personal interaction rather than a web or e-relationship, I'll generally ask in advance and obtain oral permission first befoe posting (especially if I have a camera in hand.)

Now, if I were a lawyer or engineer handling confidential files, the approach would be different.  But most people are happy to receive recognition in the blog -- especially when hyperlinks to their site are provided (thus helping their own search eingine status.)  I like to keep the bureacuracy and formality out of the approval process, knowing that blog entries can be quickly amended or deleted if there are problems, and the possibility of cached results retaining something difficult is limited -- especially since I observe the first rule:  Never identify anything negative about anyone in public.</description>
		<content:encoded><![CDATA[<p>In my case, I start with one simple rule, I never identify anyone publicly where the identification could cause negative responses.  When speaking positively, I will often post without asking permission first but also email the person involved and offer to remove or delete the post if it would cause problems.  Obviously, if the post results from personal interaction rather than a web or e-relationship, I&#8217;ll generally ask in advance and obtain oral permission first befoe posting (especially if I have a camera in hand.)</p>
<p>Now, if I were a lawyer or engineer handling confidential files, the approach would be different.  But most people are happy to receive recognition in the blog &#8212; especially when hyperlinks to their site are provided (thus helping their own search eingine status.)  I like to keep the bureacuracy and formality out of the approval process, knowing that blog entries can be quickly amended or deleted if there are problems, and the possibility of cached results retaining something difficult is limited &#8212; especially since I observe the first rule:  Never identify anything negative about anyone in public.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Simmons</title>
		<link>http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/comment-page-1/#comment-36470</link>
		<dc:creator>Anne Simmons</dc:creator>
		<pubDate>Thu, 25 Jun 2009 03:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=377#comment-36470</guid>
		<description>I tend to agree with Chuck's approach.  Make it less about the client and more about a problem - resolution.  Blogging is meant to be quick and insightful not absolutely comprehensive.  In my business, with or without permission, I would NEVER blog about a client.  It is a slippery slope.  And maybe your contact today wouldn't mind, but your next client inside the same company would.</description>
		<content:encoded><![CDATA[<p>I tend to agree with Chuck&#8217;s approach.  Make it less about the client and more about a problem - resolution.  Blogging is meant to be quick and insightful not absolutely comprehensive.  In my business, with or without permission, I would NEVER blog about a client.  It is a slippery slope.  And maybe your contact today wouldn&#8217;t mind, but your next client inside the same company would.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Franks</title>
		<link>http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/comment-page-1/#comment-36408</link>
		<dc:creator>Chuck Franks</dc:creator>
		<pubDate>Wed, 24 Jun 2009 15:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=377#comment-36408</guid>
		<description>My first response would be to explore the type of business being conducted. Some industries where confidentiality is key might pose more of a challenge.  I blog about my clients but mainly about their successes. So it usually isn't an issue, however, getting permission in writing is excellent advice no matter even if your saying something positive about them.  Will you be choosing to include client recommendations/testimonials which would also be posted to your website thus creating possible inference of who had what issue.  I might suggest an approach that rather than using a blog that focuses on client issues, a blog that approaches an industry and common problems that business owners for example have in that industry.  If you delve into common problems and solutions or how you can help solve the problem then you position yourself to be a person of value. Emphasizing solutions to the problem allows you to focus on a teaching, sharing, content building blog rather than a personal account blog.  This positions you to be more of a thought leader who has answers rather than a problem fixer. 
Chuck Franks, PCC
www.lifecoachkansascity.wordpress.com/</description>
		<content:encoded><![CDATA[<p>My first response would be to explore the type of business being conducted. Some industries where confidentiality is key might pose more of a challenge.  I blog about my clients but mainly about their successes. So it usually isn&#8217;t an issue, however, getting permission in writing is excellent advice no matter even if your saying something positive about them.  Will you be choosing to include client recommendations/testimonials which would also be posted to your website thus creating possible inference of who had what issue.  I might suggest an approach that rather than using a blog that focuses on client issues, a blog that approaches an industry and common problems that business owners for example have in that industry.  If you delve into common problems and solutions or how you can help solve the problem then you position yourself to be a person of value. Emphasizing solutions to the problem allows you to focus on a teaching, sharing, content building blog rather than a personal account blog.  This positions you to be more of a thought leader who has answers rather than a problem fixer.<br />
Chuck Franks, PCC<br />
<a href="http://www.lifecoachkansascity.wordpress.com/" rel="nofollow">http://www.lifecoachkansascity.wordpress.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Stockdale</title>
		<link>http://www.hardingco.com/blog/2009/06/24/rain-making-problem-19-using-client-information-in-blog-posts/comment-page-1/#comment-36399</link>
		<dc:creator>Martin Stockdale</dc:creator>
		<pubDate>Wed, 24 Jun 2009 12:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=377#comment-36399</guid>
		<description>No client shall be even remotely referenced to in a public forum unless I have it in writing that it is ok to do so. This keeps me free and clear of any misunderstandings.

Martin Stockdale
Wireless Logistics, Inc.</description>
		<content:encoded><![CDATA[<p>No client shall be even remotely referenced to in a public forum unless I have it in writing that it is ok to do so. This keeps me free and clear of any misunderstandings.</p>
<p>Martin Stockdale<br />
Wireless Logistics, Inc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
