<?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>Jamie&#039;s Blog &#187; article</title>
	<atom:link href="http://www.angelforge.org/wordpress/tags/article/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.angelforge.org/wordpress</link>
	<description>My life is words.</description>
	<lastBuildDate>Sat, 28 Jan 2012 04:35:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Leading Change: Why Transformation Efforts Fail</title>
		<link>http://www.angelforge.org/wordpress/mba/leading-change-why-transformation-efforts-fail/</link>
		<comments>http://www.angelforge.org/wordpress/mba/leading-change-why-transformation-efforts-fail/#comments</comments>
		<pubDate>Sun, 08 Nov 2009 18:01:24 +0000</pubDate>
		<dc:creator>Jamie</dc:creator>
				<category><![CDATA[mba]]></category>
		<category><![CDATA[article]]></category>
		<category><![CDATA[transformation]]></category>

		<guid isPermaLink="false">http://www.angelforge.org/wordpress/?p=1989</guid>
		<description><![CDATA[Notes on: Kotter, J. P. (2007). &#8220;Leading change: why transformation efforts fail.&#8221; Harvard Business Review, January 2007, 96-103 Transformation efforts go by many names TQM Reengineering Rightsizing Restructuring Cultural change Turnaround Key general lessons Change involves series of steps. Do not skip the steps! Mistakes in any phase can have devastating effects Errors Lack of [...]]]></description>
			<content:encoded><![CDATA[<p>Notes on:<br />
Kotter, J. P. (2007). &#8220;Leading change: why transformation efforts fail.&#8221; Harvard Business Review, January 2007, 96-103</p>
<ul>
<li>Transformation efforts go by many names
<ul>
<li>TQM</li>
<li>Reengineering</li>
<li>Rightsizing</li>
<li>Restructuring</li>
<li>Cultural change</li>
<li>Turnaround</li>
</ul>
</li>
<li>Key general lessons
<ul>
<li>Change involves series of steps. Do not skip the steps!</li>
<li>Mistakes in any phase can have devastating effects</li>
</ul>
</li>
<li>Errors
<ul>
<li>Lack of urgency</li>
<li>No guiding coalition</li>
<li>No vision</li>
<li>Lack of communication about vision</li>
<li>Leaving obstacles for new vision</li>
<li>Lack of quick wins</li>
<li>Predeclared victory (&#8220;Mission Accomplished!&#8221;)</li>
<li>Lack of anchors for change in culture</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.angelforge.org/wordpress/mba/leading-change-why-transformation-efforts-fail/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Saving the Business Without Losing the Company</title>
		<link>http://www.angelforge.org/wordpress/mba/saving-the-business-without-losing-the-company/</link>
		<comments>http://www.angelforge.org/wordpress/mba/saving-the-business-without-losing-the-company/#comments</comments>
		<pubDate>Sat, 07 Nov 2009 03:41:45 +0000</pubDate>
		<dc:creator>Jamie</dc:creator>
				<category><![CDATA[mba]]></category>
		<category><![CDATA[article]]></category>

		<guid isPermaLink="false">http://www.angelforge.org/wordpress/?p=1974</guid>
		<description><![CDATA[Notes on: Ghosn, C. (2002). &#8220;Saving the Business Without Losing the Company.&#8221; Harvard Business Review, January 2002, p 37-45. Intro Renault Nissan Merger Ghosn natural candidate Cleaned up failed merger with Volvo Nissan unprofitable for 8 yrs &#8220;do-or-die situation&#8221; (p 38) retain self-esteem of employees Plan involve Nissan&#8217;s own managers Cross-functional teams company culture important [...]]]></description>
			<content:encoded><![CDATA[<p>Notes on:</p>
<p>Ghosn, C. (2002). &#8220;Saving the Business Without Losing the Company.&#8221; Harvard Business Review, January 2002, p 37-45.</p>
<ul>
<li>Intro
<ul>
<li>Renault Nissan Merger</li>
<li>Ghosn natural candidate
<ul>
<li>Cleaned up failed merger with Volvo</li>
</ul>
</li>
<li>Nissan unprofitable for 8 yrs</li>
<li>&#8220;do-or-die situation&#8221; (p 38)</li>
<li>retain self-esteem of employees</li>
<li>Plan
<ul>
<li>involve Nissan&#8217;s own managers</li>
<li>Cross-functional teams</li>
<li>company culture important</li>
<li>develop new culture</li>
</ul>
</li>
</ul>
</li>
<li>Breaking with Tradition
<ul>
<li>Historically, product dev lessened to save money</li>
<li>No seniority rule</li>
<li>Sometimes younger managers suffer</li>
<li>New performance-based compensation</li>
<li>historically, loose areas of responsibility
<ul>
<li>positions with no responsibility</li>
</ul>
</li>
</ul>
</li>
<li>Mobilizing Cross-Functional Teams
<ul>
<li>Dramatic changes</li>
<li>Went against some norms of Japanese society</li>
<li>Cross-functional teams were primary part of plan
<ul>
<li>Given 3 months to come up with turnaround recommendations</li>
<li>Came from company&#8217;s middle managers</li>
<li>Each CFT had subteams</li>
<li>Executive sponsors from different business areas</li>
<li>Pilots with frontline experience and credibility with rank and file</li>
<li>Challenge to reduce costs by 20%</li>
<li>Identified many small changes to reduce costs</li>
<li>Nissan Revival Plan, developed by Nissan&#8217;s own executives
<ul>
<li>Plan was about braking, and accelerating the company</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
<li>The Importance of Respect
<ul>
<li>Uneasy public</li>
<li>Employees trusted Ghosn b/c of respect he showed</li>
<li>&#8220;careful to protect Nissan&#8217;s identity and its dignity as a company&#8221; (p 44)</li>
<li>Renault did not try to renegotiate terms</li>
<li>Nissan&#8217;s culture more impt than Japanese culture</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.angelforge.org/wordpress/mba/saving-the-business-without-losing-the-company/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Virtuoso Teams</title>
		<link>http://www.angelforge.org/wordpress/mba/virtuoso-teams/</link>
		<comments>http://www.angelforge.org/wordpress/mba/virtuoso-teams/#comments</comments>
		<pubDate>Thu, 05 Nov 2009 03:01:25 +0000</pubDate>
		<dc:creator>Jamie</dc:creator>
				<category><![CDATA[mba]]></category>
		<category><![CDATA[article]]></category>

		<guid isPermaLink="false">http://www.angelforge.org/wordpress/?p=1965</guid>
		<description><![CDATA[Notes on &#160; Fischer, B. &#38; Boynton, A. (2005). Harvard Business Review, July-August 2005, p 116-123 Intro p 117 Whiz Kids &#8211; saved Ford Seymour Cray &#8211; first commercial supercomputer Virtuoso teams &#8211; composed of elite experts Unique in ambition, intensity,&#160; esprit, results-driven Risks considered high Default mode = mediocrity V-teams use different rules Examples [...]]]></description>
			<content:encoded><![CDATA[<p>Notes on</p>
<p>&nbsp;</p>
<p>Fischer, B. &amp; Boynton, A. (2005). Harvard Business Review, July-August 2005, p 116-123</p>
<ul>
<li>Intro p 117
<ul>
<li>Whiz Kids &#8211; saved Ford</li>
<li>Seymour Cray &#8211; first commercial supercomputer</li>
<li>Virtuoso teams &#8211; composed of elite experts</li>
<li>Unique in ambition, intensity,&nbsp; esprit, results-driven</li>
<li>Risks considered high</li>
<li>Default mode = mediocrity</li>
<li>V-teams use different rules</li>
<li>Examples of v-teams accomplished goals and changed business and industry in process</li>
<li>collaboration impt for leaders of v-teams</li>
</ul>
</li>
<li>Assemble the Stars p 118
<ul>
<li>People who are able are assigned to teams</li>
<li>In v-teams, &#8220;thinking is more impt than doing&#8221; p 119</li>
<li>v-team members push each other</li>
<li>they love challenge</li>
<li>v-teams must be composed of great people</li>
<li>Your Show of Shows&#8217; staff greatest comedy staff of all time
<ul>
<li>high-energy contests</li>
<li>tension among group members</li>
</ul>
</li>
<li>&#8220;Nasty tugs-of-war&#8221;</li>
</ul>
</li>
<li>Build the Group Ego p 119
<ul>
<li>Traditional teams are cooperative</li>
<li>v-teams are individual-based</li>
<li>v-teams transform into powerful team with shared identity later</li>
<li>Kjell Sunde assembled best technical people
<ul>
<li>Goal was to understand and prevent Bloc 34</li>
<li>Each technologist was confident</li>
<li>Sunde celebrated selected v-team</li>
<li>gave access to resources</li>
<li>Introduced teamwork pattern</li>
<li>Split group into half solving problems</li>
<li>transformed into &#8220;one great totality&#8221; p 120</li>
</ul>
</li>
</ul>
</li>
<li>Make Work a Contact Sport p 120
<ul>
<li>traditional teams distant</li>
<li>v-teams need physical contact</li>
<li>passionate dialogue impt</li>
<li>experimentation/rapid-prototyping</li>
<li>pressure-cooker</li>
<li>dedicated team room</li>
<li>informal atmosphere</li>
<li>beware intense pressure vis-a-vis project duration</li>
</ul>
</li>
<li>Challenging the Customer p 122
<ul>
<li>v-teams believe customers want more</li>
<li>West Side Story risky
<ul>
<li>success = vindication</li>
</ul>
</li>
<li>Norsk Hydro
<ul>
<li>customers were equity market analysts</li>
<li>thoughtful explanations minimized market erosion</li>
</ul>
</li>
</ul>
</li>
<li>Herd the Cats p 122</li>
<li>traditional team leaders want consensus and compromize</li>
<li>v-team leaders must be def and forceful</li>
<li>cannot constraint expresiveness</li>
<li>must trust talents</li>
<li>balance individual attention with demands and timelines of projects</li>
<li>be a perfectionist</li>
<li>Robbins pushed the WSS cast</li>
<li>foster individual and creative freedom
<ul>
<li>contests of ideas</li>
<li>exploit time</li>
<li>deadline pressure requires focus</li>
</ul>
</li>
<li>stamp out mediocrity</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.angelforge.org/wordpress/mba/virtuoso-teams/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Moving Mountains</title>
		<link>http://www.angelforge.org/wordpress/mba/moving-mountains/</link>
		<comments>http://www.angelforge.org/wordpress/mba/moving-mountains/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 17:54:10 +0000</pubDate>
		<dc:creator>Jamie</dc:creator>
				<category><![CDATA[mba]]></category>
		<category><![CDATA[article]]></category>

		<guid isPermaLink="false">http://www.angelforge.org/wordpress/?p=1952</guid>
		<description><![CDATA[Notes on: Moving Mountains. (2003). Motivating People. Harvard Business Review, January 2003, p 41-47. Interviews with people about how to motivate others. &#8220;Start with the Truth&#8221; (p 42) Carly Fiorina, chairman and CEO of HP &#8220;Appeal to Greatness&#8221; (p 42) Christopher Bangle, BMW global chief of design&#160; &#8220;Make them Proud&#8221; (p 43) Chauncey Veatch, 2002 [...]]]></description>
			<content:encoded><![CDATA[<p>Notes on:</p>
<p>Moving Mountains. (2003). Motivating People. Harvard Business Review, January 2003, p 41-47.</p>
<p>Interviews with people about how to motivate others.</p>
<ul>
<li>&#8220;Start with the Truth&#8221; (p 42)
<ul>
<li>Carly Fiorina, chairman and CEO of HP</li>
</ul>
</li>
<li>&#8220;Appeal to Greatness&#8221; (p 42)
<ul>
<li>Christopher Bangle, BMW global chief of design&nbsp;</li>
</ul>
</li>
<li>&#8220;Make them Proud&#8221; (p 43)
<ul>
<li>Chauncey Veatch, 2002 National Teacher of the Year</li>
</ul>
</li>
<li>&#8220;Stick to your values&#8221; (p 43)
<ul>
<li>L.M. Banker, Jr., chairman of Wachovia</li>
</ul>
</li>
<li>&#8220;Be a broken record&#8221; (p 44)
<ul>
<li>Robert A. Eckert, chairman and CEO of Mattel</li>
</ul>
</li>
<li>&#8220;Build Trust&#8221; (p 44)
<ul>
<li>Susan Butcher, four-time winner of Iditarod</li>
</ul>
</li>
<li>&#8220;Encourage Risk&#8221; (p 45)
<ul>
<li>Ross J. Pillari, president of BP America</li>
</ul>
</li>
<li>&#8220;care for the Little Guy&#8221; (p 45)
<ul>
<li>Herb Baum, chairman, president, CEO of Dial</li>
</ul>
</li>
<li>&#8220;Ground without grinding&#8221; (p 46)
<ul>
<li>Mario Mazzola, chief development officer at Cisco Systems</li>
</ul>
</li>
<li>&#8220;Leap First, Ask Later&#8221; (p 46)
<ul>
<li>Robert D. Ballard, director of Univ Rhode Island&#8217;s Institute for Underwater Archeology</li>
</ul>
</li>
<li>&#8220;Set Different Incentive Levels&#8221; (p 47)
<ul>
<li>Liu Chuanzhi, chairman of Legend Group of Beijing</li>
</ul>
</li>
<li>&#8220;Work Quickly Through Pain&#8221; (p 47)
<ul>
<li>Hank McKinnell, chairman and CEO of Pfizer</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.angelforge.org/wordpress/mba/moving-mountains/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Every Leader Needs to Know About Followers</title>
		<link>http://www.angelforge.org/wordpress/mba/what-every-leader-needs-to-know-about-followers/</link>
		<comments>http://www.angelforge.org/wordpress/mba/what-every-leader-needs-to-know-about-followers/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 17:30:18 +0000</pubDate>
		<dc:creator>Jamie</dc:creator>
				<category><![CDATA[mba]]></category>
		<category><![CDATA[article]]></category>

		<guid isPermaLink="false">http://www.angelforge.org/wordpress/?p=1949</guid>
		<description><![CDATA[Notes on: Kellerman, B. (2007, December). What Every Leader Needs to Know About Followers. Harvard Business Review, December 2007, p 84-91. Modern leadership Stress leaders rather than followers (amorphous) Followers matter! Not obvious who is leader and who is follower New typology for followers Who are followers? &#8220;Low in the hierarchy and have less power&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>Notes on:</p>
<p>Kellerman, B. (2007, December). What Every Leader Needs to Know About Followers. Harvard Business Review, December 2007, p 84-91.</p>
<ul>
<li>Modern leadership
<ul>
<li>Stress leaders rather than followers (amorphous)</li>
</ul>
</li>
<li>Followers matter!
<ul>
<li>Not obvious who is leader and who is follower</li>
<li>New typology for followers</li>
</ul>
</li>
<li>Who are followers?
<ul>
<li>&#8220;Low in the hierarchy and have less power&#8221; (p 86)</li>
<li>Free-agents (p 86)
<ul>
<li>Demise of communism</li>
<li>Dissolution of corporate oligarchies</li>
</ul>
</li>
<li>Knowledge can be more important than position</li>
</ul>
</li>
<li>Types of followers
<ul>
<li>Zaleznik &#8211; level of dominance, level of activity</li>
<li>Kelley &#8211; level of independence, level of activity</li>
<li>Chaleff &#8211; level of leader support</li>
<li>Why segment?
<ul>
<li>impose order</li>
<li>determine individual motivations within group</li>
</ul>
</li>
</ul>
</li>
<li>New Typology
<ul>
<li>Based on engagement level
<ul>
<li>This determines relationship with superiors</li>
</ul>
</li>
<li>Provides immediate information for leaders</li>
<li>Isolates &#8211; don&#8217;t know, don&#8217;t care</li>
<li>Bystanders &#8211; know, but don&#8217;t care</li>
<li>Participants &#8211; some engagement</li>
<li>Activists &#8211; engagement and feelings for leaders/org</li>
<li>Die-hards &#8211; prepared to give everything</li>
</ul>
</li>
<li>Good and Bad Followers
<ul>
<li>Good followers have interests of org over superior</li>
<li>Bad followers have interests of self or superior over org</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.angelforge.org/wordpress/mba/what-every-leader-needs-to-know-about-followers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

