<?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: Meeting Client Expectations</title>
	<atom:link href="http://www.pmhut.com/meeting-client-expectations/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/meeting-client-expectations</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 12:06:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gabriel Blanc-Laine</title>
		<link>http://www.pmhut.com/meeting-client-expectations/comment-page-1#comment-8596</link>
		<dc:creator>Gabriel Blanc-Laine</dc:creator>
		<pubDate>Mon, 24 Aug 2009 02:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3601#comment-8596</guid>
		<description>I couldn't agree with you more on this entire article. I think discovering what it is exactly that the client needs as opposed to only what the client expects is probably one of the most overlooked steps in laying out a proper project. Often times we get so focused on what we can do or provide for a client that we don’t take the time to listen to what it is they are really looking for and don't clarify enough upstream objectives and required resources. 

Quantifiable and realistic objectives, achievable time line, appropriate resources and budget, key milestones, major risks... should be transparently discussed before any agreement, and recorded for future reference. From there, each party should be fully accountable to make the project a success: the client to provide the necessary support and you to deliver on results and on time. As needs might be lower than expectations, you could even overachieve and reach the stars.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree with you more on this entire article. I think discovering what it is exactly that the client needs as opposed to only what the client expects is probably one of the most overlooked steps in laying out a proper project. Often times we get so focused on what we can do or provide for a client that we don’t take the time to listen to what it is they are really looking for and don&#8217;t clarify enough upstream objectives and required resources. </p>
<p>Quantifiable and realistic objectives, achievable time line, appropriate resources and budget, key milestones, major risks&#8230; should be transparently discussed before any agreement, and recorded for future reference. From there, each party should be fully accountable to make the project a success: the client to provide the necessary support and you to deliver on results and on time. As needs might be lower than expectations, you could even overachieve and reach the stars.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

