<?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: Building High Performance Teams</title>
	<atom:link href="http://akfpartners.com/techblog/2007/11/13/building-high-performance-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://akfpartners.com/techblog/2007/11/13/building-high-performance-teams/</link>
	<description>Technical and Leadership Thoughts</description>
	<lastBuildDate>Sat, 04 Jul 2009 12:46:07 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Abbott, Keeven, Fisher &#38;#038 Fortuna Partners</title>
		<link>http://akfpartners.com/techblog/2007/11/13/building-high-performance-teams/comment-page-1/#comment-223</link>
		<dc:creator>Abbott, Keeven, Fisher &#38;#038 Fortuna Partners</dc:creator>
		<pubDate>Wed, 18 Mar 2009 15:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2007/11/13/building-high-performance-teams/#comment-223</guid>
		<description>[...] a recession is a terrible thing to waste. You&#8217;ve heard us say it before in our posts such as Building High Performance Teams and Seed, Feed and Weed to Succeed, and we even reference this practice in our forthcoming book [...]</description>
		<content:encoded><![CDATA[<p>[...] a recession is a terrible thing to waste. You&#8217;ve heard us say it before in our posts such as Building High Performance Teams and Seed, Feed and Weed to Succeed, and we even reference this practice in our forthcoming book [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clipmarks Internal Clog &#187; Top 5 Reasons Tech Execs fail</title>
		<link>http://akfpartners.com/techblog/2007/11/13/building-high-performance-teams/comment-page-1/#comment-4</link>
		<dc:creator>Clipmarks Internal Clog &#187; Top 5 Reasons Tech Execs fail</dc:creator>
		<pubDate>Tue, 23 Sep 2008 16:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2007/11/13/building-high-performance-teams/#comment-4</guid>
		<description>[...] strong and that everyone plays a crucial role in the construction of the site.     Share this clip  Permalink  x [...]</description>
		<content:encoded><![CDATA[<p>[...] strong and that everyone plays a crucial role in the construction of the site.     Share this clip  Permalink  x [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abbott, Keeven, Fisher &#38;#038 Fortuna Consulting</title>
		<link>http://akfpartners.com/techblog/2007/11/13/building-high-performance-teams/comment-page-1/#comment-3</link>
		<dc:creator>Abbott, Keeven, Fisher &#38;#038 Fortuna Consulting</dc:creator>
		<pubDate>Sun, 24 Aug 2008 23:53:16 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2007/11/13/building-high-performance-teams/#comment-3</guid>
		<description>[...] CTOs who need to talk about being the “smartest person in the room” and CEOs who say “I’m right more often than I’m wrong” simply have no place in a high performing team.  Such statements alienate the rest of a team and very often will push the very highest performing individuals – those actually getting stuff done – out of the team and out of the company.  These actions and statements run counter to building the best of teams and over time will serve to destroy shareholder value.  The best leaders give of themselves selflessly in an ethical pursuit of creating shareholder value.  [...]</description>
		<content:encoded><![CDATA[<p>[...] CTOs who need to talk about being the “smartest person in the room” and CEOs who say “I’m right more often than I’m wrong” simply have no place in a high performing team.  Such statements alienate the rest of a team and very often will push the very highest performing individuals – those actually getting stuff done – out of the team and out of the company.  These actions and statements run counter to building the best of teams and over time will serve to destroy shareholder value.  The best leaders give of themselves selflessly in an ethical pursuit of creating shareholder value.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: F&#124;R: The Top 5 Reasons Tech Execs Fail - GigaOM</title>
		<link>http://akfpartners.com/techblog/2007/11/13/building-high-performance-teams/comment-page-1/#comment-2</link>
		<dc:creator>F&#124;R: The Top 5 Reasons Tech Execs Fail - GigaOM</dc:creator>
		<pubDate>Sat, 02 Aug 2008 16:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2007/11/13/building-high-performance-teams/#comment-2</guid>
		<description>[...] 5. Failure to Build World Class Team  As important as any other aspect of your job is the need to cultivate the best team possible given the limitations of your budget, mission and headcount. Rather than spending time on improving the capabilities of their teams, we find that many chief tech execs spend a great deal of time attempting to compensate for deficiencies within their teams. A very typical example of this is a CTO personally taking responsibility for every technology decision within a company. While this is a necessary practice when the team is very small, it does not scale into organizations of hundreds or thousands of engineers. All managers must be able to delegate to succeed. [...]</description>
		<content:encoded><![CDATA[<p>[...] 5. Failure to Build World Class Team  As important as any other aspect of your job is the need to cultivate the best team possible given the limitations of your budget, mission and headcount. Rather than spending time on improving the capabilities of their teams, we find that many chief tech execs spend a great deal of time attempting to compensate for deficiencies within their teams. A very typical example of this is a CTO personally taking responsibility for every technology decision within a company. While this is a necessary practice when the team is very small, it does not scale into organizations of hundreds or thousands of engineers. All managers must be able to delegate to succeed. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.390 seconds -->
