<?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"
	>
<channel>
	<title>Comments on: Facebook, Lifelets, and Designer Responsibility</title>
	<atom:link href="http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/</link>
	<description>A Blog about Social Web Design</description>
	<pubDate>Sat, 30 Aug 2008 05:57:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Steve Mills</title>
		<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151628</link>
		<dc:creator>Steve Mills</dc:creator>
		<pubDate>Mon, 07 Jan 2008 05:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151628</guid>
		<description>Its a very good point that the average user can only do on facebook what the provided controls allow them to do.

I think however that it is a fact of life that bugs will get through, and that it is up for the users and the designers to be diligent and spot them before they do any real damage</description>
		<content:encoded><![CDATA[<p>Its a very good point that the average user can only do on facebook what the provided controls allow them to do.</p>
<p>I think however that it is a fact of life that bugs will get through, and that it is up for the users and the designers to be diligent and spot them before they do any real damage</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zephyr</title>
		<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151539</link>
		<dc:creator>Zephyr</dc:creator>
		<pubDate>Wed, 02 Jan 2008 17:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151539</guid>
		<description>It's the *design* principle "user in control". If the design doesn't clearly communicate what's going on, and how the user can influence it, the user can't feel in control.</description>
		<content:encoded><![CDATA[<p>It&#8217;s the *design* principle &#8220;user in control&#8221;. If the design doesn&#8217;t clearly communicate what&#8217;s going on, and how the user can influence it, the user can&#8217;t feel in control.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151535</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Wed, 02 Jan 2008 16:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151535</guid>
		<description>I think your mostly right and it is an opportunity for Digg and Facebook by selling their users information to advertisers, of course they are going to do it, their user base is huge.</description>
		<content:encoded><![CDATA[<p>I think your mostly right and it is an opportunity for Digg and Facebook by selling their users information to advertisers, of course they are going to do it, their user base is huge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151518</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Wed, 02 Jan 2008 01:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151518</guid>
		<description>You're right, Dave. Some aspects of Beacon were easy enough to spot. However, the overall landscape of testing, I believe, is getting harder for most issues, especially ones where an action happens over here, and a display changes (for lots of people) over there.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, Dave. Some aspects of Beacon were easy enough to spot. However, the overall landscape of testing, I believe, is getting harder for most issues, especially ones where an action happens over here, and a display changes (for lots of people) over there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151503</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Tue, 01 Jan 2008 20:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151503</guid>
		<description>"3. Some of the issues at hand are of such spontaneous nature that current practices in design evaluation (usability testing) could not have predicted them."

For subtle points, this may be true. But the core issues with Beacon could have been predicted with by including privacy questions in those tests. Who wants to share, by name, with no opt-out, what they bought their friends for Christmas? Who wants banner ads to be plastered alongside their p2p endorsements? There's a perception that the primary Facebook demographic is ignorant of these areas; that's not what I've seen in my own tests.</description>
		<content:encoded><![CDATA[<p>&#8220;3. Some of the issues at hand are of such spontaneous nature that current practices in design evaluation (usability testing) could not have predicted them.&#8221;</p>
<p>For subtle points, this may be true. But the core issues with Beacon could have been predicted with by including privacy questions in those tests. Who wants to share, by name, with no opt-out, what they bought their friends for Christmas? Who wants banner ads to be plastered alongside their p2p endorsements? There&#8217;s a perception that the primary Facebook demographic is ignorant of these areas; that&#8217;s not what I&#8217;ve seen in my own tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151458</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 31 Dec 2007 21:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/facebook-lifelets-and-designer-responsibility/#comment-151458</guid>
		<description>I observe that operators of online business units are indeed paying attention.  Web development is becoming business development.  More and more of my conversations with clients now have to do with business factors, not technical ones (whether graphical or IT).

As independent contributors have increasingly more control over web content, large publishers and web property owners necessarily relinquish centralized control.  But I think it's bigger than that – perceptions are changing about what users can expect (i.e. "user experience"), and competitive business owners adapt to stay ahead of the industry curve.

So, these changes appear to me to manifest a natural broadening of roles within a new technology space, and I don't see this as "developers:  with power comes responsibility."  It seems like these same changes occur as most new industries become competitive.  And in this case the pain points are around privacy and accountability.

In the automotive industry, roles expanded over time to accommodate mechanics and detailers, designers and manufacturing engineers.  Perhaps that industry's pain points had to do with safety and now environmental impact.

A valid parallel?</description>
		<content:encoded><![CDATA[<p>I observe that operators of online business units are indeed paying attention.  Web development is becoming business development.  More and more of my conversations with clients now have to do with business factors, not technical ones (whether graphical or IT).</p>
<p>As independent contributors have increasingly more control over web content, large publishers and web property owners necessarily relinquish centralized control.  But I think it&#8217;s bigger than that – perceptions are changing about what users can expect (i.e. &#8220;user experience&#8221;), and competitive business owners adapt to stay ahead of the industry curve.</p>
<p>So, these changes appear to me to manifest a natural broadening of roles within a new technology space, and I don&#8217;t see this as &#8220;developers:  with power comes responsibility.&#8221;  It seems like these same changes occur as most new industries become competitive.  And in this case the pain points are around privacy and accountability.</p>
<p>In the automotive industry, roles expanded over time to accommodate mechanics and detailers, designers and manufacturing engineers.  Perhaps that industry&#8217;s pain points had to do with safety and now environmental impact.</p>
<p>A valid parallel?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<div  style="display:none; width=0px; height=0px" >
</div>