<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bokardo &#187; Netflix</title>
	<atom:link href="http://bokardo.com/tag/netflix/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com</link>
	<description>Interface Design &#38; UX by Joshua Porter</description>
	<lastBuildDate>Tue, 08 May 2012 09:53:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Netflix in Danger of Ruining their User Experience</title>
		<link>http://bokardo.com/archives/netflix-in-danger-of-ruining-their-user-experience/</link>
		<comments>http://bokardo.com/archives/netflix-in-danger-of-ruining-their-user-experience/#comments</comments>
		<pubDate>Mon, 19 Sep 2011 11:21:24 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Netflix]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=1877</guid>
		<description><![CDATA[Netflix CEO Reed Hastings wrote a blog post yesterday explaining his company&#8217;s recent decision to split up the streaming and DVD delivery services of the company. An Explanation and Some Reflections The DVD delivery service (the original service) will now be called Qwikster. Yes, that&#8217;s right, Qwikster. The streaming part of the service will continued [...]]]></description>
			<content:encoded><![CDATA[<p>Netflix CEO <a href="http://en.wikipedia.org/wiki/Reed_Hastings">Reed Hastings</a> wrote a blog post yesterday explaining his company&#8217;s recent decision to split up the streaming and DVD delivery services of the company. </p>
<p><a href="http://blog.netflix.com/2011/09/explanation-and-some-reflections.html">An Explanation and Some Reflections</a></p>
<p>The DVD delivery service (the original service) will now be called Qwikster. Yes, that&#8217;s right, Qwikster. The streaming part of the service will continued to be called Netflix. <a href="http://abovethecrowd.com/2011/09/18/understanding-why-netflix-changed-pricing/">One explanation </a> suggests this move was made in response to pressure from Hollywood who wants to charge per user access, not per copy. In other words, no ownership, nothing like owning or renting a DVD. Think Cable TV. The more things change&#8230;the more they stay the same. </p>
<p>Netflix is taking a huge risk here. They&#8217;re changing the user experience of their web apps to model the new company structure, not a structure that is most friendly to people. This is an extremely common problem in user interface design. Netflix is in serious danger of breaking the user experience they are well-known for. </p>
<p>As one commenter complains there will now be two separate movie queues, one on Netflix for streaming and one on Qwikster for DVDs. Hasting&#8217;s response is dismissive: </p>
<blockquote><p>&#8220;We already have two queues. The two &#8220;sites&#8221; are a click between each other, so we think not that much different than two tabs on one site.&#8221;</p>
</blockquote>
<p>Technically, Hastings is right about there already being two queues. But he&#8217;s dead wrong about it being much different. Obviously he&#8217;s never watched people use web applications before. Changing websites is not even close to the same thing as changing tabs. When you change websites you go somewhere different, you get a different UI, you&#8217;re using a different username, and you probably have to log in. You have a different payment system. Different family members to add. Different recommendations to look at. And that&#8217;s just for starters. </p>
<p>When you change tabs you don&#8217;t lose any of that context. You stay in the same place, you just get a different list. </p>
<p>This is a fundamental change in the product, and Hastings just dismisses the concern with a wave of his hand. Not only that, but this is a branding issue as well. When you switch sites you&#8217;re going from Netflix, a brand people know and love, to Qwikster, which sounds like the latest get rich quick startup without a real business plan. </p>
<p>It may be that the split was inevitable, but why not name the DVD service &#8220;Mailflix&#8221; and give people a chance to understand what&#8217;s actually going on? Give them some semi-logical name that actually makes sense? Mailflix for movies in the mail, Netflix for movies on the Internet?</p>
<p>Also, people don&#8217;t think they&#8217;re buying two services right now&#8230;they&#8217;re simply buying Netflix. As another commenter points out: </p>
<blockquote><p>&#8220;You&#8217;re continuing to make a classic mistake: thinking you&#8217;re something different than what everyone believes you are. You&#8217;re not a DVD company and a streaming company: you&#8217;re where I go to watch movies. That&#8217;s it. The future clearly is streaming, but by separating and charging more for access, you&#8217;re wildly less valuable to me. I&#8217;ll likely cancel. You haven&#8217;t listened to customer feedback. You&#8217;re delusional and you&#8217;re lost.&#8221;</p>
</blockquote>
<p>There is one angle where all of this makes sense. Let&#8217;s assume for a moment that Netflix is knowingly trying to kill off its DVD rental service. This is the way to do it&#8230;separate it out completely, give it a ridiculous name, and keep your brand equity with the newer streaming service. This almost makes sense&#8230;except for the fact that the content in Netflix streaming has gotten worse, not better, over time. If they really wanted to focus attention solely on Netflix going forward, they would create a catalog worth watching. Right now the streaming catalog is abysmal, and with movies that can only mean it gets worse over time as you watch the one or two you haven&#8217;t seen yet. </p>
<p>So as a Netflix subscriber who doesn&#8217;t even use the service anymore (outside of my kids watching educational videos) I&#8217;m left wondering&#8230;what is Reed Hastings and Netflix thinking? </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/netflix-in-danger-of-ruining-their-user-experience/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The Social Graph and Objects of Sociality</title>
		<link>http://bokardo.com/archives/the-social-graph-and-objects-of-sociality/</link>
		<comments>http://bokardo.com/archives/the-social-graph-and-objects-of-sociality/#comments</comments>
		<pubDate>Tue, 11 Sep 2007 15:03:43 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>
		<category><![CDATA[Youtube]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/the-social-graph-and-objects-of-sociality/</guid>
		<description><![CDATA[<em>Why our relationships can't be explained without the objects and experiences that we share.</em>

One of the biggest problems on the Web is joining a new social networking site. To do so means going through the painful effort of creating a profile and adding all of our friends, something we've done over and over...at least once for each social networking site we already belong to. This is quickly becoming an issue for everyone who uses social networks.

This problem has led to a flurry of activity, highlighted by LiveJournal creator Brad Fitzpatrick's missive: <a href="http://bradfitz.com/social-graph-problem/">Thoughts on the Social Graph</a>, in which he clearly outlines the issues involved as well as some worthy goals to shoot for. Brad's piece was followed shortly after by the <a href="http://opensocialweb.org/">Bill of Rights for Users of the Social Web</a>, which among its rights is the right to allow users to syndicate their own profile and friend data. This, of course, would alleviate the squeaky wheel.

<img src="http://bokardo.com/images/social-network.gif" alt="Social Network" style="float:right;margin:0 0 10px 10px;" />

In addition there are countless groups getting together to try and solve this problem. The <a href="http://microformats.org">microformats</a> folks are working on building formats to help with this. The <a href="http://datasharingsummit.com/">DataSharingSummit</a> is an entire event focused on this and related problems. All of this activity is centered around one idea: that people have a social graph that can be represented in software. In other words, we can recreate our offline relationships online and let everyone know about it by sharing some sort of file or feed. 

The major axis of the social graph, as Fitzpatrick points out, is relationships between people, or more simply, a list of friends. My social graph, for example, consists of my friends, colleagues, family, and acquaintances. These people I know to some extent or another, some I talk with daily, some I know only online, and some I would rather not speak to. :)]]></description>
			<content:encoded><![CDATA[<p><em>Why our relationships can&#8217;t be explained without the objects and experiences that we share.</em></p>
<p>One of the biggest problems on the Web is joining a new social networking site. To do so means going through the painful effort of creating a profile and adding all of our friends, something we&#8217;ve done over and over&#8230;at least once for each social networking site we already belong to. This is quickly becoming an issue for everyone who uses social networks.</p>
<p>This problem has led to a flurry of activity, highlighted by LiveJournal creator Brad Fitzpatrick&#8217;s missive: <a href="http://bradfitz.com/social-graph-problem/">Thoughts on the Social Graph</a>, in which he clearly outlines the issues involved as well as some worthy goals to shoot for. Brad&#8217;s piece was followed shortly after by the <a href="http://opensocialweb.org/">Bill of Rights for Users of the Social Web</a>, which among its rights is the right to allow users to syndicate their own profile and friend data. This, of course, would alleviate the squeaky wheel.</p>
<p><img src="http://bokardo.com/images/social-network.gif" alt="Social Network" style="float:right;margin:0 0 10px 10px;" /></p>
<p>In addition there are countless groups getting together to try and solve this problem. The <a href="http://microformats.org">microformats</a> folks are working on building formats to help with this. The <a href="http://datasharingsummit.com/">DataSharingSummit</a> is an entire event focused on this and related problems. All of this activity is centered around one idea: that people have a social graph that can be represented in software. In other words, we can recreate our offline relationships online and let everyone know about it by sharing some sort of file or feed. </p>
<p>The major axis of the social graph, as Fitzpatrick points out, is relationships between people, or more simply, a list of friends. My social graph, for example, consists of my friends, colleagues, family, and acquaintances. These people I know to some extent or another, some I talk with daily, some I know only online, and some I would rather not speak to. <img src='http://bokardo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>At this point we could easily move forward and accept the common notion of social networks: that they are made up only of relationships between people. But for those folks working deeply on these issues another problem soon arises: the realization that there is more to the social graph than just people&#8230;there are objects that <em>mediate</em> our relationships as well. </p>
<p>I&#8217;ve always been uncomfortable with the word &#8220;mediate&#8221; because it is not entirely clear what it means. But in this case it means something like this: our relationships with other people are determined in part by the activities and objects we share. This idea has long been known in the world of social psychology, and could have big effects on the utility of the social graph going forward.</p>
<p>For example, our YouTube and MySpace and Flickr friends exist partly in relation to the content that we&#8217;ve shared with each other on those sites. Our lifelong friends exist in relation to the things we&#8217;ve done together: the places we&#8217;ve gone to, the words we&#8217;ve spoken, and the movies we&#8217;ve seen. It doesn&#8217;t make sense to talk about our friends without these mediating objects, and <em>that&#8217;s why our social graph must also represent them as well</em>. </p>
<p>This view is explained wonderfully by Jyri EngestrÃ¶m in this post: <a href="http://www.zengestrom.com/blog/2005/04/why_some_social.html">Why some social network services work and others don&#8217;t â€” Or: the case for object-centered sociality </a>. EngestrÃ¶m argues for an &#8220;objects of sociality&#8221; view of social networks, where people aren&#8217;t the only objects necessary for relationships. EngestrÃ¶m&#8217;s post is in turn based on the work of sociology professor <a href="http://www.uni-konstanz.de/knorrcetina/">Karin Knorr Cetina</a>. </p>
<p>This notion of &#8220;objects of sociality&#8221; helps explain the success of sites such as YouTube, Flickr, and Netflix. (and, I might add, the slideshow sharing service <a href="http://www.slideshare.net/">Slideshare</a> co-created by my friend <a href="http://rashmisinha.com">Rashmi Sinha</a>, whom I first heard the term &#8220;objects of sociality&#8221; from). What these services have done is to create a system that supports relationships around the objects of videos, photos, and movies, and slideshows. And as I wrote about the other day (<a href="http://bokardo.com/archives/what-if-youtube-was-simply-lucky/">What if YouTube was simply lucky?</a>), their success seems based on their ability to make the activities of uploading, viewing, and sharing as painless as possible. </p>
<p>Still, Jyri suggests that most notions of social networks are restricted to people. He says:</p>
<blockquote><p>&#8220;Approaching sociality as object-centered is to suggest that when it becomes easy to create digital instances of the object, the online services for networking on, through, and around that object will emerge too. Social network theory fails to recognise such real-world dynamics because its notion of sociality is limited to just people.&#8221;</p>
</blockquote>
<p>It&#8217;s interesting to note that Facebook, who is at the center of this social graph discussion because of their partially-closed (or partially-open, however you want to look at it) system, asks everyone who adds a friend how you know them. They want to know if you worked with them, if you went to school with them, or if you met them through an acquaintance. These items, the job, the school, and the other friend, are the very objects of sociality that make the relationship work. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/the-social-graph-and-objects-of-sociality/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Why I started Bokardo Design</title>
		<link>http://bokardo.com/archives/why-i-started-bokardo-design/</link>
		<comments>http://bokardo.com/archives/why-i-started-bokardo-design/#comments</comments>
		<pubDate>Thu, 09 Aug 2007 13:13:39 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Bokardo Design]]></category>
		<category><![CDATA[Del.icio.us]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/why-i-started-bokardo-design/</guid>
		<description><![CDATA[While I'm hurriedly working on building out a corporate site for Bokardo Design, I thought I would take a minute and share a little background which led me to starting the company and what services I'm offering. 

Many of you know that I worked at <a href="http://www.uie.com">User Interface Engineering</a> for 5 years. It was definitely the best and most exciting job I've ever had; Jared and the team are fantastic. While I am super excited about what I'm doing now, I am sorry to leave such a unique and wonderful place. Even so, I won't be leaving UIE completely...we're still collaborating on several projects and will continue to do so where appropriate. 

<img src="http://bokardo.com/images/bokardo-design-badge-small.gif" alt="" style="float:right; margin-left:10px;" />

When I was at UIE I did a mix of usability consulting and web design. Usability consulting for UIE clients and in-house web design and development for UIE itself. So I basically alternated between consulting and designing. In hindsight this afforded me an excellent opportunity to understand the design problem from both sides of the fence: from the view of an objective 3rd party consultant as well as from the standpoint of an in-the-trenches designer. These worlds are incredibly different, and both are unique in their own way. ]]></description>
			<content:encoded><![CDATA[<p>While I&#8217;m hurriedly working on building out a corporate site for Bokardo Design, I thought I would take a minute and share a little background which led me to starting the company and what services I&#8217;m offering. </p>
<p>Many of you know that I worked at <a href="http://www.uie.com">User Interface Engineering</a> for 5 years. It was definitely the best and most exciting job I&#8217;ve ever had; Jared and the team are fantastic. While I am super excited about what I&#8217;m doing now, I am sorry to leave such a unique and wonderful place. Even so, I won&#8217;t be leaving UIE completely&#8230;we&#8217;re still collaborating on several projects and will continue to do so where appropriate. </p>
<p><img src="http://bokardo.com/images/bokardo-design-badge-small.gif" alt="" style="float:right; margin-left:10px;" /></p>
<p>When I was at UIE I did a mix of usability consulting and web design. Usability consulting for UIE clients and in-house web design and development for UIE itself. So I basically alternated between consulting and designing. In hindsight this afforded me an excellent opportunity to understand the design problem from both sides of the fence: from the view of an objective 3rd party consultant as well as from the standpoint of an in-the-trenches designer. These worlds are incredibly different, and both are unique in their own way. </p>
<p>But I kept running into the same problem. We would talk to people who have these grand visions for their business, and then you would investigate how people were using their site and there was this huge disconnect. Either their strategy wasn&#8217;t clear, it wasn&#8217;t being communicated to the designers, or the designers weren&#8217;t able to take that strategy and embed it into an actual interface. The chain of communication from business strategy to interface to user was tenuous at best. In many cases there was no direct conversation between these parties at all. </p>
<p>The problem I kept seeing over and over was one of translation. Interfaces were not communicating what their creators wanted them to communicate. It&#8217;s kind of like a beginning writer who has a grand fantasy of a story in their head but the words on the paper give you no sense of it. But their interfaces were definitely communicating something, though&#8230;unfortunately it was something other than what was intended. </p>
<p>At around this same time there was an explosion of social software, or software that is built around the social lives of users. In testing at UIE we saw the extreme power of this social influence&#8230;we would run user tests and find out why people were making the decisions they were making. In <em>many</em> cases they were making decisions based on their social network.</p>
<p>For example, we did a huge user testing study where we tested over a dozen e-commerce web sites. We had 70 or so people actually buy products from these web sites and part of our research was to find out how they made purchasing decisions. In more cases than I can count people said things like &#8220;Well, I knew I wanted a digital camera but I didn&#8217;t know what kind. My friend really likes Canon cameras and recommended them to me&#8221;. People who don&#8217;t know something rely on their social network to find it out. </p>
<p>After we heard stuff like this this over and over again, it became clear to me that the future of software is social. And while social networking was taking off like a rocket it was also clear that it wasn&#8217;t just about networking with others, it was about finding out what others knew and using that information to help make decisions. That&#8217;s why I write about Amazon, Netflix and other sites that aren&#8217;t about connecting to new people, but are leveraging our social networks to help us find out what we need to know. The latent information in our social networks is still mostly untapped. If we only knew what the people we know, know. </p>
<p>So I wrote two pieces on my blog, one called <a href="http://bokardo.com/archives/the-delicious-lesson/">The Del.icio.us Lesson</a> and the other called <a href="http://bokardo.com/archives/diggs-design-dilemma/">Digg&#8217;s Design Dilemma</a> that together outline two important principles of what is going on. </p>
<p>The first (from the <a href="http://bokardo.com/archives/the-delicious-lesson/">Del.icio.us Lesson</a>) is that most people are acting in their own self-interest first: personal value precedes network value. This simple formulation has a huge effect on how to design, what features to focus on, and how to elicit participation and desired behavior. </p>
<p>Second (from <a href="http://bokardo.com/archives/diggs-design-dilemma/">Digg&#8217;s Design Dilemma</a>) was that the interface is the medium through which this all occurs, and thus acts as an arbiter to behavior. In other words, all that happens happens because the interface either encourages it through positive design or discourages it through negative design. Therefore, the value and importance of the interface cannot be understated. </p>
<p>So these are the factors that drove me to start Bokardo Design. The services that I offer are a direct offshoot of these problems, observations, and principles.</p>
<p>So this is what I&#8217;m offering: Interface design and strategy for social web applications. </p>
<h2>Interface Design</h2>
<p>For some folks coming up with a strategy is the part they&#8217;re good at, while interface design is inscrutable. But on the Web, <em>interface design is the execution of strategy</em>. So I&#8217;m offering a service to create interfaces that execute on strategy. I&#8217;ll work closely with you to figure out the best way to expose a strategy through an interface, and how best to elicit the correct activities from your audience. </p>
<p>For example, I&#8217;m currently working with someone whose strategy is to help people find out the best local events to attend (there are <em>many</em> people doing things in this area right now). To do this, we need to figure out how people plan their time in and around events and how they make decisions about which events to attend. Not only that, but the way that people communicate events to each other is also important&#8230;and building a tool to help them do could be extremely valuable. Coming up with an interface that actually allows people to find and share events <em>in the way they already are</em> is the goal. </p>
<p>There are two levels of details to consider. One is the screen-level, where we build buttons and layouts that draw people&#8217;s attention to the right things in the right order. But there is also the activity-level, where we create flows that support the right activities in the right order. These two levels combine to make up interface design. </p>
<p>My interface design service is about creating an interface that executes an underlying strategy for success. </p>
<h2>Interface Strategy</h2>
<p>For many folks who aren&#8217;t native to the Web executing a coherent Web-based strategy is a challenge. There are a lot of questions to consider. When do you announce your idea? When do you launch? Should you do a complete redesign? How do you know if the interface is working or not? What if we launch and nobody uses it? The questions go on and on.</p>
<p>For example, I&#8217;m currently working with a client who has amazing ideas about where to take their service. But right now they need to focus their strategy on personal value because they haven&#8217;t articulated that in their interface yet. They&#8217;ve focused on the social value so far, essentially putting them into a chicken/egg problem thats promises users &#8220;our service will be valuable once a lot of people start using it&#8221;. This might be OK if we all had limitless attention span and could try out services like we try on clothes. But the Web environment is brutal, and so this is not a desirable place to be, yet countless people I&#8217;ve talked to are in this exact spot. </p>
<p>My interface strategy service is about working with folks who are having trouble formalizing a plan to build and release a focused, Web-based application. </p>
<h2>Why I&#8217;m Excited</h2>
<p>I&#8217;m extremely excited by the early interest in Bokardo Design. I&#8217;ve heard from entrepreneurs doing social start-ups, established companies looking to add social features to existing applications, and even some visionaries thinking about huge-scale services that could change the way we all look at the Web. </p>
<p>All of my conversations so far have reinforced the idea that building social features into software is really the sweet spot at the moment, as we have collectively realized that software is just an extension of what we already do: it&#8217;s not this fantasy land we visit only once in a while. To this end we must keep our software <em>humane</em>, to borrow a word from Jeff Raskin. And on that note, here&#8217;s something else that he said so well: </p>
<blockquote><p>&#8220;As far as the customer is concerned, the interface is the product.&#8221;</p>
</blockquote>
<p>Amen. If there is one statement that defines what I do at Bokardo Design, that is it. So if you&#8217;re interested in building an amazing interface, head on over to my <a href="http://bokardo.com/contact/">contact page</a> and say Hi. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/why-i-started-bokardo-design/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Putting the Del.icio.us Lesson into Practice, Part I: The Cold-Start Problem</title>
		<link>http://bokardo.com/archives/putting-the-delicious-lesson-into-practice-part-i/</link>
		<comments>http://bokardo.com/archives/putting-the-delicious-lesson-into-practice-part-i/#comments</comments>
		<pubDate>Tue, 24 Jul 2007 12:38:49 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Del.icio.us]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/putting-the-delicious-lesson-into-practice-part-i/</guid>
		<description><![CDATA[One of the emerging principles of social design is what I call <a href="http://bokardo.com/archives/the-delicious-lesson/">The Del.icio.us Lesson</a>, which can be summarized as "personal value precedes network value". Since I wrote about the Del.icio.us Lesson last year, it has become one of my most read and cited posts. 

Other evidence would suggest that there's something to it as well, that it is indeed a strong principle that helps us build better social software. Several of the social design folks that I regularly read, including <a href="http://vanderwal.net">Thomas Vander Wal</a> and <a href="http://www.rashmisinha.com/">Rashmi Sinha</a>, have observed similar phenomena. In a talk she gave about social design at <a href="http://2007.wordcamp.org/">Wordcamp</a>, Rashmi's first principle was "Make the system personally useful". You can see <a href="http://www.slideshare.net/rashmi/social-design-wordcamp">her slides here</a>. 

Now, it's one thing to talk about the importance of personal value and how that personal value precedes network value, but just what does the Del.icio.us Lesson mean in practice? That's what this series of posts is about... 
]]></description>
			<content:encoded><![CDATA[<p>One of the emerging principles of social design is what I call <a href="http://bokardo.com/archives/the-delicious-lesson/">The Del.icio.us Lesson</a>, which can be summarized as &#8220;personal value precedes network value&#8221;. Since I wrote about the Del.icio.us Lesson last year, it has become one of my most read and cited posts. </p>
<p>Other evidence would suggest that there&#8217;s something to it as well, that it is indeed a strong principle that helps us build better social software. Several of the social design folks that I regularly read, including <a href="http://vanderwal.net">Thomas Vander Wal</a> and <a href="http://www.rashmisinha.com/">Rashmi Sinha</a>, have observed similar phenomena. In a talk she gave about social design at <a href="http://2007.wordcamp.org/">Wordcamp</a>, Rashmi&#8217;s first principle was &#8220;Make the system personally useful&#8221;. You can see <a href="http://www.slideshare.net/rashmi/social-design-wordcamp">her slides here</a>. </p>
<p>Now, it&#8217;s one thing to talk about the importance of personal value and how that personal value precedes network value, but just what does the Del.icio.us Lesson mean in practice? That&#8217;s what this series of posts is about. </p>
<p>The first step to putting the Del.icio.us Lesson into practice is asking a simple question that serves as the litmus test.  </p>
<p><strong><em>Is your system useful to someone even if nobody else uses it?</em></strong></p>
<p>When the answer to this question is NO, then you&#8217;re ripe to suffer from the Cold-Start Problem. </p>
<h2>The Cold-Start Problem</h2>
<p>The Cold-Start Problem is when you launch your site and nobody uses it. When this happens, you&#8217;re probably focusing too much on the social value and not enough on personal value. You&#8217;ve made a bet that you can convince the masses to all sign up for your service at once, so that there is suddenly lots of value for everyone, sharing, commenting, and generally supplying user-generated content by the bucketful. I&#8217;ve talked to many folks who imagine this state of nirvana, and it rarely, if ever, actually happens. </p>
<p>Looking at sites like YouTube and Digg might make the Cold-Start Problem seem less dangerous than it really is. We look at YouTube, for example, and it seems like a self-perpetuating system. People upload videos for sharing and then other people come and find the best ones. But, really, at its core YouTube focuses on personal value first. They do this by providing an excellent service for uploading and saving videos&#8230;for free. As I mentioned in <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-2">my series on common pitfalls of building social web applications</a>, YouTube is first a great, free service for storing videos, and second a great place to find those videos shared socially. </p>
<h2>Groupware</h2>
<p>Now, we must distinguish between groupware and software that isn&#8217;t built for groups. Groupware is software built for multiple people to use: it isn&#8217;t useful <em>unless</em> there is a group using it. This includes social networking sites such as MySpace and Facebook, messaging systems such as Twitter, bulletin boards, help systems, collaboration applications, project management software, etc. This software is kind of a middle ground, where the value is communication&#8230;the personal value is that you are connected to others. The important thing to notice is that <strong>most software isn&#8217;t groupware!</strong> Most sites aren&#8217;t like MySpace and Facebook or even email, even though they might like to be as successful. This doesn&#8217;t mean that there aren&#8217;t a lot of communication-oriented start-ups&#8230;there are. But they are still a very small portion of the total web application universe. </p>
<h2>Tools for Use</h2>
<p>Most web applications are tools to get work done. And as such, they serve to get work done for an individual before a group. So, returning to the original question: is your service valuable if only one person uses it? We know something is valuable if it satisfies one of several conditions: Does it make something <em>possible</em>? Does it make something <em>easier</em>? Does it make something <em>faster</em>? If it makes something possible, easier, or faster then you probably provide personal value. If it doesn&#8217;t, then you might consider going back and trying to provide at least one of these benefits. </p>
<p>The best tools do one thing very well. It nails a certain activity to the wall and really makes it simple and easy. Hammers drive in nails. Del.icio.us saves bookmarks. Netflix sends you movies. Photoshop enables image editing. iTunes plays music, etc. All of these tools actually have other uses, but that&#8217;s the 1%. We naturally gravitate toward software with a single purpose because its easier to remember and we know exactly what we&#8217;re doing when we&#8217;re using it. </p>
<h2>Apps with Cold-Start Problem Lack a Clear Personal Activity</h2>
<p>The Cold-Start Problem usually happens when there is not a clear personal activity supported in the software. In other words, the software is not succeeding as a personal tool for use. Getting over this hurdle is one of the major challenges facing many web applications out there&#8230;in a networked world you have to provide immediate, personal value in order to grow from a seed to a tree. </p>
<p>Continue to <a href="http://bokardo.com/archives/putting-the-delicious-lesson-into-practice-part-ii/">Putting the Del.icio.us Lesson into Practice, Part II: Feature Creep</a></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/putting-the-delicious-lesson-into-practice-part-i/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Why is the Netflix Site Good?</title>
		<link>http://bokardo.com/archives/why-is-the-netflix-site-good/</link>
		<comments>http://bokardo.com/archives/why-is-the-netflix-site-good/#comments</comments>
		<pubDate>Sun, 15 Jul 2007 11:55:28 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/why-is-the-netflix-site-good/</guid>
		<description><![CDATA[<a href="http://netflix.com">Netflix.com</a> is one of my favorite sites, both for the valuable service they provide but also because they do really great web application work. From the <a href="http://blog.netflix.com/2007/07/product-development-insights.html">Netflix Community Blog</a>:

<strong>Question</strong>: "If we KNOW something is a feature you want, or a feature we want, why isn't it on the site already -- or why is it taking so long to release?"]]></description>
			<content:encoded><![CDATA[<p><a href="http://netflix.com">Netflix.com</a> is one of my favorite sites, both for the valuable service they provide but also because they do really great web application work. From the <a href="http://blog.netflix.com/2007/07/product-development-insights.html">Netflix Community Blog</a>:</p>
<p><strong>Question</strong>: &#8220;If we KNOW something is a feature you want, or a feature we want, why isn&#8217;t it on the site already &#8212; or why is it taking so long to release?&#8221;</p>
<p><strong>Answer</strong>: </p>
<blockquote><p>&#8220;sometimes it is because a simple feature is more complicated than it at first appeared, and sometimes its because much more important features are on the top of our engineers&#8217; priorities list, but one of the most significant reasons is that we don&#8217;t want to make the website more complicated than it needs to be. The site not only has to work for powerusers but also for my mom. Or your mom. We have to consider this kind of &#8220;feature creep&#8221; all the time and it keeps us from just dumping a ton of odd functions into the website.</p>
<p>Do you think we don&#8217;t want to have the screenwriter on movie pages? (For cryin&#8217;outloud&#8211;some of my best friends are screenwriters. Heck, my brother is a screenwriter. Believe me, I think it would be great to get that info on movie pages.) So once you and we all agree something like that would be great, we start a serious exploration of the pros and cons, with lots of designing, with lots of testing, and make sure that it really is a good feature and not just another cool doohickie. In most cases, these features do make it to the website. But <strong>we are exceptionally careful at this. And the website is pretty good precisely because we are careful at this</strong>.&#8221;</p>
</blockquote>
<p>(my emphasis added) </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/why-is-the-netflix-site-good/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Common Pitfalls of Building Social Web Applications and How to Avoid Them, Part 3</title>
		<link>http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-3/</link>
		<comments>http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-3/#comments</comments>
		<pubDate>Wed, 11 Jul 2007 13:09:43 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-3/</guid>
		<description><![CDATA[<em>This is part III of a series on Common Pitfalls of Building Social Web Applications. Read <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications/">Part I</a> and <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-2">Part II</a></em>

<h2>8) Not Enabling Recommendations</h2>

Thoughtful recommendations are the best possible way to increase your user base. It is word-of-mouth in action. When someone takes time out of their day to say something really nice about your service, making an honest-to-goodness recommendation, you will definitely see positive results. The question is, are you making it easy for your users to recommend you? 

In our world lots of people make recommendations, but many of them are paid to do so or are looking after their own interests. Take, for example, the Publisher's book descriptions on Amazon.com. These are always super-positive...they explain why the book is so great and why you should buy it. They would never contain anything negative, never contain anything that might potentially hurt the sales of the book.

And, as a result, the book description tells us exactly what we would expect from a publisher. To Amazon's credit, they have over time given individual reviews and ratings more prominence on the product page, signaling that that content is more valuable to users. And of course it should be...those people aren't biased in the way the publishing house is. 

<img src="http://bokardo.com/images/netflix-tell-a-friend.jpg" alt="Netflix Tell a Friend" style="float:right;margin-left:10px;" />Many sites add incentives for recommendations so that people give them more freely. Netflix, for example, allows you to give "free movies" to friends while you tell them about the service. This is a good approach. Netflix does not reward you for this...the act of giving is all that you get. If Netflix did give you a free movie that would introduce too much bias...and while more people might make recommendations it would quickly turn into a case similar to the publishers...as people would realize that there is something in it for the recommender. 
]]></description>
			<content:encoded><![CDATA[<p><em>This is part III of a series on Common Pitfalls of Building Social Web Applications. Read <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications/">Part I</a> and <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-2">Part II</a></em></p>
<h2>8. Not Enabling Recommendations</h2>
<p>Thoughtful recommendations are the best possible way to increase your user base. It is word-of-mouth in action. When someone takes time out of their day to say something really nice about your service, making an honest-to-goodness recommendation, you will definitely see positive results. The question is, are you making it easy for your users to recommend you? </p>
<p>In our world lots of people make recommendations, but many of them are paid to do so or are looking after their own interests. Take, for example, the Publisher&#8217;s book descriptions on Amazon.com. These are always super-positive&#8230;they explain why the book is so great and why you should buy it. They would never contain anything negative, never contain anything that might potentially hurt the sales of the book.</p>
<p>And, as a result, the book description tells us exactly what we would expect from a publisher. To Amazon&#8217;s credit, they have over time given individual reviews and ratings more prominence on the product page, signaling that that content is more valuable to users. And of course it should be&#8230;those people aren&#8217;t biased in the way the publishing house is. </p>
<p><img src="http://bokardo.com/images/netflix-tell-a-friend.jpg" alt="Netflix Tell a Friend" style="float:right;margin-left:10px;" />Many sites add incentives for recommendations so that people give them more freely. Netflix, for example, allows you to give &#8220;free movies&#8221; to friends while you tell them about the service. This is a good approach. Netflix does not reward you for this&#8230;the act of giving is all that you get. If Netflix did give you a free movie that would introduce too much bias&#8230;and while more people might make recommendations it would quickly turn into a case similar to the publishers&#8230;as people would realize that there is something in it for the recommender. </p>
<h2>9. Failing to Set a Good Example</h2>
<p>People tend to imitate the behavior around them. It&#8217;s how we learn. We don&#8217;t just gravitate to a new place and automatically know how to behave there. We watch others and do what they do. </p>
<p>A solid strategy, and one that is often overlooked in social sites, is to set a good example of what a member of that community does. Specifically, to have a member of the project team illustrate what good behavior is. Do they send helpful messages to others? Probably. Do they post friendly comments? Yes. Are they happy to be here? Yes. So good examples start with the caretakers of the site&#8230;what they do will be mimicked by the initial set of users. </p>
<p>A good example of this is Seth Godin and Squidoo. Seth continuously eats his own dog food (he&#8217;s created <a href="http://www.squidoo.com/lensmasters/sethgodin">dozens of lenses</a>). One of his more popular lenses is <a href="http://www.squidoo.com/topfreethings/">The 8 Free Things Every Site (or Lens!) Should Do</a>, in which he gives advice about how to attract attention to your web site or lens. In creating this Seth is adding value to the service, giving others a good example about how to use Squidoo, and also selling the service itself. </p>
<p>From a social standpoint, this has a very positive affect. If Squidoo is good enough for its founder, then it&#8217;s probably good enough for other folks, too. </p>
<h2>10. Failure to See the Larger War</h2>
<p>One of the few metrics that matters for social apps is how many people are using it. But no matter how fast you can grow, this doesn&#8217;t happen at once. It&#8217;s actually a series of battles over time, crucial moments that you overcome that generate the next level of attention for the application. </p>
<p>Many social sites fail to see the larger war of which they are a part. Instead, they focus on one or two explosive moments, like being Techcrunched, that will make or break the service. But the truth is that getting Techcrunched is just super-fast attention&#8230;the people coming from Techcrunch are not motivated people who have incentives to use your service in the way that those driven by word-of-mouth will be. </p>
<p>Techcrunch is not word-of-mouth. Getting Techcrunched or Slashdotted or getting Dugg&#8230;is like being involved in a drive-by shooting. I&#8217;ve also heard it described as getting <em>seagulled</em>&#8230;they swoop in for the attack and are gone in a second. Here at Bokardo this has happened several times, and each time I get less and less value from the attention. The people who come are not my main audience, although a small number of them might start reading regularly. The event surely isn&#8217;t like a great recommendation by a peer or reviewer, which is what social design is all about. </p>
<p><img src="http://bokardo.com/images/seagulls.jpg" alt="Seagulls Attacking" title="Attribution: http://flickr.com/photos/tomloudon/169526025/"  /></p>
<p>So the larger war is a long-term focus on providing value not the to TechCrunch crowd, but to a much more specific population that really cares about what you&#8217;re doing. This population doesn&#8217;t do drive bys&#8230;their attention is much more valuable than that. </p>
<h2>11. No Business Plan other than to Grow</h2>
<p>The success of MySpace and Facebook has really caused an over-focus on growing a huge user base to eventually sell or show advertising to. Percentage-wise, the number of social apps that reach this size is relatively tiny&#8230;these sites are extreme outliers but are super well-known because they get all the press. We all have to admit, the success of 23-year-old Mark Zuckerberg of Facebook is a great story.</p>
<p>All too often, however, social sites have no other strategy than to follow in the footsteps of these Black Swans, to grow and grow and grow over a year or two and then to figure out how to make money at that point. But the hard part isn&#8217;t figuring out how to monetize a site with millions of users. The hard part is surviving long enough to grow that big. </p>
<p>The first problem, put brilliantly by Josh Kopelman, is to get users to pay a penny. He calls this <a href="http://redeye.firstround.com/2007/03/the_first_penny.html">The Penny Gap</a>, which happens when the multitude of competing services are free and the biggest challenge becomes getting users to pay even a penny for what you have. He says: </p>
<blockquote><p>&#8220;The truth is, scaling from $5 to $50 million is not the toughest part of a new venture &#8211; it&#8217;s getting your users to pay you anything at all. The biggest gap in any venture is that between a service that is free and one that costs a penny.&#8221;</p>
</blockquote>
<p>While it is possible to make money on a huge user population by advertising or selling out to a Google or Yahoo, it&#8217;s an incredible risk that only a few people will successfully navigate a year. Wouldn&#8217;t it be better if your users were paying you all along? Offer them tiered services, with a free plan that provides the basic valuable service and premium plans that provide something more. </p>
<p><em>This is part III of a series on Common Pitfalls of Building Social Web Applications. Read <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications/">Part I</a> and <a href="http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-2">Part II</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/common-pitfalls-of-building-social-web-applications-and-how-to-avoid-them-part-3/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Netflix is Designing with Community Input</title>
		<link>http://bokardo.com/archives/designing-with-community-input-netflix-style/</link>
		<comments>http://bokardo.com/archives/designing-with-community-input-netflix-style/#comments</comments>
		<pubDate>Mon, 09 Jul 2007 12:39:45 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/designing-with-community-input-netflix-style/</guid>
		<description><![CDATA[The Netflix team has a blog: <a href="http://blog.netflix.com/">Netflix Community Blog</a> (via <a href="http://sarahcpr.com/2007/07/02/design-by-community/">Sarah</a>)

<img src="http://bokardo.com/images/netflix.gif" alt="Netflix" style="float:right;margin-left:10px;" />The blog is interesting for several reasons, most notably the candidness of the posts. In this post on <a href="http://blog.netflix.com/2007/07/hiding-movies-sequel.html">Movie Privacy</a>, for example, the team talks about a new feature whereby you can mark movies private, so as to not show them to your friends. Michael writes:  

<blockquote>"So, in a rather unNetflix-like way, we're just going to release it to Friends users in the next week or so. Let's see if this finally allows you to connect to folks you know slightly less well (or maybe too well), and for whom you absolutely needed the ability to hide some titles. We've all read your comments and suggestions for how best to implement this. Trust me: this isn't that. It's not that we're not hearing your suggestions, it's just i was interested in getting this in front of you quickly."</blockquote>

This is really cool! Michael is obviously taking on a community manager type role here, announcing new features and asking for feedback. Saying that their new feature isn't even the one that users were asking for is pretty interesting, too...how many design teams would do that? ]]></description>
			<content:encoded><![CDATA[<p>The Netflix team has a blog: <a href="http://blog.netflix.com/">Netflix Community Blog</a> (via <a href="http://sarahcpr.com/2007/07/02/design-by-community/">Sarah</a>)</p>
<p><img src="http://bokardo.com/images/netflix.gif" alt="Netflix" style="float:right;margin-left:10px;" />The blog is interesting for several reasons, most notably the candidness of the posts. In this post on <a href="http://blog.netflix.com/2007/07/hiding-movies-sequel.html">Movie Privacy</a>, for example, the team talks about a new feature whereby you can mark movies private, so as to not show them to your friends. Michael writes:  </p>
<blockquote><p>&#8220;So, in a rather unNetflix-like way, we&#8217;re just going to release it to Friends users in the next week or so. Let&#8217;s see if this finally allows you to connect to folks you know slightly less well (or maybe too well), and for whom you absolutely needed the ability to hide some titles. We&#8217;ve all read your comments and suggestions for how best to implement this. Trust me: this isn&#8217;t that. It&#8217;s not that we&#8217;re not hearing your suggestions, it&#8217;s just i was interested in getting this in front of you quickly.&#8221;</p></blockquote>
<p>This is really cool! Michael is obviously taking on a community manager type role here, announcing new features and asking for feedback. Saying that their new feature isn&#8217;t even the one that users were asking for is pretty interesting, too&#8230;how many design teams would do that? </p>
<p>Now, some of you might ask: &#8220;why would Netflix be so open about what they&#8217;re doing, even so far as to say how they don&#8217;t have it all figured out yet&#8221;. </p>
<p>All I can say is: <em>welcome to a new age of design</em>. An age where you work with your users to find out the best solution, and in doing so you not only solicit their feedback, but you show them you&#8217;re human and you care by actually having a conversation with them. While <a href="http://www.useit.com/alertbox/articles-not-blogs.html">some people don&#8217;t deign to have conversations and only want to be seen as an expert</a>, others are more humble and realize that it&#8217;s OK to actually have a conversation instead. Let people know you&#8217;re not perfect. In fact&#8230;you&#8217;ll notice that it&#8217;s quite endearing to be honest instead. </p>
<p>Now, if I had to guess who is going to create a better design, a design team that doesn&#8217;t have a public conversation and one that does&#8230;well the one that does is going to get a lot more feedback to go on while seeding their features and getting a LOT more attention in the process. It&#8217;s a riskier strategy, to be sure, but one with bigger potential payoff. </p>
<p>A fast rollout and quick iteration strategy is better than a slow rollout and slow iteration strategy. I wrote about this in: </p>
<p><a href="http://www.uie.com/articles/fast_iterations/">The Freedom of Fast Iterations: How Netflix Designs a Winning Web Site</a>. </p>
<p>After meeting some of the members of the design team and seeing them have this sort of conversation on their blog, I&#8217;m still very impressed with the way they work. They really seem to know that having a conversation with users is what great business is all about. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/designing-with-community-input-netflix-style/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>The 5 W&#8217;s of Social Software</title>
		<link>http://bokardo.com/archives/the-5-ws-of-social-software/</link>
		<comments>http://bokardo.com/archives/the-5-ws-of-social-software/#comments</comments>
		<pubDate>Thu, 07 Sep 2006 04:14:46 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Del.icio.us]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[MySpace]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=457</guid>
		<description><![CDATA[Social software has been around for a long time. Email, after all, is the canonical example. But it's been only recently that web designers as a whole have embraced it and really started innovating. We've got <a href="http://digg.com">social news aggregators</a>, <a href="http://wikipedia.org">social encyclopedias</a>, <a href="http://del.icio.us">social bookmarking</a>, <a href="http://facebook.com">social networking</a>, <a href="http://www.netflix.com">recommendation systems</a>, <a href="http://flickr.com/map/">social tagging</a>...all of these things add up to huge changes in the way we use the Web. Though some folks see it as nothing more than social networking, there are elements of social software being built into most software today. 

<strong>Who</strong>: Social software helps people by modeling their social lives online.

<strong>What</strong>: Social software is software that supports social activities.

<strong>Where</strong>: Social software is nearly everywhere. 

<strong>When</strong>: Now.

<strong>Why</strong>: Social software is important because that's the way that software is trending. ]]></description>
			<content:encoded><![CDATA[<p>Social software has been around for a long time. Email, after all, is the canonical example. But it&#8217;s been only recently that web designers as a whole have embraced it and really started innovating. We&#8217;ve got <a href="http://digg.com">social news aggregators</a>, <a href="http://wikipedia.org">social encyclopedias</a>, <a href="http://del.icio.us">social bookmarking</a>, <a href="http://facebook.com">social networking</a>, <a href="http://www.netflix.com">recommendation systems</a>, <a href="http://flickr.com/map/">social tagging</a>&#8230;all of these things add up to huge changes in the way we use the Web. Though some folks see it as nothing more than social networking, there are elements of social software being built into most software today. </p>
<p><strong>Who</strong>: Social software helps people by modeling their social lives online.</p>
<p><strong>What</strong>: Social software is software that supports social activities.</p>
<p><strong>Where</strong>: Social software is nearly everywhere. </p>
<p><strong>When</strong>: Now.</p>
<p><strong>Why</strong>: Social software is important because that&#8217;s the way that software is trending. </p>
<p>In addition, social software is teaching us lots of interesting things. It&#8217;s teaching us that the distinction between online and offline is barely there anymore, that people are super-comfortable on the Web (it wasn&#8217;t always this way&#8230;really!), that there are multiple ways to succeed in social software, and that there is room for lots of highly-trafficked services because people don&#8217;t mind subscribing to multiples. Also, with gaming, dating, and new media sites/software we&#8217;re seeing that there is huge money in it.  </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/the-5-ws-of-social-software/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Web 2.0 Talk &#8211; Leveraging the Network</title>
		<link>http://bokardo.com/archives/web-20-talk-leveraging-the-network/</link>
		<comments>http://bokardo.com/archives/web-20-talk-leveraging-the-network/#comments</comments>
		<pubDate>Wed, 22 Feb 2006 13:01:39 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Amazon]]></category>
		<category><![CDATA[Del.icio.us]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Long Tail]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Tagging]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[Yahoo]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/web-20-talk-leveraging-the-network/</guid>
		<description><![CDATA[Here's the slide deck for a talk I gave on Web 2.0 for the <a href="http://www.gbcacm.org/website/">Greater Boston Chapter of the ACM</a>, a non-profit educational and scientific society of computer professionals in the Boston area.

<a href="/talks/web20_leveraging_the_network.pdf">Web 2.0 - Leveraging the Network</a> (2.74 MB pdf)

In the talk I spoke about how Web 2.0 companies distinguish themselves by leveraging the network of which they are a part. <a href="http://www.britannica.com/">Brittanica</a>, for example, has had a web site for quite some time and were slow to leverage the network in any particular way. <a href="http://wikipedia.org">Wikipedia</a>, on the other hand, exists only because they used the available network to improve their contents communally. And Wikipedia, of course, is a much, much more popular site. ]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s the slide deck for a talk I gave on Web 2.0 for the <a href="http://www.gbcacm.org/website/">Greater Boston Chapter of the ACM</a>, a non-profit educational and scientific society of computer professionals in the Boston area.</p>
<p><a href="/talks/web20_leveraging_the_network.pdf">Web 2.0 &#8211; Leveraging the Network</a> (2.74 MB pdf)</p>
<p>In the talk I spoke about how Web 2.0 companies distinguish themselves by leveraging the network of which they are a part. <a href="http://www.britannica.com/">Brittanica</a>, for example, has had a web site for quite some time and were slow to leverage the network in any particular way. <a href="http://wikipedia.org">Wikipedia</a>, on the other hand, exists only because they used the available network to improve their contents communally. And Wikipedia, of course, is a much, much more popular site. </p>
<p>As in my last talk: <a href="http://bokardo.com/archives/podcast-of-web-20-talk/">Web 2.0 for the Rest of Us</a> (which includes a podcast), I started down the road toward Web 2.0 from the standpoint of those Web companies who have excelled: Google, Yahoo, Amazon, and eBay. They obviously know more about succeeding online than anybody else, and have become so successful so fast that we often take them for granted, even though they are barely a decade old. So, I find it particularly useful to ask: What makes them so special? What have they done that others haven&#8217;t? And I find myself coming back to the same answer over and over: <em>they know how to leverage the network</em>. From Google&#8217;s pagerank algorithm to the APIs of eBay and Amazon to the movie ratings on Yahoo, these companies know how to harness the collective activity and intelligence of people to make their services better. </p>
<p>For those who want only the quick and dirty (without the pretty pictures), here are the talking points: </p>
<ol>
<li>The home page is no longer the most important page on your site.</li>
<li>The information architecture that people use to find your content is, increasingly, not yours.</li>
<li>Each feature added to an application is more to think about &#8211; for everyone.</li>
<li>Folksonomies are a way for users to map their own, familiar vocabulary to your alien one.</li>
<li>Words are the currency of the Web. Spend the most time on your words.</li>
<li>Seducible moments are those increasingly rare moments when you can talk to your users in an appropriate context.</li>
<li>Recommendation systems are a forced move.</li>
<li>Users want control.</li>
<li>Users appreciate tools that help them make their own well-informed decisions.</li>
<li>The best software models human behavior.</li>
<li>Links model how users value content, and are only the start&#8230;</li>
<li>Sometimes it is easier to design for yourself than others.</li>
<li>There is always an opportunity for a better interface to data.</li>
<li>All things being equal, faster interfaces allow for more innovation.</li>
<li>Most people are willing to trade their personal information for good service.</li>
<li>As choices grow, so does the importance of learnability.</li>
<li>Redesigns are dead.</li>
<li>Network effects are rare, and killer.</li>
<li>Network effects work in the opposite way for teams building software.</li>
<li>Personal value precedes network value</li>
<li>People rarely do things for the â€œgood of the networkâ€</li>
<li>Del.icio.us, though providing very cool tagging features, is mostly about a single person remembering items for later.</li>
<li>â€œThe accretion of tiny marvels can numb us to the arrival of the stupendousâ€</li>
</ol>
<p>I would appreciate any and all feedback, as I&#8217;ll be giving this talk in the future and would like to improve upon it in any way that I can. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/web-20-talk-leveraging-the-network/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>The Most Important Statistic of them All</title>
		<link>http://bokardo.com/archives/the-most-important-statistic-of-them-all/</link>
		<comments>http://bokardo.com/archives/the-most-important-statistic-of-them-all/#comments</comments>
		<pubDate>Wed, 01 Feb 2006 13:55:07 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Attention]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=329</guid>
		<description><![CDATA[The most important statistic on the Web in the last year is the one delivered in a NYTimes article last week: <a href="http://www.nytimes.com/2006/01/23/technology/23recommend.html">Like This? You'll Hate That. (Not All Web Recommendations Are Welcome.)</a> [behind paywall :(  ].  The statistic involves media, technology, and the ever-increasing burden on our collective attention. 

Here it is: <strong>2/3 of <a href="http://www.netflix.com">Netflix</a> rentals come from recommendations</strong>.]]></description>
			<content:encoded><![CDATA[<p>The most important statistic on the Web in the last year is the one delivered in a NYTimes article last week: <a href="http://www.nytimes.com/2006/01/23/technology/23recommend.html">Like This? You&#8217;ll Hate That. (Not All Web Recommendations Are Welcome.)</a> [behind paywall <img src='http://bokardo.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />   ].  The statistic involves media, technology, and the ever-increasing burden on our collective attention. </p>
<p>Here it is: <strong>2/3 of <a href="http://www.netflix.com">Netflix</a> rentals come from recommendations</strong>.</p>
<p>Why is this so important? Because it helps to solve the big question of the moment: the dynamic between media and technology. Oops, I mean Media and Technology, in capital letters. </p>
<p>The solution that folks are stretching for is either one or the other. On the one hand you have <a href="http://publishing2.com/2006/01/29/bubble-20-is-a-bubble-in-media/">Scott Karp</a> suggesting that we need &#8220;trusted sources&#8221; and wonders whether media &#8220;brands&#8221; can &#8220;survive the chaos&#8221;.: </p>
<blockquote><p>&#8220;So letâ€™s focus on the user. What the user needs is help allocating a finite amount of attention. And the solution needs to be personal â€” perfectly tailored to each userâ€™s needs. The user needs a personal killer app.&#8221;</p>
<p>In a world of infinite choice, who will be the new â€œtrusted sourcesâ€ that <a href="http://paul.kedrosky.com/archives/002491.html">Paul (Kedrosky) refers to</a>? Can the notion of trusted media brands survive the chaos?&#8221;</p>
</blockquote>
<p>Karp sees what he calls &#8220;Old Media&#8221; going down in favor of a new, chaotic system in which it is hard to create a business model. He even suggests that the bubble we should be paying attention to is actually a bubble in media, not technology. I think he might be right about that. </p>
<p>And on the other hand you have <a href="http://susanmernit.blogspot.com/2006/01/quote-of-day_30.html">Susan Mernit</a>, who takes a more tools-oriented approach: </p>
<blockquote><p>&#8220;The talk about attention, personal media and new tools is dead on&#8211;but we&#8217;re making BIG assumptions about how users will change&#8211;and how long will it take for the remix generation to move to the center&#8211;that&#8217;s the question that can drive the economics of the market&#8211;plot the curve correctly and you win.&#8221;</p></blockquote>
<p>Indeed, I think both are right to focus on users, as <a href="http://blogs.msdn.com/alexbarn/archive/2006/01/29/518969.aspx">Alex Barnett</a> did in his reply. </p>
<p>But they&#8217;re both wrong, too, to think that Media with a capital M and changing people to technology are also part of what we should focus on. Imagine if all the media companies just up and died&#8230;who would complain? I&#8217;ll tell you a group of folks who wouldn&#8217;t: creators. Creators create whether or not there is a industry-sized business model. </p>
<p>Instead, media is something people want and technology is how they get it. </p>
<p>And <em>the best technology is that technology which models what people do already</em>. It&#8217;s not about changing people, or looking for media brands to carry us forward. I know that people who make money selling their own version of Media want to continue to do that, but for the most part real people <em>just don&#8217;t care</em>. Do I care whether this movie is distributed by Disney or Pixar or if Atlantic Media publishes the Atlantic Monthly? No, I just want the first season of <a href="http://abc.go.com/primetime/lost/">Lost</a> to pop off my recommendations queue (which <em>just happens</em> to be on Netflix).</p>
<p>Note that I&#8217;m not saying that there shouldn&#8217;t be a healthy communication between media outlets about how their stuff works. I&#8217;m just suggesting that users are already showing us the answer to the problems.</p>
<p>The media is people, folks. You got a blog, you&#8217;re the media. You gossip at the hairdresser, you&#8217;re the media. Just because someone sticks a capital M on Media and wants to make money from it doesn&#8217;t mean they&#8217;re more important than the recommendations you get from your loved ones, your family, or your friends. </p>
<p>Oh, did you know that Netflix models all of this? Yes, they call these people &#8220;friends&#8221; and &#8220;family&#8221;. Huh. </p>
<p>See the <a href="http://www.nytimes.com">NYTimes</a> over there? They&#8217;re a sinking part of the media. I tried to recommend Laurie Flynn&#8217;s fine article on recommendations to you in the first paragraph of this post but I can&#8217;t because you now have to PAY for it. My link doesn&#8217;t even work anymore! I got it FREE last week, and now it costs 4 bucks. Forget that media. Instead, I want access to what I had access to last week. With hyperlinks that don&#8217;t break. Ever.</p>
<p>So, what is the &#8220;personal killer app&#8221; that Karp is looking for? It&#8217;s recommendation systems, just like Netflix. They&#8217;re out modeling where YOU pay attention, what media YOU want, not the media THEY try to sell you. So the question is not &#8220;how can Media survive&#8221; or &#8220;how will people change?&#8221;. </p>
<p>The question is: &#8220;How can we use technology to model people&#8217;s wants, needs, desires?&#8221; </p>
<p>And you know what? Netflix knows this better than anyone. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/the-most-important-statistic-of-them-all/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

