<?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 for Semantic Foundry</title>
	<atom:link href="http://blog.semanticfoundry.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.semanticfoundry.com</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Thu, 01 Dec 2011 10:04:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on 4 Essential Non-UX Books for UX &amp; Product Designers by Daniel Kahneman: Beware the ‘inside view’ &#124; Semantic Foundry</title>
		<link>http://blog.semanticfoundry.com/2011/11/28/4-essential-non-ux-books-for-ux-product-designers/#comment-83</link>
		<dc:creator>Daniel Kahneman: Beware the ‘inside view’ &#124; Semantic Foundry</dc:creator>
		<pubDate>Thu, 01 Dec 2011 10:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1861#comment-83</guid>
		<description>[...] find it funny that just Monday I wrote a blog post called, &#8220;4 Non-UX Books for UX &amp; Product Designers,&#8221; which included Daniel Kahneman&#8217;s &#8220;Thinking, Fast and Slow,&#8221; and just [...]</description>
		<content:encoded><![CDATA[<p>[...] find it funny that just Monday I wrote a blog post called, &#8220;4 Non-UX Books for UX &amp; Product Designers,&#8221; which included Daniel Kahneman&#8217;s &#8220;Thinking, Fast and Slow,&#8221; and just [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introduction to Design Studio Methodology by Inspire Phase &#8211; Part 1 of 4 &#171; chrisdblog</title>
		<link>http://blog.semanticfoundry.com/2011/04/30/introduction-to-design-studio-methodology/#comment-24</link>
		<dc:creator>Inspire Phase &#8211; Part 1 of 4 &#171; chrisdblog</dc:creator>
		<pubDate>Mon, 05 Sep 2011 20:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1389#comment-24</guid>
		<description>[...] We see a real focus today on ‘understanding the customer’. Its the tenet of many of the hip trends in business schools – see Lean Startups, the Business Model Canvas etc. In software development we see many different paradigms and strategies for understanding the customer problems from DDD, BDD, and even TDD where we are attempting to bring developers and business people together with a shared language and understanding. We also see this focus in front-end word such as with Lean UX and recently I’ve been reading about Design Studio. [...] </description>
		<content:encoded><![CDATA[<p>[...] We see a real focus today on ‘understanding the customer’. Its the tenet of many of the hip trends in business schools – see Lean Startups, the Business Model Canvas etc. In software development we see many different paradigms and strategies for understanding the customer problems from DDD, BDD, and even TDD where we are attempting to bring developers and business people together with a shared language and understanding. We also see this focus in front-end word such as with Lean UX and recently I’ve been reading about Design Studio. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Shades of Gray: Wireframes as Thinking Device by Twitted by usabilitycounts</title>
		<link>http://blog.semanticfoundry.com/2009/01/01/shades-of-gray-wireframes-as-thinking-device/#comment-4</link>
		<dc:creator>Twitted by usabilitycounts</dc:creator>
		<pubDate>Tue, 30 Aug 2011 21:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=152#comment-4</guid>
		<description>[...] This post was Twitted by usabilitycounts [...] </description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by usabilitycounts [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The UX Canon: Essential Reading for the User Experience Designer by The Core UX Reading List - Man with no Blog</title>
		<link>http://blog.semanticfoundry.com/2010/08/25/the-ux-canon-essential-reading-for-the-user-experience-designer/#comment-9</link>
		<dc:creator>The Core UX Reading List - Man with no Blog</dc:creator>
		<pubDate>Tue, 02 Aug 2011 14:14:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=932#comment-9</guid>
		<description>[...] having a list of starter books would be handy. Yeah sure others have their lists like Will Evans, Paul Seys and Nick Finck however some of the books on these are either too complex or take way [...] </description>
		<content:encoded><![CDATA[<p>[...] having a list of starter books would be handy. Yeah sure others have their lists like Will Evans, Paul Seys and Nick Finck however some of the books on these are either too complex or take way [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introduction to Design Studio Methodology by The UX of User Stories, Part 2 - Anders Ramsay.com</title>
		<link>http://blog.semanticfoundry.com/2011/04/30/introduction-to-design-studio-methodology/#comment-23</link>
		<dc:creator>The UX of User Stories, Part 2 - Anders Ramsay.com</dc:creator>
		<pubDate>Sun, 24 Jul 2011 17:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1389#comment-23</guid>
		<description>[...] then quickly transition to a visual exploration, such as a design studio. (Will Evans recently did a great write-up on on that.) The visual exploration will also help you improve your story [...] </description>
		<content:encoded><![CDATA[<p>[...] then quickly transition to a visual exploration, such as a design studio. (Will Evans recently did a great write-up on on that.) The visual exploration will also help you improve your story [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Design Studio for AgileUX by Chris Dunne</title>
		<link>http://blog.semanticfoundry.com/2011/07/20/design-studio-for-agileux/#comment-53</link>
		<dc:creator>Chris Dunne</dc:creator>
		<pubDate>Fri, 22 Jul 2011 13:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1700#comment-53</guid>
		<description>Excellent series of articles on Design Studio. I am wondering if you have ever applied this outside of the realm of digital media and UX design. For example have you ever applied it to problems involving the redesign of a service or business process? Do you think it is applicable in this area?</description>
		<content:encoded><![CDATA[<p>Excellent series of articles on Design Studio. I am wondering if you have ever applied this outside of the realm of digital media and UX design. For example have you ever applied it to problems involving the redesign of a service or business process? Do you think it is applicable in this area?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Design Studio for AgileUX by Anders Ramsay</title>
		<link>http://blog.semanticfoundry.com/2011/07/20/design-studio-for-agileux/#comment-52</link>
		<dc:creator>Anders Ramsay</dc:creator>
		<pubDate>Thu, 21 Jul 2011 13:18:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1700#comment-52</guid>
		<description>Will and Jeff - great post on the art and science of design studio!

Since starting to make design studios part of my practice some years back, I had to wonder how my practice had been able to function without it up until that point. What I realized was that I--as many traditional designers--had been expending tons and tons of my own energy to try to come up with design solutions and present them to passive team members, when I in fact was surrounded by an incredible source of creative power, in the form of that very same team.  IMO, any UX&#039;er today who isn&#039;t incorporating design studio is really losing out.

That said, it is just as important to point out that the design studio described in this post is only _one_ of many variations on this technique.  In my practice, I use three variations of design studio.

The first is what I call the &quot;Ideation Clearinghouse&quot; model. In contrast to the above design studio, which is convergent (i.e. the goal is to narrow your exploration to a small number of good ideas), this is a divergent form of design, in which I want to uncover the range of ideas that the project stakeholders have about the product.  

This is perfect for doing with business sponsors at the project outset, to capture the product they are seeing in their minds, such that when the team then goes to work to design the real product, they can do so with an awareness of that.  Knowing what execs and others who fund the project are imagining the end product to look like is worth nothing less than gold when presenting your own ideas to them.  (If not, you may present something that is strong, but because it was not what they expected, you&#039;ll get a thumbs down.)

Then there is the convergent model which you describe and is super-powerful as an activity for the team itself.

Then there is what I call an ad-hoc design studio.  This is great for when the team is in the throes of the sprint and some unexpected issue comes up.  At that point, a few team members grab some sheets of paper and markers, agree on what the issue is (e.g. something developers thought would be easy to build has turned out to be much harder, so they&#039;ve proposed a different technical solution which in turn will require a very different UI), and do a 5-minute or maybe even 3-minute sketching timebox (sketchbox?), followed by discussion of the ideas proposed.  I&#039;ve done sessions like this in under 15 minutes - which brings me to my last point.

From your description of design studios, someone with no experience with them, would get the sense that you need hours and hours to be able complete them. This is simply not true.  Yes, for certain models and certain situations, 3-4 hours or more can be time very well spent.  

But a design studio can also be much more *lean* than that, i.e. you can also do them in an hour or less, and I think that should be front and center when describing this powerful technique to anyone who is new to it.</description>
		<content:encoded><![CDATA[<p>Will and Jeff &#8211; great post on the art and science of design studio!</p>
<p>Since starting to make design studios part of my practice some years back, I had to wonder how my practice had been able to function without it up until that point. What I realized was that I&#8211;as many traditional designers&#8211;had been expending tons and tons of my own energy to try to come up with design solutions and present them to passive team members, when I in fact was surrounded by an incredible source of creative power, in the form of that very same team.  IMO, any UX&#8217;er today who isn&#8217;t incorporating design studio is really losing out.</p>
<p>That said, it is just as important to point out that the design studio described in this post is only _one_ of many variations on this technique.  In my practice, I use three variations of design studio.</p>
<p>The first is what I call the &#8220;Ideation Clearinghouse&#8221; model. In contrast to the above design studio, which is convergent (i.e. the goal is to narrow your exploration to a small number of good ideas), this is a divergent form of design, in which I want to uncover the range of ideas that the project stakeholders have about the product.  </p>
<p>This is perfect for doing with business sponsors at the project outset, to capture the product they are seeing in their minds, such that when the team then goes to work to design the real product, they can do so with an awareness of that.  Knowing what execs and others who fund the project are imagining the end product to look like is worth nothing less than gold when presenting your own ideas to them.  (If not, you may present something that is strong, but because it was not what they expected, you&#8217;ll get a thumbs down.)</p>
<p>Then there is the convergent model which you describe and is super-powerful as an activity for the team itself.</p>
<p>Then there is what I call an ad-hoc design studio.  This is great for when the team is in the throes of the sprint and some unexpected issue comes up.  At that point, a few team members grab some sheets of paper and markers, agree on what the issue is (e.g. something developers thought would be easy to build has turned out to be much harder, so they&#8217;ve proposed a different technical solution which in turn will require a very different UI), and do a 5-minute or maybe even 3-minute sketching timebox (sketchbox?), followed by discussion of the ideas proposed.  I&#8217;ve done sessions like this in under 15 minutes &#8211; which brings me to my last point.</p>
<p>From your description of design studios, someone with no experience with them, would get the sense that you need hours and hours to be able complete them. This is simply not true.  Yes, for certain models and certain situations, 3-4 hours or more can be time very well spent.  </p>
<p>But a design studio can also be much more *lean* than that, i.e. you can also do them in an hour or less, and I think that should be front and center when describing this powerful technique to anyone who is new to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Design of Design Studio by Kinesthetic Ideation for UX &#38; Service Design &#124; Semantic Foundry</title>
		<link>http://blog.semanticfoundry.com/2011/07/10/the-design-of-design-studio/#comment-41</link>
		<dc:creator>Kinesthetic Ideation for UX &#38; Service Design &#124; Semantic Foundry</dc:creator>
		<pubDate>Wed, 13 Jul 2011 21:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1601#comment-41</guid>
		<description>[...] at a major international banking conglomerate. Although we could have just as easily used “Design Studio,” to imagine the various touch points of the consumer experience – Lego’s [...] </description>
		<content:encoded><![CDATA[<p>[...] at a major international banking conglomerate. Although we could have just as easily used “Design Studio,” to imagine the various touch points of the consumer experience – Lego’s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Design of Design Studio by Daniela</title>
		<link>http://blog.semanticfoundry.com/2011/07/10/the-design-of-design-studio/#comment-39</link>
		<dc:creator>Daniela</dc:creator>
		<pubDate>Sun, 10 Jul 2011 23:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1601#comment-39</guid>
		<description>Love this Will.. thanks for including so much practical detail on running a Design Studio. I used a modified version of Design Studio in a UXD Fundamentals course we ran in-house early this year. (I&#039;d previously been to Todd&#039;s workshop). I was frankly astonished at the quality of the paper prototypes participants produced and the depth &amp; breadth of ideas generated in such a short space of time. This is a great design method &amp; one I&#039;d like to use more often.</description>
		<content:encoded><![CDATA[<p>Love this Will.. thanks for including so much practical detail on running a Design Studio. I used a modified version of Design Studio in a UXD Fundamentals course we ran in-house early this year. (I&#8217;d previously been to Todd&#8217;s workshop). I was frankly astonished at the quality of the paper prototypes participants produced and the depth &amp; breadth of ideas generated in such a short space of time. This is a great design method &amp; one I&#8217;d like to use more often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Design of Design Studio by Virginia</title>
		<link>http://blog.semanticfoundry.com/2011/07/10/the-design-of-design-studio/#comment-38</link>
		<dc:creator>Virginia</dc:creator>
		<pubDate>Sun, 10 Jul 2011 21:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.semanticfoundry.com/?p=1601#comment-38</guid>
		<description>Thanks Will! Love Johansson&#039;s Medici Effect. I&#039;m curious, when you are using this during the Agile process. Iteration 0? Or is this for fleshing out ideas like you discussed in the post mortem.</description>
		<content:encoded><![CDATA[<p>Thanks Will! Love Johansson&#8217;s Medici Effect. I&#8217;m curious, when you are using this during the Agile process. Iteration 0? Or is this for fleshing out ideas like you discussed in the post mortem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

