 




<?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: Out of Control Clients</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/managed-services-blog/out-of-control-clients/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/managed-services-blog/out-of-control-clients/</link>
	<description>Darren Valukis brings you an inside look into successful business of Managed Service Provider</description>
	<lastBuildDate>Sat, 16 Jun 2012 02:40:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: ShawnHendricks</title>
		<link>http://itknowledgeexchange.techtarget.com/managed-services-blog/out-of-control-clients/#comment-51</link>
		<dc:creator>ShawnHendricks</dc:creator>
		<pubDate>Sat, 16 Jun 2012 02:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/managed-services-blog/out-of-control-clients/#comment-51</guid>
		<description><![CDATA[And then we all hugged.  Heh.  

Yes, it can be difficult communicating ideas, goals, dreams, and concepts between folks of different backgrounds.  You may have to approach this investment with a rapid prototyping mindset.  

If this [likely scenario] happens, what do you do?  If that happens, what do you do?  What do you expect me to do?

I expect you to fix it.  

How quickly?  What if it is systemic and I cannot.  What about a work-around.  

Communication and establishing baselines and ground rules is key.  NEVER skimp on the contract phase.  All parties must know their parts and play them.  

Also know that contracts are not just what you establish from the get go.  Contracts are struck by precedent over time.  &quot;But Becky always came right over to my desk.  She gave me her extension so I could call her directly.  I don&#039;t even know this new person, Marge.&quot;  Becky was hit by a drunk driver last week.  A precedent has been set.  

Happily, in our little scenario above, you have an out.  &quot;Becky wasn&#039;t following company policy.&quot;  You get to play hard nose.  

Okay, so what I&#039;m trying to get across is NEVER pussy-foot around an issue.  Handling things head-on is the least painful and it is honest.  

But what about precedents that go astray?  There are two ways of handling them.  1) Suck it up - but make sure everyone not involved is trained not to engage new clients in the unfavorable practice.  2) Suck it in.  Maybe you like the results of the new precedent so re-write new contracts to incorporate them, while charging accordingly.  Add a line item to your price list.  

But this is also the case in a direct hire situation.  &quot;I can&#039;t do X if you have me doing Y, so before I do Y, I need assurances you won&#039;t penalize me for not doing X.  After all, it is you, boss, who sets my priorities.&quot;  If you don&#039;t say it, you ARE still responsible for X.  But don&#039;t use it as an excuse - bosses hate that.]]></description>
		<content:encoded><![CDATA[<p>And then we all hugged.  Heh.  </p>
<p>Yes, it can be difficult communicating ideas, goals, dreams, and concepts between folks of different backgrounds.  You may have to approach this investment with a rapid prototyping mindset.  </p>
<p>If this [likely scenario] happens, what do you do?  If that happens, what do you do?  What do you expect me to do?</p>
<p>I expect you to fix it.  </p>
<p>How quickly?  What if it is systemic and I cannot.  What about a work-around.  </p>
<p>Communication and establishing baselines and ground rules is key.  NEVER skimp on the contract phase.  All parties must know their parts and play them.  </p>
<p>Also know that contracts are not just what you establish from the get go.  Contracts are struck by precedent over time.  &#8220;But Becky always came right over to my desk.  She gave me her extension so I could call her directly.  I don&#8217;t even know this new person, Marge.&#8221;  Becky was hit by a drunk driver last week.  A precedent has been set.  </p>
<p>Happily, in our little scenario above, you have an out.  &#8220;Becky wasn&#8217;t following company policy.&#8221;  You get to play hard nose.  </p>
<p>Okay, so what I&#8217;m trying to get across is NEVER pussy-foot around an issue.  Handling things head-on is the least painful and it is honest.  </p>
<p>But what about precedents that go astray?  There are two ways of handling them.  1) Suck it up &#8211; but make sure everyone not involved is trained not to engage new clients in the unfavorable practice.  2) Suck it in.  Maybe you like the results of the new precedent so re-write new contracts to incorporate them, while charging accordingly.  Add a line item to your price list.  </p>
<p>But this is also the case in a direct hire situation.  &#8220;I can&#8217;t do X if you have me doing Y, so before I do Y, I need assurances you won&#8217;t penalize me for not doing X.  After all, it is you, boss, who sets my priorities.&#8221;  If you don&#8217;t say it, you ARE still responsible for X.  But don&#8217;t use it as an excuse &#8211; bosses hate that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
