<?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 Appropriation</title>
	<atom:link href="http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/</link>
	<description>A place to find Dan Perkel's stuff on the web</description>
	<lastBuildDate>Sun, 23 Aug 2009 07:48:25 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alan&#38;#8217;s blog &#38;#187; tales from/for Berlin - appropriation, adoption and physicality</title>
		<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/comment-page-1/#comment-20</link>
		<dc:creator>Alan&#38;#8217;s blog &#38;#187; tales from/for Berlin - appropriation, adoption and physicality</dc:creator>
		<pubDate>Sun, 02 Mar 2008 13:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://dream.sims.berkeley.edu/~dperkel/wordpress/?p=17#comment-20</guid>
		<description>[...] The appropriation part of the talk was largely based on my HCI2007 short paper &#8220;designing for appropriation&#8220;. See also blogs about the topic by Palojono and Dan Perkel. [...]</description>
		<content:encoded><![CDATA[<p>[...] The appropriation part of the talk was largely based on my HCI2007 short paper &#38;#8220;designing for appropriation&#38;#8220;. See also blogs about the topic by Palojono and Dan Perkel. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nowuseit.com &#124; links for 2006-08-16</title>
		<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/comment-page-1/#comment-19</link>
		<dc:creator>nowuseit.com &#124; links for 2006-08-16</dc:creator>
		<pubDate>Tue, 22 Aug 2006 08:18:37 +0000</pubDate>
		<guid isPermaLink="false">http://dream.sims.berkeley.edu/~dperkel/wordpress/?p=17#comment-19</guid>
		<description>[...] » Designing for Appropriation Is it possible to design for appropriation and unintended uses? If so, how? If not, why not? (tags: design appropriation hackability usability innovation process) [...]</description>
		<content:encoded><![CDATA[<p>[...] » Designing for Appropriation Is it possible to design for appropriation and unintended uses? If so, how? If not, why not? (tags: design appropriation hackability usability innovation process) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anarchitect</title>
		<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/comment-page-1/#comment-18</link>
		<dc:creator>Anarchitect</dc:creator>
		<pubDate>Fri, 21 Apr 2006 00:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://dream.sims.berkeley.edu/~dperkel/wordpress/?p=17#comment-18</guid>
		<description>&lt;strong&gt;Appropriable artifacts...&lt;/strong&gt;

	In Designing for Appropriation Dan Perkel sums up a discussion at the Berkeley school of information about the misuse of artifacts in a sense that people use them in a different way than the creators had ever anticipated. He argues that users need to ...</description>
		<content:encoded><![CDATA[<p><strong>Appropriable artifacts&#8230;</strong></p>
<p>	In Designing for Appropriation Dan Perkel sums up a discussion at the Berkeley school of information about the misuse of artifacts in a sense that people use them in a different way than the creators had ever anticipated. He argues that users need to &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linda</title>
		<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/comment-page-1/#comment-17</link>
		<dc:creator>Linda</dc:creator>
		<pubDate>Mon, 17 Apr 2006 02:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://dream.sims.berkeley.edu/~dperkel/wordpress/?p=17#comment-17</guid>
		<description>I missed the discussion on this, unfortunately, but what came to mind from my own perspective (social psychology) were some thoughts I&#039;ve been having about my qualifying exam topics.

For example, research on persuasion has been used in many different ways.  I&#039;ve been thinking about which topics, if brought out to the world, could have a positive impact (from my perspective :) but maybe one point of this discussion is that it&#039;s sure hard to know where something will be taken.

In a more physical way, atomic/nuclear research and genetics could fit in this discussion too.  Whenever someone develops basic knowledge in a domain, the future trajectory of the work is unknown.</description>
		<content:encoded><![CDATA[<p>I missed the discussion on this, unfortunately, but what came to mind from my own perspective (social psychology) were some thoughts I&#8217;ve been having about my qualifying exam topics.</p>
<p>For example, research on persuasion has been used in many different ways.  I&#8217;ve been thinking about which topics, if brought out to the world, could have a positive impact (from my perspective <img src='http://blogs.ischool.berkeley.edu/dperkel/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  but maybe one point of this discussion is that it&#8217;s sure hard to know where something will be taken.</p>
<p>In a more physical way, atomic/nuclear research and genetics could fit in this discussion too.  Whenever someone develops basic knowledge in a domain, the future trajectory of the work is unknown.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/comment-page-1/#comment-16</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Sun, 16 Apr 2006 23:56:40 +0000</pubDate>
		<guid isPermaLink="false">http://dream.sims.berkeley.edu/~dperkel/wordpress/?p=17#comment-16</guid>
		<description>According to IBM&#039;s annual report, &quot;collaboration and co-creation&quot; is one of the key &quot;innovation enablers&quot; for the near future.  They cite Eric von Hippel&#039;s book &lt;a href=&quot;http://web.mit.edu/evhippel/www/democ.htm&quot; rel=&quot;nofollow&quot;&gt;Democratizing Innovation&lt;/a&gt; as saying that as many as 40% of a company&#039;s customers modify or tinker with its products in some way.

Has anyone read Hippel&#039;s book?</description>
		<content:encoded><![CDATA[<p>According to IBM&#8217;s annual report, &#8220;collaboration and co-creation&#8221; is one of the key &#8220;innovation enablers&#8221; for the near future.  They cite Eric von Hippel&#8217;s book <a href="http://web.mit.edu/evhippel/www/democ.htm" rel="nofollow">Democratizing Innovation</a> as saying that as many as 40% of a company&#8217;s customers modify or tinker with its products in some way.</p>
<p>Has anyone read Hippel&#8217;s book?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jono</title>
		<link>http://blogs.ischool.berkeley.edu/dperkel/2006/04/13/designing-for-appropriation/comment-page-1/#comment-15</link>
		<dc:creator>Jono</dc:creator>
		<pubDate>Fri, 14 Apr 2006 17:10:35 +0000</pubDate>
		<guid isPermaLink="false">http://dream.sims.berkeley.edu/~dperkel/wordpress/?p=17#comment-15</guid>
		<description>Thanks for the write-up Dan. It reminded me of a number of important points I&#039;d forgotten from the discussion. I wrote up some reflections on the &lt;a href=&quot;http://palojono.blogspot.com/2006/04/design-for-appropriation.html&quot; rel=&quot;nofollow&quot;&gt;design and appropriation&lt;/a&gt; from the discussion also (and here concerning &lt;a href=&quot;http://palojono.blogspot.com/2006/04/appropriation-innovation-users_11.html&quot; rel=&quot;nofollow&quot;&gt; innovation and appropriation&lt;/a&gt;). In particular, we considered how this fitted with traditional notions of innovation. We (Divya and I) thought their was an interesting distinction of innovation by who. But at the end of the day does it matter for the designer if someone innovates with your design - is this the sign of a more successful design or a mistake? take the Roland 808.

I think one of the important lessons, with most of these things is just to extend our traditional notion of when the development and design period ends to well after the design is introduced. As long as you&#039;re watching and listening to what people are using your design for you can be quick to react and support it. I remember &lt;a href=&quot;http://www.zephoria.org/thoughts/&quot; title=&quot;blog&quot; rel=&quot;nofollow&quot;&gt;Danah &lt;/a&gt;talking about the design of mySpace following this model of putting something unfinished out, watching what happens, and being ready to remove it and move on or see the success and be ready to support it further.</description>
		<content:encoded><![CDATA[<p>Thanks for the write-up Dan. It reminded me of a number of important points I&#8217;d forgotten from the discussion. I wrote up some reflections on the <a href="http://palojono.blogspot.com/2006/04/design-for-appropriation.html" rel="nofollow">design and appropriation</a> from the discussion also (and here concerning <a href="http://palojono.blogspot.com/2006/04/appropriation-innovation-users_11.html" rel="nofollow"> innovation and appropriation</a>). In particular, we considered how this fitted with traditional notions of innovation. We (Divya and I) thought their was an interesting distinction of innovation by who. But at the end of the day does it matter for the designer if someone innovates with your design &#8211; is this the sign of a more successful design or a mistake? take the Roland 808.</p>
<p>I think one of the important lessons, with most of these things is just to extend our traditional notion of when the development and design period ends to well after the design is introduced. As long as you&#8217;re watching and listening to what people are using your design for you can be quick to react and support it. I remember <a href="http://www.zephoria.org/thoughts/" title="blog" rel="nofollow">Danah </a>talking about the design of mySpace following this model of putting something unfinished out, watching what happens, and being ready to remove it and move on or see the success and be ready to support it further.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
