<?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>Shaun Abram &#187; leadership</title>
	<atom:link href="http://www.shaunabram.com/tag/leadership/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shaunabram.com</link>
	<description>Java and Technology weblog</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:06:07 +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>OSCON Day3 &#8211; The Joys of Engineering Leadership</title>
		<link>http://www.shaunabram.com/oscon-day3-leadership/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=oscon-day3-leadership</link>
		<comments>http://www.shaunabram.com/oscon-day3-leadership/#comments</comments>
		<pubDate>Sat, 24 Jul 2010 23:39:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Events]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[oscon]]></category>

		<guid isPermaLink="false">http://www.shaunabram.com/?p=958</guid>
		<description><![CDATA[The first talk of Day 3 at OSCON was &#8220;How to Lose Friends and Alienate People: The Joys of Engineering Leadership&#8221; by Brian &#8216;Fitz&#8217; Fitzpatrick and Ben Collins-Sussman, both from Google. What is an engineering leader? Serves the team Eliminates roadblocks Provides advice, guidance and helps get job done Mutual respect/Mutual trust Promotes technical and [...]]]></description>
			<content:encoded><![CDATA[<p>The first talk of Day 3 at <a href="http://www.oscon.com/oscon2010">OSCON</a> was &#8220;<a href="http://www.oscon.com/oscon2010/public/schedule/detail/13245">How to Lose Friends and Alienate People: The Joys of Engineering Leadership</a>&#8221; by Brian &#8216;Fitz&#8217; Fitzpatrick and Ben Collins-Sussman, both from Google. </p>
<p>What is an engineering leader? </p>
<ul>
<li>Serves the team</li>
<li>Eliminates roadblocks</li>
<li>Provides advice, guidance and helps get job done</li>
<li>Mutual respect/Mutual trust</li>
<li>Promotes technical and social health</li>
<li>Leadership is not a waste of time&#8230;</li>
<li>Being a team leader is a way of scaling yourself</li>
</ul>
<p>The speakers broke their talk on how to be a good leader down in to two sections, which were (in good coding tradition) patterns and anti-patterns&#8230;</p>
<p><span id="more-958"></span></p>
<h2>Anti patterns for leadership</h2>
<p>1. Be everyone&#8217;s friend<br />
Don&#8217;t try to be everyone&#8217;s friend because you still need to be a hard-ass sometimes. Instead, just try to maintain a healthy, working relationships. For example, try having lunch with your team regularly.</p>
<p>2. Treat reports as children<br />
Give responsibility and trust.</p>
<p>3. Micromanage<br />
Micromanagement breeds co-dependency. If you are off for a day, the team can&#8217;t work. They should work on their own initiative, without your commands.</p>
<p>4. Hire pushovers<br />
Don&#8217;t hire people that are dumber than you! If they are smarter, you will build and better team and learn more from them.</p>
<p>5. Compromise when hiring<br />
Don&#8217;t just just hire the top 10% of candidates you interview &#8211; they might not be good enough.</p>
<p>6. Ignore low performers<br />
Do not ignore them! Low performers are the obstacle in the road. They will not go away. Try to motivate them. Maybe need to more-micro-manage. Have an &#8216;acceptable&#8217; level bar.</p>
<p>7. Ignore human problems<br />
Don&#8217;t assume the team has no life outside of work. Keep morale up.</p>
<h2>Patterns</h2>
<p>1. Be honest<br />
There is no such thing as a temporary lapse of integrity!<br />
Deliver criticism directly, constructively and with empathy.<br />
Be honest about your motivation for making decisions.</p>
<p>2. Be a wise zen master<br />
If someone asks hard questions, you can respond with questions.<br />
Don&#8217;t try to manage people!</p>
<p>3. Lose the ego<br />
You don&#8217;t need to be the smartest person in the room. Trust others and respect their abilities.</p>
<p>Appreciate any inquiries the team has; Accept feedback and don&#8217;t be scared to apologize. Humility != Doormat</p>
<p>To influence, be influenceable.</p>
<p>4. Get your hands dirty<br />
Lead by example and understand the problems the team is going through.</p>
<p>5. Delegate<br />
Delegate even if another team member can&#8217;t do a job as well (or as quickly) as you think you can.</p>
<p>6. Seek to replace yourself</p>
<p>7. Make waves<br />
When you lease want to make waves, this is probably the time you should be making most waves.</p>
<p>8. Shield your teams from bureaucracy</p>
<p>9. Succeed and fail as a team<br />
Public praise, private criticism as everyone already knows when someone messed up.</p>
<p>10. Be a catalyst, a teacher and a mentor</p>
<p>12. Set clear goals<br />
Make sure everyone agrees on the milestones and the plan for a projects.<br />
Otherwise you get feature creep and get side tracked.</p>
<p>13. Track happiness &#038; careers<br />
If someone is not happy,find out why.<br />
What do team members want to be doing?<br />
Ask them what they need?<br />
Get everyone to work on fun stuff &#038; dull stuff. Change it up.</p>
<p>Give Autonomy &#038; Trust<br />
e.g. the 20% time @ Google</p>
<p>Mastery<br />
People want to grow; Always want to master new things; Give people a sense of purpose</p>
<p>Managing your manager<br />
Act like a grown up. Encourage people to take responsibility</p>
<p>Pursue responsibility<br />
Do more than is required. Deliver 110%<br />
Take calculate risks</p>
<p>If you fail &#8211; learn. And document the process and what was learned.</p>
<p>Communicate!!</p>
<p>Point out obstacles</p>
<p>Argue<br />
Good leaders don&#8217;t want yes men<br />
Give back structured criticism</p>
<h2>Conclusion</h2>
<p>3 words:</p>
<ul>
<li>Serve</li>
<li>Respect (give more, get more)</li>
<li>Motivate</li>
</ul>
<p>Stop being a manager, be a leader!</p>
<p>Finally, the speaker recommended checking out a talk by Dan Pink on Intrinsic vs Extrinsic Motivations. I think <a href="http://www.ted.com/talks/dan_pink_on_motivation.html">this</a> is it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shaunabram.com/oscon-day3-leadership/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

