<?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: Organizational Impossibility</title>
	<atom:link href="http://blog.lizardwrangler.com/2006/06/29/organizational-impossibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.lizardwrangler.com/2006/06/29/organizational-impossibility/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 14:51:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rafael</title>
		<link>http://blog.lizardwrangler.com/2006/06/29/organizational-impossibility/comment-page-1/#comment-48</link>
		<dc:creator>Rafael</dc:creator>
		<pubDate>Fri, 30 Jun 2006 18:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lizardwrangler.com/?p=81#comment-48</guid>
		<description>Right.  So Mozilla needs to be careful about using existing organizational models and usual roles and responsibilities and applying them to Mozilla.  In other words, more "phenomenologists" than Directors of "some department".

Should you care about employee career path/growth?  I didn't.

It'd be great to see Mozilla Corp function more like a non-profit entity, more research R&#038;D like, than a corp focused on release to release.

Releasing product is crucial, extremely important though I don't think the organization should be set-up or organized to be maximized for releases.

Currently releasing product seems to be the metric for success.  That's an easy metric, you ship or you don't within a quarter and you can measure how well the release was done quality/ performance/ participation / consumer adoption.

Are there other metrics that need to be created though that could be more important?

</description>
		<content:encoded><![CDATA[<p>Right.  So Mozilla needs to be careful about using existing organizational models and usual roles and responsibilities and applying them to Mozilla.  In other words, more &#8220;phenomenologists&#8221; than Directors of &#8220;some department&#8221;.</p>
<p>Should you care about employee career path/growth?  I didn&#8217;t.</p>
<p>It&#8217;d be great to see Mozilla Corp function more like a non-profit entity, more research R&#038;D like, than a corp focused on release to release.</p>
<p>Releasing product is crucial, extremely important though I don&#8217;t think the organization should be set-up or organized to be maximized for releases.</p>
<p>Currently releasing product seems to be the metric for success.  That&#8217;s an easy metric, you ship or you don&#8217;t within a quarter and you can measure how well the release was done quality/ performance/ participation / consumer adoption.</p>
<p>Are there other metrics that need to be created though that could be more important?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
