<?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"
	>
<channel>
	<title>Comments on: Teach Skills and Tools, not Programs and Rules</title>
	<atom:link href="http://www.tinyscreenfuls.com/2008/06/teach-skills-and-tools-not-programs-and-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tinyscreenfuls.com/2008/06/teach-skills-and-tools-not-programs-and-rules/</link>
	<description>Edge Case, Community Builder, Tinkerer, and Teacher</description>
	<pubDate>Sat, 22 Nov 2008 02:01:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Mike.Mathews</title>
		<link>http://www.tinyscreenfuls.com/2008/06/teach-skills-and-tools-not-programs-and-rules/#comment-74353</link>
		<dc:creator>Mike.Mathews</dc:creator>
		<pubDate>Fri, 20 Jun 2008 00:32:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.tinyscreenfuls.com/?p=1990#comment-74353</guid>
		<description>I think you've discovered the key for building a culture: you get everyone to teach another about some aspect of that culture. That's why Intel has managers teaching classes in meetings and ethics and such. But building a culture takes a long time, so one needs to be prepared to track slow change over a long period.

Short term change is still probably best accomplished through strategy, rules, etc., just like you've mentioned. But, just like a habit that is hard to break, people will return to their pre-existing methods once the program is complete. A short term change is not a cultural change.

Also, with cultural change you'll have people drop out and leave because they do not fit the culture, which is good for developing a consistent culture, but it loses the invigorating slap of comparison and innovation forced by working with differences.

I think one needs to have a goal; a strategy is probably good to have, but it may be unnecessary; the habits of the individuals leading the culture will identify the skills.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;ve discovered the key for building a culture: you get everyone to teach another about some aspect of that culture. That&#8217;s why Intel has managers teaching classes in meetings and ethics and such. But building a culture takes a long time, so one needs to be prepared to track slow change over a long period.</p>
<p>Short term change is still probably best accomplished through strategy, rules, etc., just like you&#8217;ve mentioned. But, just like a habit that is hard to break, people will return to their pre-existing methods once the program is complete. A short term change is not a cultural change.</p>
<p>Also, with cultural change you&#8217;ll have people drop out and leave because they do not fit the culture, which is good for developing a consistent culture, but it loses the invigorating slap of comparison and innovation forced by working with differences.</p>
<p>I think one needs to have a goal; a strategy is probably good to have, but it may be unnecessary; the habits of the individuals leading the culture will identify the skills.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kenekaplan</title>
		<link>http://www.tinyscreenfuls.com/2008/06/teach-skills-and-tools-not-programs-and-rules/#comment-74181</link>
		<dc:creator>kenekaplan</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.tinyscreenfuls.com/?p=1990#comment-74181</guid>
		<description>All sounds very familiar.  Strategy is great but has a dark side:  it becomes an excuse/process for not doing things.  

Your post also reminds me of something our pal Aaron said while driving to Portland Monday.  We can get paid to learn or we can get paid to teach.  Usually the latter pays better.  I believe is we really like what we do we are doing both -- learning and teaching.  

What would be interesting is to see companies actually put more value on employees who are sharing their skills and toolkits with others.  That would drive everyone to keep learning to feed the cycle.  Where do we learn?  At work -- in good meetings! -- at home and especially at events where we share stories beyond "what's up" and into "how are your feeling and how's life comin' at you?"

I'm looking forward to your next mindspring on this topic.  Thanks, Josh!  Bet you're having a blast at Ignite.</description>
		<content:encoded><![CDATA[<p>All sounds very familiar.  Strategy is great but has a dark side:  it becomes an excuse/process for not doing things.  </p>
<p>Your post also reminds me of something our pal Aaron said while driving to Portland Monday.  We can get paid to learn or we can get paid to teach.  Usually the latter pays better.  I believe is we really like what we do we are doing both &#8212; learning and teaching.  </p>
<p>What would be interesting is to see companies actually put more value on employees who are sharing their skills and toolkits with others.  That would drive everyone to keep learning to feed the cycle.  Where do we learn?  At work &#8212; in good meetings! &#8212; at home and especially at events where we share stories beyond &#8220;what&#8217;s up&#8221; and into &#8220;how are your feeling and how&#8217;s life comin&#8217; at you?&#8221;</p>
<p>I&#8217;m looking forward to your next mindspring on this topic.  Thanks, Josh!  Bet you&#8217;re having a blast at Ignite.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Smith</title>
		<link>http://www.tinyscreenfuls.com/2008/06/teach-skills-and-tools-not-programs-and-rules/#comment-74010</link>
		<dc:creator>Greg Smith</dc:creator>
		<pubDate>Wed, 18 Jun 2008 01:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.tinyscreenfuls.com/?p=1990#comment-74010</guid>
		<description>Intel is a engineering company. They engineer microchips, blogging, safety... whatever.</description>
		<content:encoded><![CDATA[<p>Intel is a engineering company. They engineer microchips, blogging, safety&#8230; whatever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peat</title>
		<link>http://www.tinyscreenfuls.com/2008/06/teach-skills-and-tools-not-programs-and-rules/#comment-74008</link>
		<dc:creator>Peat</dc:creator>
		<pubDate>Wed, 18 Jun 2008 00:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.tinyscreenfuls.com/?p=1990#comment-74008</guid>
		<description>I think Ze Frank had the key to finding things to blog about: figuring out how to "bust that cycle."  The video (http://www.zefrank.com/theshow/archives/2006/09/092006.html) is priceless.  My weak summary is that finding that "kick ass!" thing to blog just means trying odd things to break out of your day-to-day habits.  Stay up all night.  Go somewhere different for lunch.  Build a peanut butter and jelly sandwich with your face (no, really, watch the video).  

A new perspective can be illuminating and exciting, and that's what makes blogs worth reading.

Figuring out how to bust your own cycle is a skill, for sure.  Way better than setting up a system to bait or provoke your coworkers into blogging ...</description>
		<content:encoded><![CDATA[<p>I think Ze Frank had the key to finding things to blog about: figuring out how to &#8220;bust that cycle.&#8221;  The video (http://www.zefrank.com/theshow/archives/2006/09/092006.html) is priceless.  My weak summary is that finding that &#8220;kick ass!&#8221; thing to blog just means trying odd things to break out of your day-to-day habits.  Stay up all night.  Go somewhere different for lunch.  Build a peanut butter and jelly sandwich with your face (no, really, watch the video).  </p>
<p>A new perspective can be illuminating and exciting, and that&#8217;s what makes blogs worth reading.</p>
<p>Figuring out how to bust your own cycle is a skill, for sure.  Way better than setting up a system to bait or provoke your coworkers into blogging &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
