<?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: Some Consulting Wisdom I Picked Up</title>
	<atom:link href="http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/</link>
	<description>Software development, testing, and techie life</description>
	<lastBuildDate>Thu, 08 Mar 2012 22:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Deborah Smith</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-1385</link>
		<dc:creator>Deborah Smith</dc:creator>
		<pubDate>Wed, 07 Sep 2011 11:51:00 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-1385</guid>
		<description>Hmm it looks like your blog ate my first comment (it was super long) so I guess I’ll just sum it up what I wrote and say, I’m thoroughly enjoying your blog. I too am an aspiring blog writer but I’m still new to everything. Do you have any recommendations for novice blog writers? I’d definitely appreciate it. &lt;a href=&quot;http://companyfinder.ie/maxela.html&quot; rel=&quot;nofollow&quot;&gt;Russian Food&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Hmm it looks like your blog ate my first comment (it was super long) so I guess I’ll just sum it up what I wrote and say, I’m thoroughly enjoying your blog. I too am an aspiring blog writer but I’m still new to everything. Do you have any recommendations for novice blog writers? I’d definitely appreciate it. <a href="http://companyfinder.ie/maxela.html" rel="nofollow">Russian Food</a> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ralph</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-347</link>
		<dc:creator>ralph</dc:creator>
		<pubDate>Wed, 25 Jun 2008 17:52:44 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-347</guid>
		<description>As to the last, yes: In my experience, most meetings are for concluding business in public that has already been agreed to in private by the appropriate parties. A good meeting is designed to clarify what everyone agrees as part of a public ritual. There are other good meetings, such as those in which the agreement is about what is wrong or lacking. The result of my view, then, is that Chad is basically right as rain: in poorly designed meetings (the usual ones for consultants), try to be constructive and polite and non-confrontational and then meet the appropriate people individually. Once youv&#039;e got straight with them, bring them all back into a meeting to restate what everyone thinks is best and attribute the success of that agreement to them. :-)</description>
		<content:encoded><![CDATA[<p>As to the last, yes: In my experience, most meetings are for concluding business in public that has already been agreed to in private by the appropriate parties. A good meeting is designed to clarify what everyone agrees as part of a public ritual. There are other good meetings, such as those in which the agreement is about what is wrong or lacking. The result of my view, then, is that Chad is basically right as rain: in poorly designed meetings (the usual ones for consultants), try to be constructive and polite and non-confrontational and then meet the appropriate people individually. Once youv&#8217;e got straight with them, bring them all back into a meeting to restate what everyone thinks is best and attribute the success of that agreement to them. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad Myers</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-346</link>
		<dc:creator>Chad Myers</dc:creator>
		<pubDate>Tue, 24 Jun 2008 11:06:26 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-346</guid>
		<description>@Robin:

In my experience, most meetings had nothing to do with getting things done, they were excuses to show off, score political points, bash/blame someone else, etc.  So getting to brass tacks in most meetings was pointless and dangerous. You can usually tell when you&#039;re in one of these meetings because there is more than 3-4 people in it (usually 10+).

The meetings were the real decisions happen are usually one-on-one with your manager or in a meeting with just technical people (your team + manager).

Even then, sometimes, the meeting isn&#039;t about what it&#039;s supposed to be about, so navigate carefully.</description>
		<content:encoded><![CDATA[<p>@Robin:</p>
<p>In my experience, most meetings had nothing to do with getting things done, they were excuses to show off, score political points, bash/blame someone else, etc.  So getting to brass tacks in most meetings was pointless and dangerous. You can usually tell when you&#8217;re in one of these meetings because there is more than 3-4 people in it (usually 10+).</p>
<p>The meetings were the real decisions happen are usually one-on-one with your manager or in a meeting with just technical people (your team + manager).</p>
<p>Even then, sometimes, the meeting isn&#8217;t about what it&#8217;s supposed to be about, so navigate carefully.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin Hanson</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-345</link>
		<dc:creator>Robin Hanson</dc:creator>
		<pubDate>Tue, 24 Jun 2008 10:26:04 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-345</guid>
		<description>So why bother to have a meeting with more than one person if you can&#039;t talk about anything useful there?</description>
		<content:encoded><![CDATA[<p>So why bother to have a meeting with more than one person if you can&#8217;t talk about anything useful there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: db</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-344</link>
		<dc:creator>db</dc:creator>
		<pubDate>Sun, 22 Jun 2008 23:18:21 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-344</guid>
		<description>As a former tax preparer I agree with the last item stated by jlockwood (pay yourself and save the rest) except I would say &quot;Pay the government, then pay yourself and save the rest&quot;. When my husband and I were consultants I insisted that the first 30% collected (at a minimum) went into a savings account to pay our taxes. My husband was horrified by the amount that we sent in each year when we did our taxes, but at least we had set it aside. I saw many a contractor who did not have money saved to pay their taxes and they got into trouble with the IRS that they could not get out of.</description>
		<content:encoded><![CDATA[<p>As a former tax preparer I agree with the last item stated by jlockwood (pay yourself and save the rest) except I would say &#8220;Pay the government, then pay yourself and save the rest&#8221;. When my husband and I were consultants I insisted that the first 30% collected (at a minimum) went into a savings account to pay our taxes. My husband was horrified by the amount that we sent in each year when we did our taxes, but at least we had set it aside. I saw many a contractor who did not have money saved to pay their taxes and they got into trouble with the IRS that they could not get out of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlockwood</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-343</link>
		<dc:creator>jlockwood</dc:creator>
		<pubDate>Fri, 20 Jun 2008 15:24:05 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-343</guid>
		<description>@Chad

This is a wonderful blog entry!  I&#039;ve been consulting for about 3 years now and have learned many of these rules through trial and error.  The most important one were learned before moving over to consulting, which I think has been key to success.  In fact, many of these rules should also be practiced by full timers.

#7 seems to have stirred up a bit of controversy, but think about it guys, when has publicly embarrassing team members of managers ever paid off?  The spirit behind #7 is &quot;don&#039;t get in pissing matches during meetings&quot;.  If a proposed solution is rejected during a meeting, let it go.  AFTER the meeting determine why the proposal was rejected, adapt the proposal to address any concerns, sell the merits of the proposal to key stakeholders (or obstacles), then present it again (this time with some backing).

#1 has been difficult for me, but I&#039;m learning and I agree with it completely.  Consulting can be ridiculously frustrating.  If you can&#039;t keep your emotions out of the picture then find some fulltime position.  Getting angry with the client does no one any good.  You&#039;ll never create your little utopia on a contract, you simply find what works for the client, do your absolute best, compromise fundamentalist attitudes, then move on to the next gig.  If you do well they&#039;ll call you back for more work in the future.


There is only one thing that I would add.  Before I took the bold leap into the wild world of consulting Michael Feathers gave me what was probably the best advice to date (it regards personal finance).  He told me to be carful not to change my lifestyle when I start seeing the bigger paychecks that consulting offers, but so pay myself when the checks come in and put the rest away.  Contracts (especially subcontracts) can disappear at any time, often for reasons completely unrelated to performance.  The &quot;six month savings rule&quot; applies especially to the contractor.  If you don&#039;t have the discipline to save stick with full time positions...you&#039;ll find yourself hungry when the market dips.
</description>
		<content:encoded><![CDATA[<p>@Chad</p>
<p>This is a wonderful blog entry!  I&#8217;ve been consulting for about 3 years now and have learned many of these rules through trial and error.  The most important one were learned before moving over to consulting, which I think has been key to success.  In fact, many of these rules should also be practiced by full timers.</p>
<p>#7 seems to have stirred up a bit of controversy, but think about it guys, when has publicly embarrassing team members of managers ever paid off?  The spirit behind #7 is &#8220;don&#8217;t get in pissing matches during meetings&#8221;.  If a proposed solution is rejected during a meeting, let it go.  AFTER the meeting determine why the proposal was rejected, adapt the proposal to address any concerns, sell the merits of the proposal to key stakeholders (or obstacles), then present it again (this time with some backing).</p>
<p>#1 has been difficult for me, but I&#8217;m learning and I agree with it completely.  Consulting can be ridiculously frustrating.  If you can&#8217;t keep your emotions out of the picture then find some fulltime position.  Getting angry with the client does no one any good.  You&#8217;ll never create your little utopia on a contract, you simply find what works for the client, do your absolute best, compromise fundamentalist attitudes, then move on to the next gig.  If you do well they&#8217;ll call you back for more work in the future.</p>
<p>There is only one thing that I would add.  Before I took the bold leap into the wild world of consulting Michael Feathers gave me what was probably the best advice to date (it regards personal finance).  He told me to be carful not to change my lifestyle when I start seeing the bigger paychecks that consulting offers, but so pay myself when the checks come in and put the rest away.  Contracts (especially subcontracts) can disappear at any time, often for reasons completely unrelated to performance.  The &#8220;six month savings rule&#8221; applies especially to the contractor.  If you don&#8217;t have the discipline to save stick with full time positions&#8230;you&#8217;ll find yourself hungry when the market dips.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dennis</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-342</link>
		<dc:creator>dennis</dc:creator>
		<pubDate>Mon, 16 Jun 2008 05:38:54 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-342</guid>
		<description>I agree with #7. Many times, its hard to convince your users upfront, especially when there are many people in the same meeting. But they are much more receptive when you go to them and explain things 1-on-1. Keep doing it enough times and you&#039;ll eventually get them to accept your inputs on how some issues should be handled or to ask for added resources (manpower, time schedule, money, etc). Its even possible to have that requirement dropped if you push the right buttons.  

Just sharing my thoughts and kudos on the very informative post!
</description>
		<content:encoded><![CDATA[<p>I agree with #7. Many times, its hard to convince your users upfront, especially when there are many people in the same meeting. But they are much more receptive when you go to them and explain things 1-on-1. Keep doing it enough times and you&#8217;ll eventually get them to accept your inputs on how some issues should be handled or to ask for added resources (manpower, time schedule, money, etc). Its even possible to have that requirement dropped if you push the right buttons.  </p>
<p>Just sharing my thoughts and kudos on the very informative post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy DeMonbreun</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-341</link>
		<dc:creator>Troy DeMonbreun</dc:creator>
		<pubDate>Tue, 10 Jun 2008 18:09:43 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-341</guid>
		<description>Excellent list!

I only take issue with the literal statement of #7, but I think I now understand the meaning behind your statement.

Keep up the great posts!</description>
		<content:encoded><![CDATA[<p>Excellent list!</p>
<p>I only take issue with the literal statement of #7, but I think I now understand the meaning behind your statement.</p>
<p>Keep up the great posts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Opgenorth</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-340</link>
		<dc:creator>Tom Opgenorth</dc:creator>
		<pubDate>Mon, 09 Jun 2008 16:31:13 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-340</guid>
		<description>Good list.  I&#039;d add another very important point:  

#0:  Humility.  Clients typically don&#039;t want a consultant coming in and making them feel small/stupid/insignificant.  </description>
		<content:encoded><![CDATA[<p>Good list.  I&#8217;d add another very important point:  </p>
<p>#0:  Humility.  Clients typically don&#8217;t want a consultant coming in and making them feel small/stupid/insignificant.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://lostechies.com/chadmyers/2008/06/08/some-consulting-wisdom-i-picked-up/#comment-339</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 09 Jun 2008 15:40:26 +0000</pubDate>
		<guid isPermaLink="false">/blogs/chad_myers/archive/2008/06/08/some-consulting-wisdom-i-picked-up.aspx#comment-339</guid>
		<description>The problem with #7 is that other people will think you are implementing it one way and will become confused if you do it another.  I generally just find a graceful way to agree and disagree (and do it my way).</description>
		<content:encoded><![CDATA[<p>The problem with #7 is that other people will think you are implementing it one way and will become confused if you do it another.  I generally just find a graceful way to agree and disagree (and do it my way).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
