<?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: HBR Finally Runs Their Design Thinking Article</title>
	<atom:link href="http://noisebetweenstations.com/personal/weblogs/?feed=rss2&#038;p=2201" rel="self" type="application/rss+xml" />
	<link>http://noisebetweenstations.com/personal/weblogs/?p=2201</link>
	<description>Business, Design, and the Internet. Since 1999.</description>
	<pubDate>Wed, 08 Sep 2010 03:11:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: smartbrains</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651589</link>
		<dc:creator>smartbrains</dc:creator>
		<pubDate>Sat, 10 Jul 2010 07:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651589</guid>
		<description>According to me, 
What the article is missing is some concrete examples
Agreed. In his defense, it’s just an introductory article. I suspect it’s both very hard and very easy to show examples. Very hard because applying creativity to what are normally analytical activities is a design problem in itself. I’ve found that inventing even rudimentary tools is hard…
&lt;a href="//oldfashiongirl.com”" rel="nofollow"&gt;
Fashion Girl &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>According to me,<br />
What the article is missing is some concrete examples<br />
Agreed. In his defense, it’s just an introductory article. I suspect it’s both very hard and very easy to show examples. Very hard because applying creativity to what are normally analytical activities is a design problem in itself. I’ve found that inventing even rudimentary tools is hard…<br />
<a href="//oldfashiongirl.com”" rel="nofollow"><br />
Fashion Girl </a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: businessmodel innovation _ design &#187; Design Thinking and Five Challenges of Design-led Organizations</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651387</link>
		<dc:creator>businessmodel innovation _ design &#187; Design Thinking and Five Challenges of Design-led Organizations</dc:creator>
		<pubDate>Wed, 01 Oct 2008 09:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651387</guid>
		<description>[...] got the german language paper version only, but Victor and others have written extensively about it.   tagged with  creativity, design, design-thinking, [...]</description>
		<content:encoded><![CDATA[<p>[...] got the german language paper version only, but Victor and others have written extensively about it.   tagged with  creativity, design, design-thinking, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Design Thinking to Finance Skyscapers at Noise Between Stations</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651147</link>
		<dc:creator>Design Thinking to Finance Skyscapers at Noise Between Stations</dc:creator>
		<pubDate>Tue, 03 Jun 2008 14:59:13 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651147</guid>
		<description>[...] her comment to my post on the recent HBR article on design thinking, my friend HK writes, &#8220;What the article is [...]</description>
		<content:encoded><![CDATA[<p>[...] her comment to my post on the recent HBR article on design thinking, my friend HK writes, &#8220;What the article is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651146</link>
		<dc:creator>Victor</dc:creator>
		<pubDate>Tue, 03 Jun 2008 14:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651146</guid>
		<description>RE&#62;What the article is missing is some concrete examples

Agreed. In his defense, it's just an introductory article. I suspect it's both very hard and very easy to show examples. Very hard because applying creativity to what are normally analytical activities is a design problem in itself. I've found that inventing even rudimentary tools is hard...
http://noisebetweenstations.com/personal/weblogs/?p=2192

But it's also easy, there are examples all around us. Financing a very expensive project, like a skyscraper, happens frequently enough. This requires creativity to solve a problem involving several parties, credit instruments, commitments over time, taxes, and so on. 

I'd like to know if anyone in finance is studying these deals as creative activities to help us understand how to design them better.</description>
		<content:encoded><![CDATA[<p>RE&gt;What the article is missing is some concrete examples</p>
<p>Agreed. In his defense, it&#8217;s just an introductory article. I suspect it&#8217;s both very hard and very easy to show examples. Very hard because applying creativity to what are normally analytical activities is a design problem in itself. I&#8217;ve found that inventing even rudimentary tools is hard&#8230;<br />
<a href="http://noisebetweenstations.com/personal/weblogs/?p=2192" rel="nofollow">http://noisebetweenstations.com/personal/weblogs/?p=2192</a></p>
<p>But it&#8217;s also easy, there are examples all around us. Financing a very expensive project, like a skyscraper, happens frequently enough. This requires creativity to solve a problem involving several parties, credit instruments, commitments over time, taxes, and so on. </p>
<p>I&#8217;d like to know if anyone in finance is studying these deals as creative activities to help us understand how to design them better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hk dunston</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651143</link>
		<dc:creator>hk dunston</dc:creator>
		<pubDate>Mon, 02 Jun 2008 16:04:49 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651143</guid>
		<description>What the article is missing is some concrete examples – what do designers *do* at strategic phases of projects, when the problems they’re solving aren’t explicit design problems? Why is it important for designers to participate in the process at that point? What would they do differently from a typical business strategist? 

Designers bring a few things to the table at strategic points in the process but the primary tasks are:

1.	Asking different questions that result in a fuller understanding of the problem. Any good strategy process is going to involve research. Including designers (or design thinking) in the research process ensures that the strategy you’re developing includes a more human-centric focus. Imagine a fairly unsexy business problem: working on a strategy for a wholesaler who needs to make their warehouse processes more effective. After understanding the lay of the land, traditional consultants are likely to first figure out where the leverage points are – where are the points at which improvement will make the biggest impact? Where are there process imbalances? What’s the cost structure? A designer is more likely to spend time in the warehouse, shadowing workers to understand how they do their work, the tools they use and the kinds of workarounds and inventions they have developed to make their life easier. Both of these perspectives are vital – business strategists are looking at the landscape from the top down, where designers are more likely to look at the world from the bottom up, from the perspective of  the people doing the work. A good strategy needs to take into account both perspectives. 
2.	Making the strategy real. As the article describes, the design process revolves around the prototyping process, developing an idea by designing potential solutions in a way that’s tangible, that allows everyone in the room to develop a shared understanding of the direction. Applying design thinking in a business context allows the strategy team to come to a very clear, succinct understanding of the possibilities for the world their strategy will create. It also provides an easy way to test ideas with stakeholders. If our strategy is to re-vamp our warehouse to enable significantly faster through-put, here are two potential ways we could make that happen. Option 1 looks like this: [insert visualization of that new world, via sketches, stories, process flows or all of the above]; Option 2 looks like this: [ditto]. Because the options are real and tangible, it’s easier for stakeholders to respond, to come up with their own ideas, or to point out the disconnects in their understanding of the strategy. A few iterations of this kind of visualization results in a strategy that’s been road tested and is significantly more likely to avoid the kinds of executional risks inherent in any strategy. 
3.	Ensuring a smoother transition to the tactical design process. In order to create a more efficient warehouse, we may decide that we need to redesign the physical plant; we may decide that what we need is a revised recruiting process, we may decide that we need to recategorize the items on the shelves to link items that tend to be purchased together; maybe we need all of the above. In any of these cases, the execution phase requires design. The translation process from the strategy to the design entails significant risk. How do you communicate the context, goals and requirements of the task to a wide variety of different vendors, each of whom has their own methods and their own interpretation of the plan. Instilling design into the process ensures significantly smoother translation of strategy into each aspect of the execution.</description>
		<content:encoded><![CDATA[<p>What the article is missing is some concrete examples – what do designers *do* at strategic phases of projects, when the problems they’re solving aren’t explicit design problems? Why is it important for designers to participate in the process at that point? What would they do differently from a typical business strategist? </p>
<p>Designers bring a few things to the table at strategic points in the process but the primary tasks are:</p>
<p>1.	Asking different questions that result in a fuller understanding of the problem. Any good strategy process is going to involve research. Including designers (or design thinking) in the research process ensures that the strategy you’re developing includes a more human-centric focus. Imagine a fairly unsexy business problem: working on a strategy for a wholesaler who needs to make their warehouse processes more effective. After understanding the lay of the land, traditional consultants are likely to first figure out where the leverage points are – where are the points at which improvement will make the biggest impact? Where are there process imbalances? What’s the cost structure? A designer is more likely to spend time in the warehouse, shadowing workers to understand how they do their work, the tools they use and the kinds of workarounds and inventions they have developed to make their life easier. Both of these perspectives are vital – business strategists are looking at the landscape from the top down, where designers are more likely to look at the world from the bottom up, from the perspective of  the people doing the work. A good strategy needs to take into account both perspectives.<br />
2.	Making the strategy real. As the article describes, the design process revolves around the prototyping process, developing an idea by designing potential solutions in a way that’s tangible, that allows everyone in the room to develop a shared understanding of the direction. Applying design thinking in a business context allows the strategy team to come to a very clear, succinct understanding of the possibilities for the world their strategy will create. It also provides an easy way to test ideas with stakeholders. If our strategy is to re-vamp our warehouse to enable significantly faster through-put, here are two potential ways we could make that happen. Option 1 looks like this: [insert visualization of that new world, via sketches, stories, process flows or all of the above]; Option 2 looks like this: [ditto]. Because the options are real and tangible, it’s easier for stakeholders to respond, to come up with their own ideas, or to point out the disconnects in their understanding of the strategy. A few iterations of this kind of visualization results in a strategy that’s been road tested and is significantly more likely to avoid the kinds of executional risks inherent in any strategy.<br />
3.	Ensuring a smoother transition to the tactical design process. In order to create a more efficient warehouse, we may decide that we need to redesign the physical plant; we may decide that what we need is a revised recruiting process, we may decide that we need to recategorize the items on the shelves to link items that tend to be purchased together; maybe we need all of the above. In any of these cases, the execution phase requires design. The translation process from the strategy to the design entails significant risk. How do you communicate the context, goals and requirements of the task to a wide variety of different vendors, each of whom has their own methods and their own interpretation of the plan. Instilling design into the process ensures significantly smoother translation of strategy into each aspect of the execution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Putting People First in italiano &#187; Tim Brown di IDEO sul design thinking su HBR</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651128</link>
		<dc:creator>Putting People First in italiano &#187; Tim Brown di IDEO sul design thinking su HBR</dc:creator>
		<pubDate>Fri, 30 May 2008 15:25:49 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651128</guid>
		<description>[...] Noise between Stations)           &#160;    Scrivi un [...]</description>
		<content:encoded><![CDATA[<p>[...] Noise between Stations)           &nbsp;    Scrivi un [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harvard Business Review on design thinking &#171; L.Galli</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651124</link>
		<dc:creator>Harvard Business Review on design thinking &#171; L.Galli</dc:creator>
		<pubDate>Thu, 29 May 2008 13:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651124</guid>
		<description>[...] thinking from Ideo&#8217;s Tim Brown (nb: complete version available online, no subscribtion). The post from Victor Lombardi includes a nice, compact [...]</description>
		<content:encoded><![CDATA[<p>[...] thinking from Ideo&#8217;s Tim Brown (nb: complete version available online, no subscribtion). The post from Victor Lombardi includes a nice, compact [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Putting people first &#187; IDEO&#8217;s Tim Brown on design thinking in HBR</title>
		<link>http://noisebetweenstations.com/personal/weblogs/?p=2201&cpage=1#comment-651123</link>
		<dc:creator>Putting people first &#187; IDEO&#8217;s Tim Brown on design thinking in HBR</dc:creator>
		<pubDate>Thu, 29 May 2008 08:00:19 +0000</pubDate>
		<guid isPermaLink="false">http://noisebetweenstations.com/personal/weblogs/?p=2201#comment-651123</guid>
		<description>[...] Noise between Stations)           &#160;    Leave a [...]</description>
		<content:encoded><![CDATA[<p>[...] Noise between Stations)           &nbsp;    Leave a [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
