<?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: Design Consequences: A fun workshop technique for brainstorming &amp; consensus building</title>
	<atom:link href="http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/</link>
	<description>Observing, reflecting, designing.</description>
	<lastBuildDate>Thu, 09 Feb 2012 23:14:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sjors</title>
		<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/comment-page-1/#comment-246939</link>
		<dc:creator>Sjors</dc:creator>
		<pubDate>Fri, 24 Apr 2009 11:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/#comment-246939</guid>
		<description>Thanks for presenting this on #iamini, I managed to try it out already two days later.

Just to give you some feedback on the way we used it.
Because we already have an existing site, and I was a bit worried that when I would ask them to sketch, they would just sketch the current site, we defined to goal as &quot;Sketch in five minutes how our site would work on the iPhone&quot; 

The outcome was quite a positive surprise, everyone got involved, all using their own approach, we got some bullet points list, some sketches, some flowcharts. 

To speed it up a bit we decided to pick some people representing the different divisions to explain their sketches and ideas. And eventually asked everyone to give their two words on it.

The outcome was that everyone had a better understanding of what was really important and also how the current situation related to the one we all agreed on.

So, exercise was successful!  I am wondering though if I could repeat this a few times without everyone getting stuck to what they did last time. Perhaps moving to another piece of technology, a set top box, a watch, etc.

Thanks!
Sjors Timmer</description>
		<content:encoded><![CDATA[<p>Thanks for presenting this on #iamini, I managed to try it out already two days later.</p>
<p>Just to give you some feedback on the way we used it.<br />
Because we already have an existing site, and I was a bit worried that when I would ask them to sketch, they would just sketch the current site, we defined to goal as &#8220;Sketch in five minutes how our site would work on the iPhone&#8221; </p>
<p>The outcome was quite a positive surprise, everyone got involved, all using their own approach, we got some bullet points list, some sketches, some flowcharts. </p>
<p>To speed it up a bit we decided to pick some people representing the different divisions to explain their sketches and ideas. And eventually asked everyone to give their two words on it.</p>
<p>The outcome was that everyone had a better understanding of what was really important and also how the current situation related to the one we all agreed on.</p>
<p>So, exercise was successful!  I am wondering though if I could repeat this a few times without everyone getting stuck to what they did last time. Perhaps moving to another piece of technology, a set top box, a watch, etc.</p>
<p>Thanks!<br />
Sjors Timmer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna Spencer</title>
		<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/comment-page-1/#comment-193898</link>
		<dc:creator>Donna Spencer</dc:creator>
		<pubDate>Wed, 21 Jan 2009 04:52:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/#comment-193898</guid>
		<description>Awesome game. I&#039;m really sorry I missed this earlier - Andy Budd just pointed me to it!</description>
		<content:encoded><![CDATA[<p>Awesome game. I&#8217;m really sorry I missed this earlier &#8211; Andy Budd just pointed me to it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier</title>
		<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/comment-page-1/#comment-158538</link>
		<dc:creator>Olivier</dc:creator>
		<pubDate>Thu, 09 Oct 2008 08:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/#comment-158538</guid>
		<description>Hi. Would you be willen to share (some of) those &quot;*very* scratchy samples&quot;? I&#039;m not a designer so I don&#039;t really have access to lots of wireframes and other design examples. I will be doing this exercise in a couple of days though.</description>
		<content:encoded><![CDATA[<p>Hi. Would you be willen to share (some of) those &#8220;*very* scratchy samples&#8221;? I&#8217;m not a designer so I don&#8217;t really have access to lots of wireframes and other design examples. I will be doing this exercise in a couple of days though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Riccardo Cambiassi</title>
		<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/comment-page-1/#comment-11602</link>
		<dc:creator>Riccardo Cambiassi</dc:creator>
		<pubDate>Sun, 04 Mar 2007 22:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/#comment-11602</guid>
		<description>Hi Leisa,
thanks for sharing the whole process!
I really enjoyed our design consequences session at the BarCampLondon, and I&#039;m planning to use it in a similar (barcamp) context in Italy soon. I&#039;ll keep you posted.</description>
		<content:encoded><![CDATA[<p>Hi Leisa,<br />
thanks for sharing the whole process!<br />
I really enjoyed our design consequences session at the BarCampLondon, and I&#8217;m planning to use it in a similar (barcamp) context in Italy soon. I&#8217;ll keep you posted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/comment-page-1/#comment-11213</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Wed, 28 Feb 2007 09:50:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/#comment-11213</guid>
		<description>Hi Leisa,

This sounds like a great technique. I teach something similar in a paper prototyping workshop that I run from time-to-time, but this is much more immediate. (I especially like your ‘ins’ and ‘outs’ concept – a sooper-simple way of sorting and capturing the output.)

I’m a big fan of these kinds of techniques because they generate ideas quickly and early, they help to focus the team and, most importantly, they drastically lower the barrier for participation (allowing you to tap into the creativity of your entire team, your stakeholders and even your users – heresy in these Designer-driven days!) Thanks for sharing.</description>
		<content:encoded><![CDATA[<p>Hi Leisa,</p>
<p>This sounds like a great technique. I teach something similar in a paper prototyping workshop that I run from time-to-time, but this is much more immediate. (I especially like your ‘ins’ and ‘outs’ concept – a sooper-simple way of sorting and capturing the output.)</p>
<p>I’m a big fan of these kinds of techniques because they generate ideas quickly and early, they help to focus the team and, most importantly, they drastically lower the barrier for participation (allowing you to tap into the creativity of your entire team, your stakeholders and even your users – heresy in these Designer-driven days!) Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: disambiguity - &#187; BarCampLondon2</title>
		<link>http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/comment-page-1/#comment-11063</link>
		<dc:creator>disambiguity - &#187; BarCampLondon2</dc:creator>
		<pubDate>Mon, 26 Feb 2007 10:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/design-consequences-a-fun-workshop-technique-for-brainstorming-consensus-building/#comment-11063</guid>
		<description>[...] For my presentation I managed to make people who turned up do most of the work  I ran a demo of a homespun design workshop technique I&#8217;ve recently started using which we currently call &#8216;Design Consequences&#8217;. It&#8217;s much more approachable and fun than the name suggests, so I&#8217;m issuing a call for suggestions to rename it! I&#8217;ll do a write up of what Design Consequences for anyone who was there and wants the notes, and those who missed out, in the next couple of days. Thanks to everyone who came along and participated in my session. I had lots of fun! (Update: I&#8217;ve written up the technique here if you&#8217;re interested in trying it yourself) [...]</description>
		<content:encoded><![CDATA[<p>[...] For my presentation I managed to make people who turned up do most of the work  I ran a demo of a homespun design workshop technique I&#8217;ve recently started using which we currently call &#8216;Design Consequences&#8217;. It&#8217;s much more approachable and fun than the name suggests, so I&#8217;m issuing a call for suggestions to rename it! I&#8217;ll do a write up of what Design Consequences for anyone who was there and wants the notes, and those who missed out, in the next couple of days. Thanks to everyone who came along and participated in my session. I had lots of fun! (Update: I&#8217;ve written up the technique here if you&#8217;re interested in trying it yourself) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

