<?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>Project Oriel &#187; business culture</title>
	<atom:link href="http://www.edstrom.net/blog/archive/tag/business-culture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.edstrom.net/blog</link>
	<description>Embracing Change</description>
	<lastBuildDate>Tue, 07 Feb 2012 03:39:18 +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>The Knowing Doing Gap</title>
		<link>http://www.edstrom.net/blog/archive/the-knowing-doing-gap/</link>
		<comments>http://www.edstrom.net/blog/archive/the-knowing-doing-gap/#comments</comments>
		<pubDate>Mon, 01 Aug 2011 03:20:32 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[learning]]></category>
		<category><![CDATA[work environment]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1409</guid>
		<description><![CDATA[I recently started reading the book, The Knowing Doing Gap, How Smart Companies Turn Knowledge into Action by Jeffrey Pfeffer (Professor of Organizational Behavior, Stanford) and Robert Sutton (Professor of Management science, Stanford). I&#8217;ve been a long-time follower of Bob Sutton&#8217;s blog, and it was about time I picked up one of his books to [...]]]></description>
			<content:encoded><![CDATA[<p>I recently started reading the book, <a href="http://www.amazon.com/Knowing-Doing-Gap-Companies-Knowledge-Action/dp/1578511240">The Knowing Doing Gap</a>, How Smart Companies Turn Knowledge into Action by <a href="http://www.jeffreypfeffer.com/">Jeffrey Pfeffer</a> (Professor of Organizational Behavior, Stanford) and <a href="http://bobsutton.typepad.com/">Robert Sutton</a> (Professor of Management science, Stanford).</p>
<p>I&#8217;ve been a long-time follower of Bob Sutton&#8217;s <a href="http://bobsutton.typepad.com/">blog</a>, and it was about time I picked up one of his books to read. To my way of thinking, Bob has some fairly sensible advice for working with people, and I&#8217;d suggest you take a moment to hear what he has to say.</p>
<p>From the Preface:</p>
<p style="padding-left: 30px;">&#8220;But once something was clearly not working [while writing the book], we abandoned the path quickly, stopping just long enough to figure out what we should learn before trying something new. We never stopped to worry about how much time we had wasted and never spent one minute talking about which one of us was to blame for the last dead end. Rather we were inspired by the successful firms we studied, in which setbacks and mistakes were viewed as an inevitable, even desirable, part of being action oriented. We heeded their advice that <strong>the only true failure was to stop trying new things and to stop learning from the last effort</strong> to turn knowledge into action.&#8221;</p>
<p> Great advice for being action oriented &#8212; from the preface, no less!</p>
<ol>
<li>Recognize that something isn&#8217;t working. (This is often easier said than done.)</li>
<li>Abandon that path quickly.</li>
<li>Figure out what to learn from the last effort, and try something new.</li>
<li>Don&#8217;t worry about wasted time, nor assigning blame.</li>
<li>View setbacks and mistakes as desirable.</li>
<li>The worst thing you can do is to stop trying new things.</li>
</ol>
<p>My questions to you are: When did you last fail in front of your whole team (maybe even your whole company)? What did you learn? What are you trying now?</p>
<p>Can&#8217;t wait to read the rest of the book!</p>
<p>- Peter</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/the-knowing-doing-gap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Focus</title>
		<link>http://www.edstrom.net/blog/archive/focus/</link>
		<comments>http://www.edstrom.net/blog/archive/focus/#comments</comments>
		<pubDate>Wed, 09 Feb 2011 19:02:50 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[urgency]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1384</guid>
		<description><![CDATA[Hoarce Dediu; Why focusing on a few products is hard: But “focus” is the willful rejection of this theory. By saying no to alternatives you increase risk disproportionally to the reward. If you have the means to maintain a portfolio it certainly seems imprudent not to do so. So why would someone want to focus? [...]]]></description>
			<content:encoded><![CDATA[<p>Hoarce Dediu; <a href="http://www.asymco.com/2011/02/09/why-focusing-on-a-few-products-is-hard/">Why focusing on a few products is hard</a>:</p>
<blockquote><p>But “focus” is the willful rejection of this theory. By saying no to alternatives you increase risk disproportionally to the reward. If you have the means to maintain a portfolio it certainly seems imprudent not to do so.</p>
<p>So why would someone want to focus?</p>
<p>The answer is that too much diversification is dangerous. It’s dilutive to everything the company uses to create value: its resources, its processes and its priorities. It dulls the mind and tarnishes the brand.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/focus/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Time Waste</title>
		<link>http://www.edstrom.net/blog/archive/time-waste/</link>
		<comments>http://www.edstrom.net/blog/archive/time-waste/#comments</comments>
		<pubDate>Sat, 13 Nov 2010 19:32:51 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[lean]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1326</guid>
		<description><![CDATA[Henry Ford: &#8220;Time waste differs from material waste in that there can be no salvage. The easiest of all wastes and the hardest to correct is the waste of time, because wasted time does not litter the floor like wasted material.&#8221; Time wastes are hard to see, and even harder to fix. Take for example, [...]]]></description>
			<content:encoded><![CDATA[<p>Henry Ford:</p>
<blockquote><p>&#8220;Time waste differs from material waste in that there can be no salvage.  The easiest of all wastes and the hardest to correct is the waste of time, because wasted time does not litter the floor like wasted material.&#8221;</p></blockquote>
<p>Time wastes are hard to see, and even harder to fix.</p>
<p>Take for example, communicating an idea to someone. You could spend 30 minutes crafting what you think is a perfectly clear email, or you could just talk to them for 5 minutes and let them ask a few questions. Who knows, they may understand your idea far faster than you thought.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/time-waste/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Right Team</title>
		<link>http://www.edstrom.net/blog/archive/the-right-team/</link>
		<comments>http://www.edstrom.net/blog/archive/the-right-team/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 18:20:24 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1319</guid>
		<description><![CDATA[Jim Collins, in Good to Great: &#8220;We expected that good-to-great leaders would begin by setting a new vision and strategy. We found instead that they first got the right people on the bus, the wrong people off the bus, and the right people in the right seats &#8211; and then they figured out where to [...]]]></description>
			<content:encoded><![CDATA[<p>Jim Collins, in <a href="http://www.jimcollins.com/">Good to Great</a>:</p>
<p style="padding-left: 30px;">&#8220;We expected that good-to-great leaders would begin by setting a new vision and strategy. We found instead that they <em>first </em>got the right people on the bus, the wrong people off the bus, and the right people in the right seats &#8211; and <em>then </em>they figured out where to drive it. The old adage &#8220;People are your most important asset&#8221; turns out to be wrong. People are <em>not </em>your most important asset. The <em>right </em>people are.&#8221;</p>
<p>I think <a href="http://www.edstrom.net/blog/archive/create-a-vision-and-reward-failures-agile2009/">vision and strategy</a> are important (just watch the <a href="http://video.google.com/videoplay?docid=-5144094928842683632">Knowledge Navigator</a> from Apple&#8217;s distant past to understand how they got to be where they are today), but getting the right people in the right places is far more important.  Studies have found <a href="http://forums.construx.com/blogs/stevemcc/archive/2008/03/27/productivity-variations-among-software-developers-and-teams-the-origin-of-quot-10x-quot.aspx">10-fold differences in productivity</a> between different programmers, and I see no reason why that wouldn&#8217;t apply to other roles. New tools routinely are found to be <a href="http://www.edstrom.net/blog/archive/exponentially-more-productive/">exponentially more useful</a> than their predecessors.</p>
<blockquote><p>&#8220;the purpose of bureaucracy is to compensate for incompetence and lack of discipline &#8211; a problem that largely goes away if you have the right people in the first place.&#8221; &#8211; Jim Collins</p>
<p>&#8220;People can learn skills and acquire knowledge, but they cannot learn  the essential character traits that make them right for your  organization.&#8221;- Jim Collins</p></blockquote>
<p>I&#8217;m not a fan of <a href="http://www.edstrom.net/blog/archive/turn-your-workers-into-machines/">calling people resources</a>, but perhaps in the sense that they are the foundation of <em>any </em>company, people are by far your most important asset. Get the right people on the team <em>first</em>, and there&#8217;s nothing you can&#8217;t do exponentially better (or 10-fold better) than your competitors.</p>
<p><a href="http://www.sethgodin.com/sg/">Seth Godin</a>, describes these people:</p>
<blockquote><p>&#8220;Is there anyone in an organization who is absolutely irreplaceable? Probably not. But the most essential people are so difficult to replace, so risky to lose, and so valuable that they might as well be irreplaceable.&#8221;</p></blockquote>
<p>Now <em>that </em>is the type of person you want filling each and every role on your team.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/the-right-team/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Good Ideas</title>
		<link>http://www.edstrom.net/blog/archive/good-ideas/</link>
		<comments>http://www.edstrom.net/blog/archive/good-ideas/#comments</comments>
		<pubDate>Sat, 06 Nov 2010 03:09:40 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[learning]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1316</guid>
		<description><![CDATA[Worth watching: Where Good Ideas Come From by Steven Johnson. It is a &#8220;trailer&#8221; for a recently released book. Same folks did this one as Dan Pink&#8217;s The Surprising Truth About What Motivates Us. Video:]]></description>
			<content:encoded><![CDATA[<p>Worth watching: <a href="http://www.youtube.com/watch?v=NugRZGDbPFU">Where Good Ideas Come From</a> by Steven Johnson. It is a &#8220;trailer&#8221; for a recently released book. Same folks did this one as Dan Pink&#8217;s <a href="http://www.edstrom.net/blog/archive/motivate-with-real-projects/">The Surprising Truth About What Motivates Us</a>.</p>
<p>Video:</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="640" height="385" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/NugRZGDbPFU?fs=1&amp;hl=en_US" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="640" height="385" src="http://www.youtube.com/v/NugRZGDbPFU?fs=1&amp;hl=en_US" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/good-ideas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Focusing on Value</title>
		<link>http://www.edstrom.net/blog/archive/focusing-on-value/</link>
		<comments>http://www.edstrom.net/blog/archive/focusing-on-value/#comments</comments>
		<pubDate>Tue, 19 Oct 2010 03:52:42 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[value]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1285</guid>
		<description><![CDATA[Esther Derby recommends you focus on value, not on costs: &#8220;A small engineering firm axed the company lunch room and eliminated over $200,000 per year in costs. That gave an immediate boost to the bottom line. [... however,] A more insidious side-effect was invisible (at least on the balance sheet) for several months.&#8221; Read her full [...]]]></description>
			<content:encoded><![CDATA[<p>Esther Derby recommends you <a href="http://www.estherderby.com/2010/09/improve-financial-results-by-focusing-on-value-not-costs.html">focus on value, not on costs</a>:</p>
<blockquote><p>&#8220;A small engineering firm axed the company lunch room and eliminated over $200,000 per year in costs. That gave an immediate boost to the bottom line. [... however,] A more insidious side-effect was invisible (at least on the balance sheet) for several months.&#8221;</p></blockquote>
<p>Read her <a href="http://www.estherderby.com/2010/09/improve-financial-results-by-focusing-on-value-not-costs.html">full post</a> to see what havoc this cost saving effort did to the company.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/focusing-on-value/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Another procedure?</title>
		<link>http://www.edstrom.net/blog/archive/another-procedure/</link>
		<comments>http://www.edstrom.net/blog/archive/another-procedure/#comments</comments>
		<pubDate>Tue, 28 Sep 2010 17:46:14 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[simplicity]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1256</guid>
		<description><![CDATA[Seth Godin in Linchpin: &#8220;Fear of living without a map is the main reason people are so insistent that we tell them what to do. The reasons are pretty obvious: If it&#8217;s someone else&#8217;s map, it&#8217;s not your fault if it doesn&#8217;t work out. If you&#8217;ve memorized the sales script I gave you and you [...]]]></description>
			<content:encoded><![CDATA[<p>Seth Godin in <a href="http://www.sethgodin.com/sg/books.asp">Linchpin</a>:</p>
<blockquote><p>&#8220;Fear of living without a map is the main reason people are so insistent that we tell them what to do. The reasons are pretty obvious: If it&#8217;s someone else&#8217;s map, it&#8217;s not your fault if it doesn&#8217;t work out. If you&#8217;ve memorized the sales script I gave you and you don&#8217;t make the sale, who&#8217;s in trouble now?&#8221;</p></blockquote>
<p>I think this sums up the #1 reason I hate procedures. They are used to deflect blame.</p>
<p>My second reason I hate procedures? They are a tactical admission that even though something is so complicated it has to be written down, there is no desire to make it simpler and better. My vote: incrementally make it better till you don&#8217;t need the procedure any more.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/another-procedure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great Design</title>
		<link>http://www.edstrom.net/blog/archive/great-design/</link>
		<comments>http://www.edstrom.net/blog/archive/great-design/#comments</comments>
		<pubDate>Sat, 28 Aug 2010 02:35:02 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[software development]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1230</guid>
		<description><![CDATA[Fred Brooks in an interview with Wired: &#8220;Great design does not come from great processes; it comes from great designers.&#8221; This seems so natural and correct when talking about design. Applied to other professions, you might see: Great software does not come from great processes; it comes from great developers. Great engineering does not come [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.wired.com/magazine/2010/07/ff_fred_brooks">Fred Brooks in an interview</a> with Wired:</p>
<blockquote><p>&#8220;Great design does not come from great processes; it comes from great designers.&#8221;</p></blockquote>
<p>This seems so natural and correct when talking about design. Applied to other professions, you might see:</p>
<ul>
<li>Great <em>software</em> does not come from great processes; it comes from great <em>developers</em>.</li>
<li>Great <em>engineering</em> does not come from great processes; it comes from great <em>engineers</em>.</li>
<li>Great <em>testing</em> does not come from great processes; it comes from great <em>testers</em>.</li>
<li>Great <em>management</em> does not come from great processes; it comes from great <em>managers</em>.</li>
</ul>
<p>Yet time and time again, we lean back on the processes that in the best of situations are mediocre and brittle.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/great-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can we fix it? Yes we &#8230; no, wait &#8230; Maybe!</title>
		<link>http://www.edstrom.net/blog/archive/can-we-fix-it-yes-we-no-wait-maybe/</link>
		<comments>http://www.edstrom.net/blog/archive/can-we-fix-it-yes-we-no-wait-maybe/#comments</comments>
		<pubDate>Wed, 18 Aug 2010 01:47:17 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1212</guid>
		<description><![CDATA[Daniel Pink writing for the Telegraph: &#8220;Most of us believe in positive self-talk. &#8220;I can achieve anything,&#8221; we mouth to the mirror in the morning. &#8220;Nobody can stop me,&#8221; we tell ourselves before walking into a big meeting. We believe we&#8217;ll do better if we banish doubts about our ability or our strategy and instead [...]]]></description>
			<content:encoded><![CDATA[<p>Daniel Pink <a href="http://www.telegraph.co.uk/finance/businessclub/7839988/Can-we-fix-it-is-the-right-question-to-ask.html">writing for the Telegraph</a>:</p>
<blockquote><p>&#8220;Most of us believe in positive self-talk. &#8220;I can achieve anything,&#8221; we mouth to the mirror in the morning. &#8220;Nobody can stop me,&#8221; we tell ourselves before walking into a big meeting. We believe we&#8217;ll do better if we banish doubts about our ability or our strategy and instead muster an inner voice that affirms our awesomeness.</p>
<p>But not Bob [the Builder]. Instead of puffing up himself and his team, he first wonders whether they can actually achieve their goal.&#8221;</p></blockquote>
<p>Pink then dives into some research on whether positive self-talk actually improves performance or not.</p>
<p>Spoiler: Having doubts improves performance.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/can-we-fix-it-yes-we-no-wait-maybe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fairly Good Estimators</title>
		<link>http://www.edstrom.net/blog/archive/fairly-good-estimators/</link>
		<comments>http://www.edstrom.net/blog/archive/fairly-good-estimators/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 01:51:11 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[urgency]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1194</guid>
		<description><![CDATA[Johanna Rothman in Maintaining Project Agility has a positive take on the skill of estimating: &#8220;In my experience, most engineers with more than five years of experience are actually fairly good estimators, they just can’t estimate the amount of weekly bureaucracy they have to deal with.&#8221;]]></description>
			<content:encoded><![CDATA[<p>Johanna Rothman in <a href="http://www.jrothman.com/Papers/Cutter/projectagility.html">Maintaining Project Agility</a> has a positive take on the skill of estimating:</p>
<blockquote><p>&#8220;In my experience, most engineers with more than five years of experience are actually fairly good estimators, they just can’t estimate the amount of weekly bureaucracy they have to deal with.&#8221;</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/fairly-good-estimators/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You got an Apple in your Corporate</title>
		<link>http://www.edstrom.net/blog/archive/you-got-an-apple-in-your-corporate/</link>
		<comments>http://www.edstrom.net/blog/archive/you-got-an-apple-in-your-corporate/#comments</comments>
		<pubDate>Tue, 20 Jul 2010 11:20:20 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[corp]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iphone]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1190</guid>
		<description><![CDATA[Apple doesn&#8217;t belong in a Corporate environment, right? Well someone forgot to tell Wells Fargo, SAP, and Mercedes-Benz: &#8220;[They] are using the tablet-style computer for tasks as varied as accessing work e-mail, approving shipping orders, and calling up on-the-spot auto-finance options.&#8221; It takes time to change things, but now that Apple is bigger than Microsoft, [...]]]></description>
			<content:encoded><![CDATA[<p>Apple doesn&#8217;t belong in a Corporate environment, right? Well <a href="http://www.businessweek.com/technology/content/jul2010/tc2010076_193868.htm?campaign_id=yhoo">someone forgot to tell</a> Wells Fargo, SAP, and Mercedes-Benz:</p>
<blockquote><p>&#8220;[They] are using the tablet-style computer for tasks as varied as accessing work e-mail, approving shipping orders, and calling up on-the-spot auto-finance options.&#8221;</p></blockquote>
<p>It takes time to change things, but now that Apple is bigger than Microsoft, one has to wonder how long corporate will continue to cling to the underdog.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/you-got-an-apple-in-your-corporate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beliefs</title>
		<link>http://www.edstrom.net/blog/archive/beliefs/</link>
		<comments>http://www.edstrom.net/blog/archive/beliefs/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 03:26:01 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[scalability]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[world]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=266</guid>
		<description><![CDATA[Beliefs: The framework of things you hold to be true, and of which form the basis for all of your decisions. Here are some of mine. Which do you disagree with? Why? Workarounds are never a good thing. Short term workarounds are never short-term. They should be avoided. Do it right the first time, and [...]]]></description>
			<content:encoded><![CDATA[<p><em>Beliefs: The framework of things you hold to be true, and of which form the basis for all of your decisions. </em></p>
<p>Here are some of mine. Which do you disagree with? Why?</p>
<p><strong>Workarounds are never a good thing.</strong> Short term workarounds are never short-term. They should be avoided. Do it right the first time, and if you can&#8217;t due to time or budget, delay the project. I hate technical debt.</p>
<p><strong>Plan as you go is more appropriate to life and to projects, and returns better results, than planning everything up front (ie agile vs. waterfall).</strong> What we are talking about is <a href="http://www.edstrom.net/blog/archive/predicting-the-future-planning-projects/">predicting the future</a>. Sure, you can be <a href="http://www.edstrom.net/blog/archive/estimates/">somewhat</a> accurate, some of the time. But it&#8217;s just a <a href="http://www.edstrom.net/blog/archive/planning-is-only-a-guess/">guess</a>. You&#8217;ll be more accurate if you don&#8217;t predict too far out. If you&#8217;re more accurate, you&#8217;ll be happier.</p>
<p><strong>The problems of new are less than the problems of the old.</strong> On occasion you will run into a bug by upgrading software to the latest version. But I&#8217;ve found that on balance, I have far fewer compatibility &amp; stability problems if I keep up to date. And as a bonus, new features!</p>
<p><strong>Buy the well-built item once instead of the cheap thing multiple times.</strong> It&#8217;s eco-friendly, and you get to have the quality item to use every day. My wife and I had been wearing out a $10 garlic press once every 12 months or so with basic wear and tear &#8212; till we bought the <a href="http://www.williams-sonoma.com/products/4517736/?catalogId=91&amp;bnrid=3154701&amp;cm_ven=Shopping&amp;cm_cat=MSN_Shopping&amp;cm_pla=default&amp;cm_ite=default">Rösle Garlic Press</a> for (at the time) $30. Five years later, it still looks good as new and works brilliantly.</p>
<p><strong>Price is not correlated to the value.</strong> Just because it&#8217;s expensive doesn&#8217;t mean it&#8217;s worth a lot. Conversely, just because it&#8217;s cheap doesn&#8217;t mean it has no value. Open-Source Software, Wikipedia, a walk with your kids &#8211; these all have a lot of value, and they don&#8217;t cost you a dime.</p>
<p><strong>Deals are rarely worth it.</strong> Everything is &#8220;on sale&#8221;. Everything is discounted. Of course, there <em>are</em> good deals to be had. It&#8217;s just that the effort to find and take advantage of the deal is more costly than any savings I might obtain. There is a reason why rebate forms are difficult to complete: it is in the company&#8217;s best interest that you never fill them out.</p>
<p><strong>I believe in Scaling Software over Scaling People.</strong> See my blip on <a href="http://www.edstrom.net/blog/archive/techies-and-the-business/">Techies and The Business</a>, or the whole article <a href="http://plpatterns.com/post/55433565/techies-vs-the-business">here</a>.</p>
<p><strong>The most important attribute to any employee is their willingness and ability to learn.</strong> I&#8217;ve written about this one a lot. I think <a href="http://www.edstrom.net/blog/archive/on-unleashing-innovation/">learning is the key to innovation</a>, that<a href="http://www.edstrom.net/blog/archive/make-more-mistakes/"> through mistakes you get better</a>, that <a href="http://www.edstrom.net/blog/archive/most-crucial-skill-youll-ever-learn/">Adapting is the Most Crucial Skill You’ll Ever Learn</a>, and that progress (and who doesn&#8217;t want progress?) is <a href="http://www.edstrom.net/blog/archive/doing-it-right-the-first-time/">an act of discovery</a>.</p>
<p>So!  What are some of your beliefs?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/beliefs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Estimates</title>
		<link>http://www.edstrom.net/blog/archive/estimates/</link>
		<comments>http://www.edstrom.net/blog/archive/estimates/#comments</comments>
		<pubDate>Mon, 14 Jun 2010 19:54:57 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1150</guid>
		<description><![CDATA[I&#8217;ve said it before and Jonathan Rasmusson said it again: &#8220;Let’s face it. Our industry has had some challenges when it comes to setting expectations around estimates on software projects. It’s not that our estimates are necessarily wrong (though they almost always are). It’s more that too often people have looked to estimates for something they can never give—an accurate [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve said it <a href="http://www.edstrom.net/blog/archive/predicting-the-future-planning-projects/">before</a> and <a href="http://www.pragprog.com/titles/jtrap/the-agile-samurai">Jonathan Rasmusson</a> said it again:</p>
<blockquote><p>&#8220;Let’s face it. Our industry has had some challenges when it comes to setting expectations around estimates on software projects. It’s not that our estimates are necessarily wrong (though they almost always are). It’s more that too often people have looked to estimates for something they can never give—an accurate prediction of the future. [...] <strong>The simple fact is that accurate upfront estimates aren’t possible and we need to stop pretending that they are.</strong>&#8220;</p></blockquote>
<p>[emphasis added]</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/estimates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Businesses Don’t Experiment</title>
		<link>http://www.edstrom.net/blog/archive/why-businesses-don%e2%80%99t-experiment/</link>
		<comments>http://www.edstrom.net/blog/archive/why-businesses-don%e2%80%99t-experiment/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 12:59:44 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1116</guid>
		<description><![CDATA[Harvard Business Review: &#8220;Companies pay amazing amounts of money to get answers from consultants with overdeveloped confidence in their own intuition. Managers rely on focus groups—a dozen people riffing on something they know little about—to set strategies. And yet, companies won’t experiment to find evidence of the right way forward.&#8221; The same can be seen [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://hbr.org/2010/04/column-why-businesses-dont-experiment/ar/1">Harvard Business Review</a>:</p>
<blockquote><p>&#8220;Companies pay amazing amounts of money to get answers from consultants  with overdeveloped confidence in their own intuition. Managers rely on  focus groups—a dozen people riffing on something they know little  about—to set strategies. And yet, companies won’t experiment to find  evidence of the right way forward.&#8221;</p></blockquote>
<p>The same can be seen with <a href="http://www.edstrom.net/blog/archive/fighting-fires-instead-of-owning-the-problem/">fighting fires</a>: They don&#8217;t want to try something and fail, and they don&#8217;t want to be at fault if they do fail &#8230; so hire consultants!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/why-businesses-don%e2%80%99t-experiment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SFW</title>
		<link>http://www.edstrom.net/blog/archive/sfw/</link>
		<comments>http://www.edstrom.net/blog/archive/sfw/#comments</comments>
		<pubDate>Sat, 17 Apr 2010 02:40:57 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1108</guid>
		<description><![CDATA[&#8220;Everybody knows what NSFW means. [...] But what about safe for work?&#8221; Seth Godin asks some good questions in his post SFW.]]></description>
			<content:encoded><![CDATA[<p>&#8220;Everybody knows what NSFW means. [...] But what about <em>safe for work</em>?&#8221;</p>
<p>Seth Godin <a href="http://sethgodin.typepad.com/seths_blog/2010/03/sfw.html">asks some good questions in his post SFW</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/sfw/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Analysis Paralysis</title>
		<link>http://www.edstrom.net/blog/archive/analysis-paralysis/</link>
		<comments>http://www.edstrom.net/blog/archive/analysis-paralysis/#comments</comments>
		<pubDate>Tue, 13 Apr 2010 02:26:19 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[work environment]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1105</guid>
		<description><![CDATA[In case you forgot what it means: &#8220;Analysis paralysis is a phrase that describes a situation where the opportunity cost of decision analysis exceeds the benefits that could be gained by enacting some decision, or an informal or non-deterministic situation where the sheer quantity of analysis overwhelms the decision making process itself, thus preventing a decision. The [...]]]></description>
			<content:encoded><![CDATA[<p>In case you forgot <a href="http://en.wikipedia.org/wiki/Analysis_paralysis">what it means</a>:</p>
<blockquote><p>&#8220;<strong>Analysis paralysis</strong> is a phrase that describes a situation where the <a title="Opportunity cost" href="http://en.wikipedia.org/wiki/Opportunity_cost">opportunity cost</a> of <a title="Decision analysis" href="http://en.wikipedia.org/wiki/Decision_analysis">decision analysis</a> exceeds the benefits that could be gained by enacting some decision, or an informal or non-deterministic situation where the sheer quantity of analysis overwhelms the decision making process itself, thus preventing a decision. The phrase applies to any situation where analysis may be applied to help make a decision and may be a <a title="Dysfunctional" href="http://en.wikipedia.org/wiki/Dysfunctional">dysfunctional</a> element of <a title="Organizational behavior" href="http://en.wikipedia.org/wiki/Organizational_behavior">organizational behavior</a>.&#8221;</p></blockquote>
<p>I like how the see-also section refers you to <a href="http://en.wikipedia.org/wiki/Wicked_problems">Wicked problems</a>:</p>
<blockquote><p>&#8220;a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize. Moreover, because of complex interdependencies, the effort to solve one aspect of a wicked problem may reveal or create other problems.&#8221;</p></blockquote>
<p>&lt;sigh&gt;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/analysis-paralysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Time Poverty and the Cult of Busy</title>
		<link>http://www.edstrom.net/blog/archive/time-poverty-and-the-cult-of-busy/</link>
		<comments>http://www.edstrom.net/blog/archive/time-poverty-and-the-cult-of-busy/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 01:01:06 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[urgency]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1080</guid>
		<description><![CDATA[Scott Berkun (author of The Myths of Innovation)  writes: &#8220;[...] What people really mean when they say “I don’t have time” is this thing is not important enough to earn my time. It’s a polite way to tell people they’re not worth your time. This means people who are always busy are time poor. They have [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.scottberkun.com/blog/2010/the-cult-of-busy/">Scott Berkun</a> (author of The Myths of Innovation)  writes:</p>
<blockquote><p>&#8220;[...] What people really mean when they say “I don’t have time” is this thing is not important enough to earn my time. It’s a polite way to tell people they’re not worth your time.</p>
<p>This means people who are always busy are <a href="http://www.scottberkun.com/blog/2010/the-cult-of-busy/">time poor</a>. They have a time shortage. They have time debt. They are either trying to do too much, or they aren’t doing what they’re doing very well. They are failing to either a) be effective with their time b) don’t know what they’re trying to effect, so they scramble away at trying to optimize for  everything, which leads to optimizing nothing.&#8221;</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/time-poverty-and-the-cult-of-busy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fighting Fires instead of Owning the Problem</title>
		<link>http://www.edstrom.net/blog/archive/fighting-fires-instead-of-owning-the-problem/</link>
		<comments>http://www.edstrom.net/blog/archive/fighting-fires-instead-of-owning-the-problem/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 02:11:15 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[urgency]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=1071</guid>
		<description><![CDATA[Jeffrey Phillips: Why is fighting fires more valuable than avoiding fires? &#8220;For some reason we believe that sweeping in and fixing a problem has more drama, and gains more attention, than doing the work to predict and avoid problems.&#8221; I think the problem is also a blame game. If we acknowledged that there were ways [...]]]></description>
			<content:encoded><![CDATA[<p>Jeffrey Phillips: <a href="http://workingsmarter.typepad.com/my_weblog/2010/02/why-is-fighting-fires-more-valuable-than-avoiding-fires.html?utm_source=twitterfeed&amp;utm_medium=twitter">Why is fighting fires more valuable than avoiding fires?</a></p>
<blockquote><p>&#8220;For some reason we believe that sweeping in and fixing a problem has more drama, and gains more attention, than doing the work to predict and avoid problems.&#8221;</p></blockquote>
<p>I think the problem is also a blame game. If we acknowledged that there were ways we could avoid the fire, then we would implicitly own the problem and more so, be responsible for avoiding the next occurrence. But when the next fire comes, implicitly we&#8217;ve now failed. The goal was to avoid the fire, not react quickly. This requires strategic thinking.</p>
<p>So if we never acknowledge there is a change that could make things better, then when the fire comes, we just block and tackle &#8212; it is happening <em>to us,</em> not <em>caused by us</em>. No one is to blame for the fire, and thus our only measure of success is our reaction speed.</p>
<p>Blocking and tackling is easy. Strategic thinking is hard.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/fighting-fires-instead-of-owning-the-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Decisiveness</title>
		<link>http://www.edstrom.net/blog/archive/decisiveness/</link>
		<comments>http://www.edstrom.net/blog/archive/decisiveness/#comments</comments>
		<pubDate>Sat, 13 Feb 2010 03:35:05 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=987</guid>
		<description><![CDATA[Herding Cats Quote of the Day: If I had to sum up in a word what makes a good manager, I’d say decisiveness. You can use the fanciest computers to gather the numbers, but in the end you have to set a timetable and act. —Lido Anthony (Lee) Iacocca]]></description>
			<content:encoded><![CDATA[<p><a href="http://herdingcats.typepad.com/my_weblog/2009/12/q-5.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+typepad%2FHerdingCats+%28Herding+Cats%29">Herding Cats Quote of the Day</a>:</p>
<blockquote><p><em>If I had to sum up in a word what makes a good manager, I’d say decisiveness. You can use the fanciest computers to gather the numbers, but in the end you have to set a timetable and act.</em></p>
<p>—Lido Anthony (Lee) Iacocca</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/decisiveness/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>We Trust You </title>
		<link>http://www.edstrom.net/blog/archive/we-trust-you/</link>
		<comments>http://www.edstrom.net/blog/archive/we-trust-you/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 13:51:13 +0000</pubDate>
		<dc:creator>Peter Edstrom</dc:creator>
				<category><![CDATA[Main]]></category>
		<category><![CDATA[business culture]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[trust]]></category>

		<guid isPermaLink="false">http://www.edstrom.net/blog/?p=973</guid>
		<description><![CDATA[Matt from SvN on control via trust: A lot of companies seek to control employees. They have handbooks and policies. They monitor emails. They make rules about what’s allowed and what’s forbidden. [...] Imagine an employee handbook that just said: “We trust you. Be mischievous.” This makes a lot of sense to me. If the [...]]]></description>
			<content:encoded><![CDATA[<p>Matt from SvN on <a href="http://37signals.com/svn/posts/2060-control-in-its-wider-sense">control via trust</a>:</p>
<blockquote><p>A lot of companies seek to control employees. They have handbooks and policies. They monitor emails. They make rules about what’s allowed and what’s forbidden. [...]</p>
<p>Imagine an employee handbook that just said: “We trust you. Be mischievous.”</p></blockquote>
<p>This makes a lot of sense to me. If the company trusts you with corporate secrets, company property, and access to production servers &#8230; maybe the policies on appropriate use of YouTube, Twitter, and Facebook are misplaced.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.edstrom.net/blog/archive/we-trust-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

