<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Growth &#187; project management</title>
	<atom:link href="http://bloggertone.com/growth/tag/project-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://bloggertone.com/growth</link>
	<description></description>
	<lastBuildDate>Sat, 04 Sep 2010 09:28:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>It&#039;s About Your Customer, Not You!</title>
		<link>http://bloggertone.com/growth/2009/11/22/its-about-your-customer-not-you/</link>
		<comments>http://bloggertone.com/growth/2009/11/22/its-about-your-customer-not-you/#comments</comments>
		<pubDate>Sun, 22 Nov 2009 18:43:34 +0000</pubDate>
		<dc:creator>Barney Austen</dc:creator>
				<category><![CDATA[Business expansion]]></category>
		<category><![CDATA[customer management]]></category>
		<category><![CDATA[project delivery]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[team focus]]></category>
		<category><![CDATA[ustomer]]></category>

		<guid isPermaLink="false">http://bloggertone.com/growth/?p=211</guid>
		<description><![CDATA[When dealing with customer projects, we must maintain the realisation that the project is for our customers and not for us. We are doing it at their request and their needs must be to the forefront of project consideration at all times.]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-medium wp-image-217" src="http://bloggertone.com/growth/files/clock2-300x225.jpg" alt="clock" width="240" height="180" /></p>
<p>I was reading a great blog post yesterday about <a href="http://www.contrast.ie/blog/compelling-event/#more-955" target="_blank">compelling events</a> and it got me thinking about the way that many of us in business deliver our products or services.</p>
<p>The context of the compelling events article was essentially that <strong>they had a defined date</strong> and were as a result of a particular <strong>business event</strong>. The one piece of the post that provoked my thoughts was the element discussing the understanding of the customers compelling event.</p>
<p>To all of our businesses, <strong>customer is king</strong>, but we often lose sight of this fact during our normal working day. This is primarily the case in the services delivery world where the purchase is not instant for the most part i.e. it usually involves multiple interactions e.g. a piece of consultancy.</p>
<p>What tends to happen is that we become so inwardly focussed that we forget that <strong>we are engaged with the customer at their request</strong> i.e. the project often turns into being &#8220;our own&#8221; and not for the customer who asked for it in the first place.<br />
<span id="more-211"></span></p>
<p><strong>So how do we stop this happening?</strong></p>
<p>There are a few simple steps that we can take.</p>
<ol>
<li>At the outset of the project, make sure you <span style="text-decoration: underline"><strong>understand the customers end-game</strong></span>. This may seem an obvious statement, but can we all put our hands on heart 100% of the time and say we took the time to really get where the customer was going?</li>
<li>Revisit 1 above throughout the duration of the project.  The team should be <strong><span style="text-decoration: underline">focussed on the customers end-game</span></strong> all of the time. Engage with the customer, has anything changed? If it has, are the needs still being met.</li>
<li>If things start going wrong, don&#8217;t become inward looking e.g. you&#8217;ve run over-budget.  If this is your fault, then it&#8217;s your problem, not the customers. They should still get the same attention they always have and should not feel like they are being forgotten.</li>
<li><span style="text-decoration: underline"><strong>Talk to your customers </strong></span>regularly. Tell them what&#8217;s going well. Tell them what&#8217;s not &#8211; they can often help out or at least be willing to understand your view point.</li>
<li><strong><span style="text-decoration: underline">Encourage your customers</span></strong> to be open with you. If they can&#8217;t/won&#8217;t, no matter, you have to be open with them and continue to seek an understanding of their drivers.</li>
</ol>
<p>There are plenty more examples, but this should give you a good idea on how to create a project that is focussed on the customer and never loses sight of that fact.</p>
<p>Sure give it a go and see what happens!</p>
<p>The photo is attributed to <a href="http://www.flickr.com/photos/tonivc/2283676770/" target="_blank">TonyVC</a> on Flickr</p>
]]></content:encoded>
			<wfw:commentRss>http://bloggertone.com/growth/2009/11/22/its-about-your-customer-not-you/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
