<?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: Epic Client Communication</title>
	<atom:link href="http://john.onolan.org/epic-client-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://john.onolan.org/epic-client-communication/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=epic-client-communication</link>
	<description></description>
	<lastBuildDate>Sun, 29 Jan 2012 00:32:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: John</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-785</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 29 Jul 2009 15:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-785</guid>
		<description>I&#039;m glad it helped Hayley and Japh :) I&#039;m sure we can all improve!</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad it helped Hayley and Japh :) I&#8217;m sure we can all improve!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Japh</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-781</link>
		<dc:creator>Japh</dc:creator>
		<pubDate>Wed, 29 Jul 2009 09:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-781</guid>
		<description>Wow, Hayley!  That&#039;s brilliant!  I think I&#039;ll make myself a template so I remember to use the format... I think it&#039;ll make a lot of difference for my clients too.

I&#039;m a developer, and I&#039;m having to communicate both with clients and with designers (who are also my clients).  Each needs very different things!

Thanks for this post, John!  I think it could be my favourite yet!  ;)</description>
		<content:encoded><![CDATA[<p>Wow, Hayley!  That&#8217;s brilliant!  I think I&#8217;ll make myself a template so I remember to use the format&#8230; I think it&#8217;ll make a lot of difference for my clients too.</p>
<p>I&#8217;m a developer, and I&#8217;m having to communicate both with clients and with designers (who are also my clients).  Each needs very different things!</p>
<p>Thanks for this post, John!  I think it could be my favourite yet!  ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hayley</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-779</link>
		<dc:creator>Hayley</dc:creator>
		<pubDate>Tue, 28 Jul 2009 13:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-779</guid>
		<description>Since reading this post I&#039;ve been sending all my e-mails in that format and you would not believe the difference it&#039;s made. Usually I get responses back that only answer half the questions or answer the wrong questions altogether but now I&#039;m finding clients understand what I need first time which saves time and frustration for both me *and* them.

Awesome!</description>
		<content:encoded><![CDATA[<p>Since reading this post I&#8217;ve been sending all my e-mails in that format and you would not believe the difference it&#8217;s made. Usually I get responses back that only answer half the questions or answer the wrong questions altogether but now I&#8217;m finding clients understand what I need first time which saves time and frustration for both me *and* them.</p>
<p>Awesome!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ash Young</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-776</link>
		<dc:creator>Ash Young</dc:creator>
		<pubDate>Sun, 26 Jul 2009 12:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-776</guid>
		<description>This is something that we suffer from from as well. Often we&#039;ll send emails to clients with a list of points that need addressing only to receive a reply to perhaps 50% of the points. It then becomes a nightmare to chase the missing answers. This is something we&#039;ll have to look at.</description>
		<content:encoded><![CDATA[<p>This is something that we suffer from from as well. Often we&#8217;ll send emails to clients with a list of points that need addressing only to receive a reply to perhaps 50% of the points. It then becomes a nightmare to chase the missing answers. This is something we&#8217;ll have to look at.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-772</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Fri, 24 Jul 2009 19:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-772</guid>
		<description>Great post.  Definitely something we need to be reminded of.

I did tech support for several years and, especially when I was working for MSN, we used the PAR format when we were writing notes into our ticketing system:

Problem:
Action:
Resolution:

I&#039;ve pretty much blocked that whole period of my life out of my memory as tech support is a soul-sucking pit of despair that entices you with ideas of &quot;getting your foot in the door&quot; of the IT Industry, but the truth is that tech support drones are the lowest on the totem pole, even escalation support agents, and are destined to sit and rot in tech support for eternity.

HOWEVER, the email you received from your Magento experts sounds very similar to that format, and, I agree, could benefit client communications immensely.  It&#039;s a very simple format, and very easy to adopt with little room for confusion or argument.  It&#039;s definitely something I will start thinking about when communicating with clients.

~c</description>
		<content:encoded><![CDATA[<p>Great post.  Definitely something we need to be reminded of.</p>
<p>I did tech support for several years and, especially when I was working for MSN, we used the PAR format when we were writing notes into our ticketing system:</p>
<p>Problem:<br />
Action:<br />
Resolution:</p>
<p>I&#8217;ve pretty much blocked that whole period of my life out of my memory as tech support is a soul-sucking pit of despair that entices you with ideas of &#8220;getting your foot in the door&#8221; of the IT Industry, but the truth is that tech support drones are the lowest on the totem pole, even escalation support agents, and are destined to sit and rot in tech support for eternity.</p>
<p>HOWEVER, the email you received from your Magento experts sounds very similar to that format, and, I agree, could benefit client communications immensely.  It&#8217;s a very simple format, and very easy to adopt with little room for confusion or argument.  It&#8217;s definitely something I will start thinking about when communicating with clients.</p>
<p>~c</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-769</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 24 Jul 2009 10:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-769</guid>
		<description>Hi Karl, thanks for commenting, great to hear that I&#039;m not the only one! :)</description>
		<content:encoded><![CDATA[<p>Hi Karl, thanks for commenting, great to hear that I&#8217;m not the only one! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Bowers</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-768</link>
		<dc:creator>Karl Bowers</dc:creator>
		<pubDate>Fri, 24 Jul 2009 09:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-768</guid>
		<description>Hi John, I can relate to your pain in this article, as I have just recently had the same experience with a client on quite a large project. 

I thought I had quite clearly outlined the project requirements via email and on the phone with my client, but it turned out (at the 11th Hour!) that they had not clearly understood my proposal details at all!

This is of course led to some serious major revisions to the project, but like yourself, I have learned quite a lot from the exercise!

You learn and develop your communication skills from situations like these, and I think its part of the process in strengthening your skills as an independent freelance / business owner.

Thanks for a great post!

Karl</description>
		<content:encoded><![CDATA[<p>Hi John, I can relate to your pain in this article, as I have just recently had the same experience with a client on quite a large project. </p>
<p>I thought I had quite clearly outlined the project requirements via email and on the phone with my client, but it turned out (at the 11th Hour!) that they had not clearly understood my proposal details at all!</p>
<p>This is of course led to some serious major revisions to the project, but like yourself, I have learned quite a lot from the exercise!</p>
<p>You learn and develop your communication skills from situations like these, and I think its part of the process in strengthening your skills as an independent freelance / business owner.</p>
<p>Thanks for a great post!</p>
<p>Karl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Japh</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-767</link>
		<dc:creator>Japh</dc:creator>
		<pubDate>Fri, 24 Jul 2009 08:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-767</guid>
		<description>Very insightful post, John.  Isn&#039;t always the way that these things often happen just the wrong way around?  But then maybe it had to happen that way for you to get as much from it.

I&#039;m certainly taking notes about that email too.  It&#039;s an excellent example.</description>
		<content:encoded><![CDATA[<p>Very insightful post, John.  Isn&#8217;t always the way that these things often happen just the wrong way around?  But then maybe it had to happen that way for you to get as much from it.</p>
<p>I&#8217;m certainly taking notes about that email too.  It&#8217;s an excellent example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Roche</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-765</link>
		<dc:creator>Matt Roche</dc:creator>
		<pubDate>Thu, 23 Jul 2009 15:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-765</guid>
		<description>This is a really interesting one. It really is true that the &#039;problem client&#039; can about through lack of clarity in the first place. In every aspect of life people like transparency; and when they feel like something is hidden from them, or they don&#039;t understand something they tend to get defensive.

So many future problems can be avoided by transparency in the first place. People in every industry are guilty of it, but I have to say that web designers (or people who work online) and car mechanics are two of the worst! And I know this because a) I work online and b) I don&#039;t understand the inner-workings of a car engine!</description>
		<content:encoded><![CDATA[<p>This is a really interesting one. It really is true that the &#8216;problem client&#8217; can about through lack of clarity in the first place. In every aspect of life people like transparency; and when they feel like something is hidden from them, or they don&#8217;t understand something they tend to get defensive.</p>
<p>So many future problems can be avoided by transparency in the first place. People in every industry are guilty of it, but I have to say that web designers (or people who work online) and car mechanics are two of the worst! And I know this because a) I work online and b) I don&#8217;t understand the inner-workings of a car engine!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharon</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-764</link>
		<dc:creator>Sharon</dc:creator>
		<pubDate>Thu, 23 Jul 2009 13:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-764</guid>
		<description>What a great way to lay out an email. You&#039;re so right John, I&#039;ve been going on my own for about the same time as you have and am slowly learning to think like a client as well as everything else.</description>
		<content:encoded><![CDATA[<p>What a great way to lay out an email. You&#8217;re so right John, I&#8217;ve been going on my own for about the same time as you have and am slowly learning to think like a client as well as everything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-763</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 23 Jul 2009 13:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-763</guid>
		<description>Communication is absolutely key.  I make it the #1 priority and selling point for my business.

I agree - that is a well-structured response.  Organizing it into issue / action is perfect.

Client communication and email writing is a skill that constantly evolves, just like any other skills we develop as web designers.</description>
		<content:encoded><![CDATA[<p>Communication is absolutely key.  I make it the #1 priority and selling point for my business.</p>
<p>I agree &#8211; that is a well-structured response.  Organizing it into issue / action is perfect.</p>
<p>Client communication and email writing is a skill that constantly evolves, just like any other skills we develop as web designers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Jones</title>
		<link>http://john.onolan.org/epic-client-communication/comment-page-1/#comment-762</link>
		<dc:creator>Luke Jones</dc:creator>
		<pubDate>Thu, 23 Jul 2009 12:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://john.onolan.org/?p=503#comment-762</guid>
		<description>Fantastic post, I sometimes have issues with communications, so laying out your emails/letters in a way like that above really helps to be clear about what you&#039;re doing.

Luckily, I&#039;ve never really had a &#039;nightmare&#039; client, but it will happen one day and with advice like this, I&#039;ll be able to counter-act that.</description>
		<content:encoded><![CDATA[<p>Fantastic post, I sometimes have issues with communications, so laying out your emails/letters in a way like that above really helps to be clear about what you&#8217;re doing.</p>
<p>Luckily, I&#8217;ve never really had a &#8216;nightmare&#8217; client, but it will happen one day and with advice like this, I&#8217;ll be able to counter-act that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced (User agent is rejected)
Database Caching 2/20 queries in 0.013 seconds using disk: basic
Object Caching 576/585 objects using disk: basic

Served from: john.onolan.org @ 2012-02-04 15:18:54 -->
