<?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>Bruce Tulgan&#039;s Blog</title>
	<atom:link href="http://www.rainmakerthinking.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rainmakerthinking.com</link>
	<description>Founded by Bruce Tulgan in 1993, RainmakerThinking, Inc. is a management and employee training firm. We help managers get better at managing and help employees work better with their bosses.</description>
	<lastBuildDate>Tue, 21 Feb 2012 14:27:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Being a Strong Follower Doesn’t Mean That You Never Push-Back</title>
		<link>http://www.rainmakerthinking.com/posts/being-a-strong-follower-doesn%e2%80%99t-mean-that-you-never-push-back/</link>
		<comments>http://www.rainmakerthinking.com/posts/being-a-strong-follower-doesn%e2%80%99t-mean-that-you-never-push-back/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 14:26:08 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Posts]]></category>

		<guid isPermaLink="false">http://www.rainmakerthinking.com/?p=1320</guid>
		<description><![CDATA[<p>Text posted Tuesday,&#160;February 21,&#160;2012 Being a strong follower doesn’t mean that you never ask questions,&#160;never make requests,&#160;never push-back,&#160;never disagree,&#160;never debate. Being a strong follower often requires that you ask questions. Just make sure they are good penetrating questions that help clarify the mission,&#160;strategy,&#160;tactics and the plan for execution. </p> <p>Being a strong follower often requires [...]]]></description>
			<content:encoded><![CDATA[<p>Text posted Tuesday,&nbsp;February 21,&nbsp;2012<br />
Being a strong follower doesn’t mean that you never ask questions,&nbsp;never make requests,&nbsp;never push-back,&nbsp;never disagree,&nbsp;never debate.  Being a strong follower often requires that you ask questions. Just make sure they are good penetrating questions that help clarify the mission,&nbsp;strategy,&nbsp;tactics and the plan for execution. </p>
<p>Being a strong follower often requires that you make requests,&nbsp;especially if the requests are for resources necessary to carry out your part of the mission. Just make sure your requests are reasonable,&nbsp;clearly thought out,&nbsp;and in service of the mission. If your requests happen to be self-serving in nature,&nbsp;just make sure that in serving yourself you are also strengthening your ability,&nbsp;skill,&nbsp;or motivation to better serve the mission. </p>
<p>Being a strong follower sometimes requires you to push-back,&nbsp;disagree,&nbsp;and debate with your leader. Just make sure it is productive and helpful debate. Are you bringing relevant information to the table about which the leader and the team were not aware?  Or is it a differing interpretation of the same information? Or is it the same information and the same interpretation,&nbsp;but you want to make clear that you would come to a different conclusion? Any way you slice it,&nbsp;make your point,&nbsp;but when the decision is made,&nbsp;it’s time to fall in line -&nbsp;if you want to remain part of the team.</p>
<p>Stay strong,<br />
Bruce</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rainmakerthinking.com/posts/being-a-strong-follower-doesn%e2%80%99t-mean-that-you-never-push-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Competing and Conflicting Boss Demands</title>
		<link>http://www.rainmakerthinking.com/videos/managing-competing-and-conflicting-boss-demands/</link>
		<comments>http://www.rainmakerthinking.com/videos/managing-competing-and-conflicting-boss-demands/#comments</comments>
		<pubDate>Mon, 20 Feb 2012 18:39:18 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Videos]]></category>

		<guid isPermaLink="false">http://www.rainmakerthinking.com/?p=1315</guid>
		<description><![CDATA[<p>Video posted Monday,&#160;February 20,&#160;2012 Transcript of video available by clicking here. NOTE: This is a SAMPLE LESSON from the It&#8217;s Okay to Manage Your Boss program in our forthcoming subscription based web site,&#160;talkaboutthework.com. </p> <p></p> <p></p> <p></p> <p> brightcove.createExperiences();</p> <p></p> [...]]]></description>
			<content:encoded><![CDATA[<p>Video posted Monday,&nbsp;February 20,&nbsp;2012<br />
Transcript of video available by <a target="_new" href="/old_newsletters/2012/feb20.htm">clicking here</a>.<br />
NOTE: This is a SAMPLE LESSON from the It&#8217;s Okay to Manage Your Boss program in our forthcoming subscription based web site,&nbsp;<a href="/about-us/highlighted-information/talkaboutthework-com/" target="_blank">talkaboutthework.com</A>.<br />
<!-- Start of Brightcove Player --></p>
<div style="display:none">
</div>
<p><!--<br />
By use of this code snippet, I agree to the Brightcove Publisher T and C<br />
found at https://accounts.brightcove.com/en/terms-and-conditions/.<br />
--></p>
<p><script language="JavaScript" type="text/javascript" src="http://admin.brightcove.com/js/BrightcoveExperiences.js"></script></p>
<p><object id="myExperience1462936720001" class="BrightcoveExperience" wmode="transparent"><param name="bgcolor" value="#FFFFFF" /><param name="width" value="352" /><param name="height" value="272" /><param name="wmode" value="transparent" /><param name="playerID" value="1409166525001" /><param name="playerKey" value="AQ~~,AAAAukMoI0k~,F6GKJq76IjFzSqn7eTUSYatw_BExFEAF" /><param name="isVid" value="true" /><param name="isUI" value="true" /><param name="dynamicStreaming" value="true" /><param name="@videoPlayer" value="1462936720001" /></object></p>
<p><!--<br />
This script tag will cause the Brightcove Players defined above it to be created as soon<br />
as the line is read by the browser. If you wish to have the player instantiated only after<br />
the rest of the HTML is processed and the page load is complete, remove the line.<br />
--><br />
<script type="text/javascript">brightcove.createExperiences();</script></p>
<p><!-- End of Brightcove Player --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rainmakerthinking.com/videos/managing-competing-and-conflicting-boss-demands/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Often the Ultimate Test of a Partnership is the Ability of One Partner to Follow Another</title>
		<link>http://www.rainmakerthinking.com/posts/1298/</link>
		<comments>http://www.rainmakerthinking.com/posts/1298/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 17:00:36 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Posts]]></category>

		<guid isPermaLink="false">http://www.rainmakerthinking.com/?p=1298</guid>
		<description><![CDATA[<p>Text posted Thursday,&#160;February 16,&#160;2012 I always say,&#160;if you want to be part of an entity larger than yourself,&#160;you need to be a good leader or a good follower. Otherwise you are likely to find yourself being a bystander or a troublemaker. </p> <p>Maybe you are thinking,&#160;&#8221;What about partnership? Isn’t that an alternative?&#8221;</p> <p>For starters:&#160;The number [...]]]></description>
			<content:encoded><![CDATA[<p>Text posted Thursday,&nbsp;February 16,&nbsp;2012<br />
I always say,&nbsp;if you want to be part of an entity larger than yourself,&nbsp;you need to be a good leader or a good follower. Otherwise you are likely to find yourself being a bystander or a troublemaker. </p>
<p>Maybe you are thinking,&nbsp;&#8221;What about partnership? Isn’t that an alternative?&#8221;</p>
<p>For starters:&nbsp;The number one reason why so many partnerships fail is when there is a lack of clearly delineated roles,&nbsp;responsibilities,&nbsp;and authority within the partnership. Successful partners consult and learn from and cooperate with each other. But they cannot always agree on everything. Ultimately a partnership must have a mechanism for making decisions in the absence of 100% agreement among the partners. That’s why large partnership organizations have a governing body like an executive committee.</p>
<p>Most successful partnerships are built on power that is NOT SHARED exactly but APPORTIONED in complimentary ways,&nbsp;ideally according to the strengths of each partner.  One partner is good with computers,&nbsp;so she is in charge of the computers. Another partner is good with money,&nbsp;so she is in charge of the money. And so on.  Often the ultimate test of a partnership,&nbsp;funny enough,&nbsp;is the ability of one partner to FOLLOW another,&nbsp;especially when they disagree.  Of course sometimes partners balk and do not support each other.  If that happens too many times,&nbsp;the partnership becomes less and less effective and will fail. </p>
<p>Stay strong,<br />
Bruce</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rainmakerthinking.com/posts/1298/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When It Comes to Followership,&#160;What’s In It for the Followers?</title>
		<link>http://www.rainmakerthinking.com/posts/when-it-comes-to-followershipwhat%e2%80%99s-in-it-for-fhe-followers/</link>
		<comments>http://www.rainmakerthinking.com/posts/when-it-comes-to-followershipwhat%e2%80%99s-in-it-for-fhe-followers/#comments</comments>
		<pubDate>Wed, 15 Feb 2012 14:04:48 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Posts]]></category>

		<guid isPermaLink="false">http://www.rainmakerthinking.com/?p=1292</guid>
		<description><![CDATA[<p>Text posted Wednesday,&#160;February 15,&#160;2012 Management relationships must be a two-way street,&#160;at least two-ways,&#160;sometimes many more than two-ways.</p> <p>Indeed,&#160;authority relationships in most workplaces nowadays are complex and shifting. Some people answer to one boss Monday and another on Tuesday. Some have to balance the requirements of multiple bosses at the same time. Sometimes the chain-of-command is [...]]]></description>
			<content:encoded><![CDATA[<p>Text posted Wednesday,&nbsp;February 15,&nbsp;2012<br />
Management relationships must be a two-way street,&nbsp;at least two-ways,&nbsp;sometimes many more than two-ways.</p>
<p>Indeed,&nbsp;authority relationships in most workplaces nowadays are complex and shifting.  Some people answer to one boss Monday and another on Tuesday. Some have to balance the requirements of multiple bosses at the same time.  Sometimes the chain-of-command is not at all clear.  And sometimes,&nbsp;even when the chain-of-command is clear,&nbsp;people can’t or won’t follow it,&nbsp;or they just don’t know how. </p>
<p>FOLLOWERSHIP is an issue that not enough people are studying and talking about.  And it is definitely not something that is well taught in many places outside the military. Yet,&nbsp;good followership is absolutely critical to an effective organization,&nbsp;every bit as critical as effective leadership. </p>
<p>Why does leadership seem like such an obvious issue for study and discussion and learning,&nbsp;but not followership? Does everyone nowadays want to be a leader? Maybe people want the power that comes with leadership,&nbsp;but unfortunately not enough people accept the responsibilities that come with leadership. </p>
<p>What about the flip side? When it comes to followership,&nbsp;there is a lot of responsibility,&nbsp;but there is no power. In fact,&nbsp;there is an abdication of power. That’s why people often say to me,&nbsp;“It is clear that strong followership has benefits for the organization and its leaders,&nbsp;but what’s in it for the followers?” How about this:&nbsp;(1) Belonging to something larger than yourself.  (2) Contributing to a clear and worthy mission. (3) Clear direction and meaningful feedback from someone more experienced,&nbsp;knowledgeable,&nbsp;skilled,&nbsp;and maybe wiser than yourself,&nbsp;at least when it comes to the mission of this particular team. (4) The joy of diligence,&nbsp;loyalty,&nbsp;and faith. </p>
<p>Of course followership,&nbsp;like leadership,&nbsp;is highly context-dependent. You might be a leader on one team and a follower on another.  But if you are part of a team and you don’t know whether you are a leader or a follower,&nbsp;THEN WHAT ARE YOU? Beware! You sure don’t want to be a trouble-maker. And why would you want to be a bystander? </p>
<p>You don’t need to be a leader in every context. If you are not the leader,&nbsp;then oh,&nbsp;what a gift you can give,&nbsp;to your team,&nbsp;its leaders,&nbsp;and any constituency served by your team. Be a great follower! Know who to follow and know how to follow,&nbsp;and then follow proudly to the very best of your ability.</p>
<p>Stay strong,<br />
Bruce</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rainmakerthinking.com/posts/when-it-comes-to-followershipwhat%e2%80%99s-in-it-for-fhe-followers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When the Chain of Command in Your Workplace Gets Disrupted</title>
		<link>http://www.rainmakerthinking.com/videos/when-the-chain-of-command-in-your-workplace-gets-disrupted/</link>
		<comments>http://www.rainmakerthinking.com/videos/when-the-chain-of-command-in-your-workplace-gets-disrupted/#comments</comments>
		<pubDate>Mon, 13 Feb 2012 22:26:45 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[Videos]]></category>

		<guid isPermaLink="false">http://www.rainmakerthinking.com/?p=1286</guid>
		<description><![CDATA[<p>Video posted Monday,&#160;February 13,&#160;2012 Transcript of video available by clicking here. NOTE: This is a SAMPLE LESSON from the It&#8217;s Okay to Manage Your Boss program in our forthcoming subscription based web site,&#160;talkaboutthework.com. </p> <p></p> <p></p> <p></p> <p> brightcove.createExperiences();</p> <p></p> [...]]]></description>
			<content:encoded><![CDATA[<p>Video posted Monday,&nbsp;February 13,&nbsp;2012<br />
Transcript of video available by <a target="_new" href="/old_newsletters/2012/feb13.htm">clicking here</a>.<br />
NOTE: This is a SAMPLE LESSON from the It&#8217;s Okay to Manage Your Boss program in our forthcoming subscription based web site,&nbsp;<a href="/about-us/highlighted-information/talkaboutthework-com/" target="_blank">talkaboutthework.com</A>.<br />
<!-- Start of Brightcove Player --></p>
<div style="display:none">
</div>
<p><!--<br />
By use of this code snippet, I agree to the Brightcove Publisher T and C<br />
found at https://accounts.brightcove.com/en/terms-and-conditions/.<br />
--></p>
<p><script language="JavaScript" type="text/javascript" src="http://admin.brightcove.com/js/BrightcoveExperiences.js"></script></p>
<p><object id="myExperience1450345375001" class="BrightcoveExperience" wmode="transparent"><param name="bgcolor" value="#FFFFFF" /><param name="width" value="352" /><param name="height" value="272" /><param name="wmode" value="transparent" /><param name="playerID" value="1409166525001" /><param name="playerKey" value="AQ~~,AAAAukMoI0k~,F6GKJq76IjFzSqn7eTUSYatw_BExFEAF" /><param name="isVid" value="true" /><param name="isUI" value="true" /><param name="dynamicStreaming" value="true" /><param name="@videoPlayer" value="1450345375001" /></object></p>
<p><!--<br />
This script tag will cause the Brightcove Players defined above it to be created as soon<br />
as the line is read by the browser. If you wish to have the player instantiated only after<br />
the rest of the HTML is processed and the page load is complete, remove the line.<br />
--><br />
<script type="text/javascript">brightcove.createExperiences();</script></p>
<p><!-- End of Brightcove Player --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rainmakerthinking.com/videos/when-the-chain-of-command-in-your-workplace-gets-disrupted/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

