<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Do you work for your clients or do they work for you?</title>
	<atom:link href="http://blog.civilengineeringcentral.com/2010/01/12/do-you-work-for-your-clients-or-do-they-work-for-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.civilengineeringcentral.com/2010/01/12/do-you-work-for-your-clients-or-do-they-work-for-you/</link>
	<description>building teams . engineering careers</description>
	<lastBuildDate>Wed, 15 Feb 2012 17:30:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Babette Burdick</title>
		<link>http://blog.civilengineeringcentral.com/2010/01/12/do-you-work-for-your-clients-or-do-they-work-for-you/#comment-783</link>
		<dc:creator><![CDATA[Babette Burdick]]></dc:creator>
		<pubDate>Fri, 15 Jan 2010 13:47:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.civilengineeringcentral.com/?p=2380#comment-783</guid>
		<description><![CDATA[You hit the nail on the head, Brandon! Depending on where we sit around the table, we all see the same thing differently. Architects (in particular) and engineers often cannot see the forest for the trees. They feel they are the only ones to truly &quot;see&quot; the entire problem  (due to their technical training and ability to think in 3 dimensions) and therefore hold the keys to the solution. 

The problem is that the client (e.g., the individual who will sign the contract) is thinking about a simple solution - even if his/her problem is rather complex. The client typically solves problems in 2D and the architects/engineers are thinking 3D. This is a big disconnect.

Keeping things simple, and developing the ability to present the solution in &quot;bite-sized&quot; pieces ,for the client to ponder and digest, is essential for gaining buy in and eventual closure of the sale/award of project.]]></description>
		<content:encoded><![CDATA[<p>You hit the nail on the head, Brandon! Depending on where we sit around the table, we all see the same thing differently. Architects (in particular) and engineers often cannot see the forest for the trees. They feel they are the only ones to truly &#8220;see&#8221; the entire problem  (due to their technical training and ability to think in 3 dimensions) and therefore hold the keys to the solution. </p>
<p>The problem is that the client (e.g., the individual who will sign the contract) is thinking about a simple solution &#8211; even if his/her problem is rather complex. The client typically solves problems in 2D and the architects/engineers are thinking 3D. This is a big disconnect.</p>
<p>Keeping things simple, and developing the ability to present the solution in &#8220;bite-sized&#8221; pieces ,for the client to ponder and digest, is essential for gaining buy in and eventual closure of the sale/award of project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Lee</title>
		<link>http://blog.civilengineeringcentral.com/2010/01/12/do-you-work-for-your-clients-or-do-they-work-for-you/#comment-782</link>
		<dc:creator><![CDATA[Brandon Lee]]></dc:creator>
		<pubDate>Fri, 15 Jan 2010 01:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.civilengineeringcentral.com/?p=2380#comment-782</guid>
		<description><![CDATA[As a civil engineering firm working on a lot of SFR&#039;s, it&#039;s hard to translate what we do to the client so they understand what&#039;s going on.  Sometime I forget that some stuff I talk about goes over people&#039;s heads.  I can imagine having a class about dealing with a client to make them understand what you are talking about as vital for a lot of companies, big and small.]]></description>
		<content:encoded><![CDATA[<p>As a civil engineering firm working on a lot of SFR&#8217;s, it&#8217;s hard to translate what we do to the client so they understand what&#8217;s going on.  Sometime I forget that some stuff I talk about goes over people&#8217;s heads.  I can imagine having a class about dealing with a client to make them understand what you are talking about as vital for a lot of companies, big and small.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Babette Burdick</title>
		<link>http://blog.civilengineeringcentral.com/2010/01/12/do-you-work-for-your-clients-or-do-they-work-for-you/#comment-779</link>
		<dc:creator><![CDATA[Babette Burdick]]></dc:creator>
		<pubDate>Wed, 13 Jan 2010 16:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.civilengineeringcentral.com/?p=2380#comment-779</guid>
		<description><![CDATA[I agree. The client ultimately takes your idea elsewhere to price shop OR you end up overwhelming them with theiir perception of project complexity. Once they become overwhelmed, they search for a way out - which can turn to skepticism. Translating your deliverables into the customer&#039;s language is important. Often, it&#039;s the pre-sale understanding of the factors impacting their decision that creates rapport and communication. Taking the time to build that base can positively impact the final result.]]></description>
		<content:encoded><![CDATA[<p>I agree. The client ultimately takes your idea elsewhere to price shop OR you end up overwhelming them with theiir perception of project complexity. Once they become overwhelmed, they search for a way out &#8211; which can turn to skepticism. Translating your deliverables into the customer&#8217;s language is important. Often, it&#8217;s the pre-sale understanding of the factors impacting their decision that creates rapport and communication. Taking the time to build that base can positively impact the final result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Lee</title>
		<link>http://blog.civilengineeringcentral.com/2010/01/12/do-you-work-for-your-clients-or-do-they-work-for-you/#comment-778</link>
		<dc:creator><![CDATA[Brandon Lee]]></dc:creator>
		<pubDate>Wed, 13 Jan 2010 05:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.civilengineeringcentral.com/?p=2380#comment-778</guid>
		<description><![CDATA[I sometimes feel like we do too much due diligence on a project before giving a proposal over to a client.  I have gone to a clients house and visually drew what was going to happen on their property according to what we would engineer while looking at the Architect&#039;s plans, only for them to be skeptical of my abilities, and not use us.]]></description>
		<content:encoded><![CDATA[<p>I sometimes feel like we do too much due diligence on a project before giving a proposal over to a client.  I have gone to a clients house and visually drew what was going to happen on their property according to what we would engineer while looking at the Architect&#8217;s plans, only for them to be skeptical of my abilities, and not use us.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

