<?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: Designing for Change: “Be Water My Friend”</title>
	<atom:link href="http://johnnyholland.org/2011/09/designing-for-change-be-water-my-friend/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnyholland.org/2011/09/designing-for-change-be-water-my-friend/</link>
	<description>It&#039;s all about interaction</description>
	<lastBuildDate>Wed, 05 Jun 2013 06:03:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: From Heartache to Mastery: 5 Lessons for the UX Designer Seeking Agency Experience - UX Booth &#124; UX Booth</title>
		<link>http://johnnyholland.org/2011/09/designing-for-change-be-water-my-friend/#comment-119546</link>
		<dc:creator>From Heartache to Mastery: 5 Lessons for the UX Designer Seeking Agency Experience - UX Booth &#124; UX Booth</dc:creator>
		<pubDate>Tue, 13 Nov 2012 14:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=11628#comment-119546</guid>
		<description>[...] will turn into a realisation that there is no perfect process. Instead, learn to compromise and react just as much as plan. Become [...]</description>
		<content:encoded><![CDATA[<p>[...] will turn into a realisation that there is no perfect process. Instead, learn to compromise and react just as much as plan. Become [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Leech &#187; Blog Archive &#187; Great Outdoors of Design Conference 2011</title>
		<link>http://johnnyholland.org/2011/09/designing-for-change-be-water-my-friend/#comment-117349</link>
		<dc:creator>Joe Leech &#187; Blog Archive &#187; Great Outdoors of Design Conference 2011</dc:creator>
		<pubDate>Wed, 28 Sep 2011 13:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=11628#comment-117349</guid>
		<description>[...] nicely summed up in the phrase &#8220;Be water my friend&#8221; from Bruce [...]</description>
		<content:encoded><![CDATA[<p>[...] nicely summed up in the phrase &#8220;Be water my friend&#8221; from Bruce [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Cain</title>
		<link>http://johnnyholland.org/2011/09/designing-for-change-be-water-my-friend/#comment-117348</link>
		<dc:creator>David Cain</dc:creator>
		<pubDate>Thu, 15 Sep 2011 16:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=11628#comment-117348</guid>
		<description>Excellent points all.

I&#039;ll add that in large organizations, there&#039;s a lot to be said for picking your projects carefully.

Showing a little success means you may be in high demand quickly. When that happens, you must avoid the temptation to spread yourself thin. It&#039;s then time to pivot, help a business spread design-thinking to additional facilitators and designers inside, help stakeholders realize they&#039;ll need to augment with help from outside, or perhaps just triage and prioritize the many things that need fixing.

Hardest thing for me: behemoth projects that need everything fixed, likely riding on the back of broken business process. There&#039;s never enough money, enough time, and there are so many stakeholders with competing interests that things never seem to move.

Some things are just too big to fix, resistant to guerilla tactics. If you can&#039;t swallow these one bite at a time, you should probably extricate yourself and find a project with a better risk/reward profile for you AND your company.</description>
		<content:encoded><![CDATA[<p>Excellent points all.</p>
<p>I&#8217;ll add that in large organizations, there&#8217;s a lot to be said for picking your projects carefully.</p>
<p>Showing a little success means you may be in high demand quickly. When that happens, you must avoid the temptation to spread yourself thin. It&#8217;s then time to pivot, help a business spread design-thinking to additional facilitators and designers inside, help stakeholders realize they&#8217;ll need to augment with help from outside, or perhaps just triage and prioritize the many things that need fixing.</p>
<p>Hardest thing for me: behemoth projects that need everything fixed, likely riding on the back of broken business process. There&#8217;s never enough money, enough time, and there are so many stakeholders with competing interests that things never seem to move.</p>
<p>Some things are just too big to fix, resistant to guerilla tactics. If you can&#8217;t swallow these one bite at a time, you should probably extricate yourself and find a project with a better risk/reward profile for you AND your company.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
