<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Energized Work | agile in action</title><link>http://www.energizedwork.com/weblog</link><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/AgileInAction" /><description>This is the blog of Simon Baker and Gus Power of Energized Work.</description><language>en</language><copyright>http://creativecommons.org/licenses/by/2.0/</copyright><dc:language xmlns:dc="http://purl.org/dc/elements/1.1/">en</dc:language><dc:rights xmlns:dc="http://purl.org/dc/elements/1.1/">http://creativecommons.org/licenses/by/2.0/</dc:rights><feedburner:info uri="agileinaction" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><creativeCommons:license>http://creativecommons.org/licenses/by/2.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by/2.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site, subject to copyright and fair use.</feedburner:browserFriendly><item><title>System failure is inevitable so design for a fast recovery</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/zJs-ZFmq_nY/system-failure-is-inevitable-so-design-for-a-fast-recovery</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Richardson</dc:creator><pubDate>Wed, 04 Apr 2012 13:22:44 PDT</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[So you're trying to build a reliable website or application. What do you need to think about?<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=zJs-ZFmq_nY:uiveVJVVFJ0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=zJs-ZFmq_nY:uiveVJVVFJ0:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=zJs-ZFmq_nY:uiveVJVVFJ0:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=zJs-ZFmq_nY:uiveVJVVFJ0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=zJs-ZFmq_nY:uiveVJVVFJ0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=zJs-ZFmq_nY:uiveVJVVFJ0:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=zJs-ZFmq_nY:uiveVJVVFJ0:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/zJs-ZFmq_nY" height="1" width="1"/>]]></content:encoded><description>So you're trying to build a reliable website or application. What do you need to think about?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Richardson</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-04-04T20:22:44Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/04/system-failure-is-inevitable-so-design-for-a-fast-recovery</feedburner:origLink></item><item><title>Delight comes as a surprise in unexpected places</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/wO2Ee_cAl1Q/delight-comes-as-a-surprise-in-unexpected-places</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Mon, 26 Mar 2012 16:00:00 PDT</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[The other day at the lab I was going about my 'morning constitutional' in the little boys room when I noticed the end of the toilet paper had been folded into a point. You know, just like in hotel room bathrooms. I realized I had a big smile on my face. This simple act by the office cleaner apparently made me happy. I think the fact it surprised me - I so wasn't expecting it - had an amplifying affect on my delight. If you haven't visited our lab, the last thing you'd expect to see was pointy toilet paper.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=wO2Ee_cAl1Q:dlWZoxHZ_GE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=wO2Ee_cAl1Q:dlWZoxHZ_GE:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=wO2Ee_cAl1Q:dlWZoxHZ_GE:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=wO2Ee_cAl1Q:dlWZoxHZ_GE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=wO2Ee_cAl1Q:dlWZoxHZ_GE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=wO2Ee_cAl1Q:dlWZoxHZ_GE:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=wO2Ee_cAl1Q:dlWZoxHZ_GE:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/wO2Ee_cAl1Q" height="1" width="1"/>]]></content:encoded><description>The other day at the lab I was going about my 'morning constitutional' in the little boys room when I noticed the end of the toilet paper had been folded into a point. You know, just like in hotel room bathrooms. I realized I had a big smile on my face. This simple act by the office cleaner apparently made me happy. I think the fact it surprised me - I so wasn't expecting it - had an amplifying affect on my delight. If you haven't visited our lab, the last thing you'd expect to see was pointy toilet paper.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-03-26T23:00:00Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/03/delight-comes-as-a-surprise-in-unexpected-places</feedburner:origLink></item><item><title>Help create business agility. Bake quality in</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/StliHli8K-s/help-create-business-agility-bake-quality-in</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Sat, 24 Mar 2012 17:00:00 PDT</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Something common I&rsquo;ve seen in effective agile teams is that testing has found a new home at the heart of development. I&rsquo;m not referring to developers doing test-driven development to create code that is simpler in design and has testability engineered into it. I&rsquo;m referring to testers working among developers doing continuous exploratory testing on vertical slices of stories still in progress. </p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=StliHli8K-s:Dw3pb7OyFvM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=StliHli8K-s:Dw3pb7OyFvM:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=StliHli8K-s:Dw3pb7OyFvM:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=StliHli8K-s:Dw3pb7OyFvM:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=StliHli8K-s:Dw3pb7OyFvM:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=StliHli8K-s:Dw3pb7OyFvM:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=StliHli8K-s:Dw3pb7OyFvM:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/StliHli8K-s" height="1" width="1"/>]]></content:encoded><description>Something common I've seen in effective agile teams is that testing has found a new home at the heart of development. I'm not referring to developers doing test-driven development to create code that is simpler in design and has testability engineered into it. I'm referring to testers working among developers doing continuous exploratory testing on vertical slices of stories still in progress.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-03-25T00:00:00Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/03/help-create-business-agility-bake-quality-in</feedburner:origLink></item><item><title>Governance - Friend or Foe?</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/iDLzhWoI4Hw/governance-friend-or-foe-</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Thu, 22 Mar 2012 16:17:44 PDT</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>We&rsquo;re designing a session about governance in an agile world that will explore a contrarian view of what agile governance can be. It&rsquo;s called: Governance – Friend or Foe? Basically&hellip;</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=iDLzhWoI4Hw:WuMzYHohkdE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=iDLzhWoI4Hw:WuMzYHohkdE:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=iDLzhWoI4Hw:WuMzYHohkdE:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=iDLzhWoI4Hw:WuMzYHohkdE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=iDLzhWoI4Hw:WuMzYHohkdE:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=iDLzhWoI4Hw:WuMzYHohkdE:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=iDLzhWoI4Hw:WuMzYHohkdE:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/iDLzhWoI4Hw" height="1" width="1"/>]]></content:encoded><description>We're designing a session about governance in an agile world that will explore a contrarian view of what agile governance can be. It's called: Governance – Friend or Foe? Basically...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-03-22T23:17:44Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/03/governance-friend-or-foe-</feedburner:origLink></item><item><title>70% Forum</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/Jitj4JLlz40/70-forum</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Fri, 02 Mar 2012 05:34:15 PST</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[Last night we hosted a talk by Kris and Suki at the Energized Work lab. The talk was called 230 Iteration Later and it was a dry run for the QCon conference in London this month.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=Jitj4JLlz40:_vEpCU4IPU4:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=Jitj4JLlz40:_vEpCU4IPU4:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=Jitj4JLlz40:_vEpCU4IPU4:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=Jitj4JLlz40:_vEpCU4IPU4:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=Jitj4JLlz40:_vEpCU4IPU4:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=Jitj4JLlz40:_vEpCU4IPU4:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=Jitj4JLlz40:_vEpCU4IPU4:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/Jitj4JLlz40" height="1" width="1"/>]]></content:encoded><description>Last night we hosted a talk by Kris and Suki at the Energized Work lab. The talk was called 230 Iteration Later and it was a dry run for the QCon conference in London this month.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-03-02T13:34:15Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/03/70-forum</feedburner:origLink></item><item><title>Measuring purpose. Measuring customer delight</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/ImaEKHSel1E/measuring-purpose-measuring-customer-delight</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Sat, 25 Feb 2012 16:00:00 PST</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[Power is shifting in the marketplace from the seller to the buyer. The rules of business are changing. Increasingly, customers know everything about the companies they buy from. Customers are taking charge and the new business bottom line is customer delight. It's no longer about pushing features at customers, it's about achieving the experiences customers desire. It's no longer about concept to cash, it's about how long it takes to go from concept to customer delight. It's no longer about output, it's about outcomes. Delighting customers is everyone's responsibility and whether you realize it or not, no matter what you do, you're working in customer services.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ImaEKHSel1E:7IJSHApIEdQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ImaEKHSel1E:7IJSHApIEdQ:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ImaEKHSel1E:7IJSHApIEdQ:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ImaEKHSel1E:7IJSHApIEdQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=ImaEKHSel1E:7IJSHApIEdQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ImaEKHSel1E:7IJSHApIEdQ:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=ImaEKHSel1E:7IJSHApIEdQ:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/ImaEKHSel1E" height="1" width="1"/>]]></content:encoded><description>Power is shifting in the marketplace from the seller to the buyer. The rules of business are changing. Increasingly, customers know everything about the companies they buy from. Customers are taking charge and the new business bottom line is customer delight. It's no longer about pushing features at customers, it's about achieving the experiences customers desire. It's no longer about concept to cash, it's about how long it takes to go from concept to customer delight. It's no longer about output, it's about outcomes. Delighting customers is everyone's responsibility and whether you realize it or not, no matter what you do, you're working in customer services.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-02-26T00:00:00Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/02/measuring-purpose-measuring-customer-delight</feedburner:origLink></item><item><title>Stop pushing features and start delighting users</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/ScAXBrJkFKU/stop-pushing-features-and-start-delighting-users</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Fri, 24 Feb 2012 14:54:57 PST</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[Focus on outcomes not output. Stop pushing features and start delighting users.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ScAXBrJkFKU:M1VeQJ8fxpg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ScAXBrJkFKU:M1VeQJ8fxpg:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ScAXBrJkFKU:M1VeQJ8fxpg:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ScAXBrJkFKU:M1VeQJ8fxpg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=ScAXBrJkFKU:M1VeQJ8fxpg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=ScAXBrJkFKU:M1VeQJ8fxpg:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=ScAXBrJkFKU:M1VeQJ8fxpg:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/ScAXBrJkFKU" height="1" width="1"/>]]></content:encoded><description>Focus on outcomes not output. Stop pushing features and start delighting users.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-02-24T22:54:57Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/02/stop-pushing-features-and-start-delighting-users</feedburner:origLink></item><item><title>Lost without a goal</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/6PKfSQHQ-eg/lost-without-a-goal</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Sat, 18 Feb 2012 16:00:00 PST</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[I can't operate effectively without some kind of goal. Let me clarify that. Without some kind of goal I am directionless. I'm easily distracted from any focus I might have started with by other things that crop up. I end up flitting from one thing to another, multitasking. I become anxious and frustrated. I lose my sense of priority. I end up working on things that don't add value and I create lots of work-in-progress. It only gets worse the longer I go without being able to check in against some goal. I suspect most people are like this.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=6PKfSQHQ-eg:wv293H-s_Jo:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=6PKfSQHQ-eg:wv293H-s_Jo:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=6PKfSQHQ-eg:wv293H-s_Jo:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=6PKfSQHQ-eg:wv293H-s_Jo:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=6PKfSQHQ-eg:wv293H-s_Jo:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=6PKfSQHQ-eg:wv293H-s_Jo:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=6PKfSQHQ-eg:wv293H-s_Jo:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/6PKfSQHQ-eg" height="1" width="1"/>]]></content:encoded><description>I can't operate effectively without some kind of goal. Let me clarify that. Without some kind of goal I am directionless. I'm easily distracted from any focus I might have started with by other things that crop up. I end up flitting from one thing to another, multitasking. I become anxious and frustrated. I lose my sense of priority. I end up working on things that don't add value and I create lots of work-in-progress. It only gets worse the longer I go without being able to check in against some goal. I suspect most people are like this.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-02-19T00:00:00Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/02/lost-without-a-goal</feedburner:origLink></item><item><title>Emotion creates the common language</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/tiImQ_Vih7Q/emotion-creates-the-common-language</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Fri, 17 Feb 2012 16:00:00 PST</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[The challenge when dealing with people from different backgrounds, with different experiences, qualifications, roles and domain knowledge is speaking the same language. When we face together a problem or opportunity, or given a certain need, we talk about what and how - what is the solution? How will we meet this need? We each think we see the same thing. We each believe we are talking about the same thing. When we talk about what it is it's often a case of the five blind guys and the elephant. Together we work hard to overcome our individual perspectives and structure a common language we think describes the what and the how.<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=tiImQ_Vih7Q:EtqP1Pi_mQI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=tiImQ_Vih7Q:EtqP1Pi_mQI:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=tiImQ_Vih7Q:EtqP1Pi_mQI:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=tiImQ_Vih7Q:EtqP1Pi_mQI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=tiImQ_Vih7Q:EtqP1Pi_mQI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=tiImQ_Vih7Q:EtqP1Pi_mQI:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=tiImQ_Vih7Q:EtqP1Pi_mQI:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/tiImQ_Vih7Q" height="1" width="1"/>]]></content:encoded><description>The challenge when dealing with people from different backgrounds, with different experiences, qualifications, roles and domain knowledge is speaking the same language. When we face together a problem or opportunity, or given a certain need, we talk about what and how - what is the solution? How will we meet this need? We each think we see the same thing. We each believe we are talking about the same thing. When we talk about what it is it's often a case of the five blind guys and the elephant. Together we work hard to overcome our individual perspectives and structure a common language we think describes the what and the how.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-02-18T00:00:00Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/02/emotion-creates-the-common-language</feedburner:origLink></item><item><title>Five sneaky ways to kill an initiative</title><link>http://feedproxy.google.com/~r/AgileInAction/~3/7tqStNxjcKQ/five-sneaky-ways-to-kill-an-initiative</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><pubDate>Sun, 12 Feb 2012 07:02:15 PST</pubDate><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h4>1. Declare victory</h4><p>Regardless of whether something has been successful or not the quickest way to kill it is to publicly declare it a success: &ldquo;The initiative has been completely successful. The team responsible is no longer needed. The values have been internalized.&rdquo; </p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/AgileInAction?a=7tqStNxjcKQ:pgI66Aupz00:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=7tqStNxjcKQ:pgI66Aupz00:dnMXMwOfBR0"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=dnMXMwOfBR0" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=7tqStNxjcKQ:pgI66Aupz00:7Q72WNTAKBA"><img src="http://feeds.feedburner.com/~ff/AgileInAction?d=7Q72WNTAKBA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=7tqStNxjcKQ:pgI66Aupz00:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=7tqStNxjcKQ:pgI66Aupz00:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/AgileInAction?a=7tqStNxjcKQ:pgI66Aupz00:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/AgileInAction?i=7tqStNxjcKQ:pgI66Aupz00:gIN9vFwOqvQ" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AgileInAction/~4/7tqStNxjcKQ" height="1" width="1"/>]]></content:encoded><description>1. Declare victory Regardless of whether something has been successful or not the quickest way to kill it is to publicly declare it a success: "The initiative has been completely successful. The team responsible is no longer needed. The values have been internalized."</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Baker</dc:creator><dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2012-02-12T15:02:15Z</dc:date><feedburner:origLink>http://www.energizedwork.com/weblog/2012/02/five-sneaky-ways-to-kill-an-initiative</feedburner:origLink></item></channel></rss>

