<?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: 4 Ways to Tell About the Problem</title>
	<atom:link href="http://blog.brodzinski.com/2007/09/4-ways-to-tell-about-problem.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2007/09/4-ways-to-tell-about-problem.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Thu, 29 Jul 2010 10:46:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2007/09/4-ways-to-tell-about-problem.html#comment-1932</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Sun, 07 Oct 2007 20:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/4-ways-to-tell-about-the-problem.html#comment-1932</guid>
		<description>Thanks for a comment David. Sharing a set of options how problems can be resolved is a natural consequence to me after telling bad news. Unfortunately sometimes it is hard to show several different ways to solve the problem and not use &quot;pray for the miracle&quot;.&lt;br/&gt;&lt;br/&gt;I agree, you should prepare yourself, before you go to on &lt;i&gt;that&lt;/i&gt; kind of meetings and everything what can be helpful is essential because it calms down the customer and bring the substantial discussion back. &lt;br/&gt;&lt;br/&gt;And yes, if you don&#039;t want even to try to find the solution yourself, the customer won&#039;t do the job for you either.</description>
		<content:encoded><![CDATA[<p>Thanks for a comment David. Sharing a set of options how problems can be resolved is a natural consequence to me after telling bad news. Unfortunately sometimes it is hard to show several different ways to solve the problem and not use &#8220;pray for the miracle&#8221;.</p>
<p>I agree, you should prepare yourself, before you go to on <i>that</i> kind of meetings and everything what can be helpful is essential because it calms down the customer and bring the substantial discussion back. </p>
<p>And yes, if you don&#8217;t want even to try to find the solution yourself, the customer won&#8217;t do the job for you either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Daly</title>
		<link>http://blog.brodzinski.com/2007/09/4-ways-to-tell-about-problem.html#comment-1931</link>
		<dc:creator>David Daly</dc:creator>
		<pubDate>Sat, 06 Oct 2007 21:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/4-ways-to-tell-about-the-problem.html#comment-1931</guid>
		<description>Firstly, thanks for the great blog!&lt;br/&gt;I agree with you that being up-front about problems as soon as they occur is the best way of keeping a customer on-side. One thing that I would add (and that I have personally found very powerful) is that you should serve up a solution (or range of options) along with the bad news. That way you are actually going to a customer with a solution rather than just a problem.</description>
		<content:encoded><![CDATA[<p>Firstly, thanks for the great blog!<br />I agree with you that being up-front about problems as soon as they occur is the best way of keeping a customer on-side. One thing that I would add (and that I have personally found very powerful) is that you should serve up a solution (or range of options) along with the bad news. That way you are actually going to a customer with a solution rather than just a problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
