<?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>jukka.niiranen.eu &#187; collaboration</title>
	<atom:link href="http://niiranen.eu/jukka/tag/collaboration/feed/" rel="self" type="application/rss+xml" />
	<link>http://niiranen.eu/jukka</link>
	<description>Welcome to my world</description>
	<lastBuildDate>Sun, 29 Aug 2010 17:37:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Lessons from Google Wave</title>
		<link>http://niiranen.eu/jukka/2010/08/lessons-from-google-wave/</link>
		<comments>http://niiranen.eu/jukka/2010/08/lessons-from-google-wave/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 07:01:32 +0000</pubDate>
		<dc:creator>Jukka</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[SocialMedia]]></category>

		<guid isPermaLink="false">http://niiranen.eu/jukka/?p=843</guid>
		<description><![CDATA[It was announced yesterday (on August 4th) that Google would no longer develop Google Wave. In other words, R.I.P. Google Wave. Let&#8217;s have a look at some of the reasons why Wave suffered this fate and what Google might have learned from it. Google Wave was an island There was no easy nor logical way [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://niiranen.eu/jukka/wp-content/uploads/2010/08/Google_Wave_splash.jpg" rel="lightbox[843]"><img class="alignright size-full wp-image-846" title="Google_Wave_splash" src="http://niiranen.eu/jukka/wp-content/uploads/2010/08/Google_Wave_splash.jpg" alt="" width="243" height="238" /></a>It was <a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html" target="_blank">announced</a> yesterday (on August 4th) that Google would no longer develop Google Wave. In other words, R.I.P. Google Wave. Let&#8217;s have a look at some of the reasons why Wave suffered this fate and what Google might have learned from it.</p>
<h2>Google Wave was an island</h2>
<p>There was no easy nor logical way to incorporate Wave into your ordinary workflow. If you weren&#8217;t opening wave.google.com on your browser, you were not &#8220;on the wave&#8221;. The most critical thing was that even though it looked almost exactly like a webmail client, and your user account had the form of<em> username@googlewave.com</em>, there was no email integration whatsoever. It&#8217;s bad enough that you couldn&#8217;t subscribe to any Wave updates to your inbox (later this <a href="http://mashable.com/2010/03/04/google-wave-email-notifications/" target="_blank">feature was added</a> without much fanfare), but the fact that a company hosting one of the largest email services in the world goes and assigns users pseudo email addresses you can&#8217;t send messages to is something that <a title="Everything is still email" href="http://niiranen.eu/jukka/2010/02/everything-is-still-email/" target="_blank">still boggles my mind</a>. Ok, I understand that Google Wave was supposed to be something beyond email, but even emails could be printed on paper. How about some backward compatibility, eh?</p>
<h2>Google Wave did not solve a specific problem</h2>
<p>Most people just couldn&#8217;t quite figure out what exactly they were supposed to use Wave for. Pretty much everybody saw the potential of it for something useful, but were they able to picture themselves as a user in a specific use case where Wave was a natural fit? Let&#8217;s face it: there&#8217;s no point in releasing a technology demo and expect people to start using it straight away. What in fact was missing was the real <em>product</em>. Wave gave us the tools, but it would have probably taken an ecosystem around it to turn these tools into products that people could utilise for solving a specific problem (which Google did try to encourage through it&#8217;s API and federation protocol offering). Yes, collaboration challenges tend to be universal, but that doesn&#8217;t mean you could simply throw technology at them and expect people to take it from there.<br />
<span id="more-843"></span></p>
<h2>Google Wave was not social</h2>
<p><img class="alignright size-full wp-image-849" title="Google_Wave_invite" src="http://niiranen.eu/jukka/wp-content/uploads/2010/08/Google_Wave_invite.jpg" alt="" width="238" height="182" />Given that the beta program with its invitation only approach initially stirred up quite a lot of interest towards the service, with invitations sold on <a href="http://mashable.com/2009/09/30/google-wave-invite/" target="_blank">eBay for $70</a>, the approach quickly turned on its head. Let&#8217;s say that there were several groups of people in your company that were experimenting with Wave. How could you identify these particular people that were potential co-wavers and collaborators? Not through the service you wouldn&#8217;t. It happened on the corridors and water coolers, or in long email threads (sigh) circulating around the office. Come to think of it, for a company revolving around the concept of search, Google&#8217;s products can be incredibly hard to find. Just compare the findability of users and information on Twitter vs. Google Buzz.</p>
<h2>Google Wave was developed by&#8230; Google</h2>
<p>Huh? Why is that a bad thing? Well, let me explain. Google knows us all, but we still have no effective way of knowing each other through Google. This lack of the social dimension is perhaps the most significant barrier currently limiting Google&#8217;s growth beyond &#8220;just&#8221; indexing all the world&#8217;s data. 10 years ago that must have seemed like the ultimate goal you could have within the scope of Internet. Ever since the &#8216;net has evolved from a collection of documents to a platform for human interaction, that goal no longer sounds like the Holy Grail. Wave, just like Buzz or Orkut, relies on tapping into the social behaviour between people, not just a lone swordsman searching for a piece of information in the sea of data. Designing services to this new breed of customers requires a new way of thinking, which Google is only in the process of learning. Read <a href="http://ifindkarma.posterous.com/pandas-and-lobsters-why-google-cannot-build-s" target="_blank">this</a> excellent post for further analysis on <a href="http://ifindkarma.posterous.com/pandas-and-lobsters-why-google-cannot-build-s" target="_blank">why Google cannot build social applications</a>.</p>
<p>Just because the &#8220;surf&#8217;s up&#8221; for Wave, doesn&#8217;t mean the game&#8217;s over for Google&#8217;s initiative to change how people collaborate on information online. On the contrary: because they keep on trying, they can eventually succeed. Obviously there&#8217;s no other path for the corporation that&#8217;s built its product success on the concept of perpetual beta. I&#8217;ll hold up my board and wait for the next big wave.</p>
]]></content:encoded>
			<wfw:commentRss>http://niiranen.eu/jukka/2010/08/lessons-from-google-wave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Everything is still email</title>
		<link>http://niiranen.eu/jukka/2010/02/everything-is-still-email/</link>
		<comments>http://niiranen.eu/jukka/2010/02/everything-is-still-email/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 21:15:47 +0000</pubDate>
		<dc:creator>Jukka</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://niiranen.eu/jukka/?p=508</guid>
		<description><![CDATA[A few weeks back I discovered Posterous, which is a tumblelog service (think Tumblr) built around the concept of email as the UI. Want to create an account? Send an email to post@posterous.com and you&#8217;ll get one. Want to create a blog post? Write it in an email and send it again to post@posterous.com and [...]]]></description>
			<content:encoded><![CDATA[<p>A few weeks back I discovered <a href="http://jukkan.posterous.com/" target="_blank">Posterous</a>, which is a tumblelog service (think <a href="http://www.tumblr.com" target="_blank">Tumblr</a>) built around the concept of email as the UI. Want to create an account? Send an email to post@posterous.com and you&#8217;ll get one. Want to create a blog post? Write it in an email and send it again to post@posterous.com and it&#8217;ll get published. Sure, you can post stuff through the web interface, if you really must. But the service makes a serious effort in trying to do the best job possible in figuring out how the contents of an email message should be rendered, in terms of attached images, youtube links and the likes. Even with it&#8217;s shortcomings, I feel the user experience is actually superior to my long time favourite blogging platform WordPress. Forget about tweaking your posts, just email &#8216;em.</p>
<p><a href="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Posterous.jpg" rel="lightbox[508]"><img class="aligncenter size-full wp-image-510" title="Posterous" src="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Posterous.jpg" alt="" width="480" height="90" /></a></p>
<p>Facebook has such bad usability all-around that nowadays I tend to only navigate to Bejeweled Blitz and follow status updates throug <a href="http://www.tweetdeck.com/" target="_blank">TweetDeck</a>. When do I then go to Facebook? When I get an email from the service, telling me that someone has commented my stuff or sent me a message. <a title="TechCrunch: Facebook's Project Titan: A Full Featured Webmail Product" href="http://techcrunch.com/2010/02/05/facebooks-project-titan-a-full-featured-webmail-product/" target="_blank">Rumor has it</a> that Facebook is in fact working on developing a full webmail service, where you could receive messages to your <em>vanityurl</em>@facebook.com.</p>
<p><a href="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Facebook.jpg" rel="lightbox[508]"><img class="aligncenter size-full wp-image-512" title="Facebook" src="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Facebook.jpg" alt="" width="480" height="167" /></a></p>
<p>Google is the current king of email with Gmail. Nothing comes close, except the threat of people&#8217;s increasing usage of media other than traditional email for their messaging needs. Google isn&#8217;t standing still, instead they are trying to incorporate more and more social features into Gmail, like the recent announcement of <a href="http://www.google.com/buzz" target="_blank">Google Buzz</a>. And where does the Buzz exist in terms of UI? In Gmail. Where do the comments to your status updates come to? Your inbox. ¡Viva la email revolución!</p>
<p><a href="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Google.jpg" rel="lightbox[508]"><img class="alignnone size-full wp-image-515" title="Google" src="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Google.jpg" alt="" width="480" height="273" /></a></p>
<p>Google Wave is trying to go beyond email, but the current preview version (notice: not even beta!) has one severe limitation: it doesn&#8217;t act like webmail, meaning you can&#8217;t actually send emails to your @wave.com address. Yeah, what do you call and @address that&#8217;s not an email address? It&#8217;s hard to see the adoption rate picking up until Wave embraces email.</p>
<p><a href="http://geekandpoke.typepad.com/geekandpoke/"><img class="alignright size-full wp-image-519" title="Geekandpoke" src="http://niiranen.eu/jukka/wp-content/uploads/2010/02/Geekandpoke.jpg" alt="" width="222" height="216" /></a>Numerous <a title="Wikipedia: Enterprise social software" href="http://www.google.com/url?sa=t&amp;source=web&amp;ct=res&amp;cd=3&amp;ved=0CFIQFjAC&amp;url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FEnterprise_social_software&amp;ei=V89xS7KPLpvB-Qb_h5HUCQ&amp;usg=AFQjCNE5TuKHq7s-Oz-kYPrLwU9ccO6WDA&amp;sig2=xFwOMJ0s24LAlWhQdWmccw" target="_blank">Enterprise 2.0</a> application providers are keeping themselves busy by building wonderful collaboration environments for office workers, to make them more productive in their daily tasks and teamwork. But still they can&#8217;t come anywhere near email. Everyone uses it and it is the lowest common denominator that every information worker loves to hate, but couldn&#8217;t live without. As Jacob Uckelson <a title="The Collaboration Challenges of SaaS in the Enterprise" href="http://www.ctoedge.com/content/collaboration-challenges-saas-enterprise" target="_blank">writes</a> about the enterprise collaboration paradox:</p>
<blockquote><p>So even though almost every enterprise has special purpose solutions available for collaboration and process management, good old e-mail always ends up being the primary method for both collaboration and processes in the enterprise. This can be called the &#8220;enterprise collaboration and process paradox,&#8221; and is the &#8220;dirty little secret&#8221; of both collaboration and process execution in the enterprise. Realistically, there doesn&#8217;t seem to be any way to displace e-mail as the king of collaboration and processes</p></blockquote>
<p>Everybody used to be stressed about the growing amount of spam email a few years back. Today the rate of spam that avoids my junk email filters is probably 0,001%. Email used to be confined into desktop applications like Eudora or the omnipresent Outlook. Now it&#8217;s in the browser and in your mobile phone, meaning in practice everywhere.</p>
<p>Email has come a long way and it&#8217;s not going away anytime soon. It&#8217;s more likely that we&#8217;ll just be getting more of it.</p>
]]></content:encoded>
			<wfw:commentRss>http://niiranen.eu/jukka/2010/02/everything-is-still-email/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
