<?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>YDOP &#187; document management</title>
	<atom:link href="http://www.ydop.com/tag/document-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ydop.com</link>
	<description>Insights for the next click</description>
	<lastBuildDate>Wed, 23 Nov 2011 21:37:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Google Wave will change business</title>
		<link>http://www.ydop.com/google-wave-change-business/</link>
		<comments>http://www.ydop.com/google-wave-change-business/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 14:35:27 +0000</pubDate>
		<dc:creator>Daniel Klotz</dc:creator>
				<category><![CDATA[Social Media]]></category>
		<category><![CDATA[document management]]></category>
		<category><![CDATA[e-mail]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Wave]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[project management]]></category>

		<guid isPermaLink="false">http://ydop.com/?p=793</guid>
		<description><![CDATA[Google Wave will impact project management, document management, wikis, and message boards. It will also remedy the nonsocial nature of e-mail.]]></description>
			<content:encoded><![CDATA[<p>At first (and, OK, for weeks after that), Google Wave is hard to understand. It&#8217;s difficult to figure out how to use Wave, and it&#8217;s even harder to imagine how it might be truly useful.<br />
<span id="more-793"></span></p>
<div id="attachment_803" class="wp-caption alignright" style="width: 220px"><a href="http://ydop.com/wp-content/uploads/2009/12/google-wave.jpg"><img class="size-full wp-image-803 " title="Google Wave logo" src="http://ydop.com/wp-content/uploads/2009/12/google-wave.jpg" alt="Google Wave" width="210" height="210" /></a><p class="wp-caption-text">Google Wave</p></div>
<p>At last night&#8217;s <a title="Lancaster technology network" href="http://www.meetup.com/New-Tech-Meetup-of-Central-PA/">Central PA New Tech Meetup</a>, I had the pleasure of facilitating a conversation about Google&#8217;s latest product with the brain trust of techies in the room, along with the meetup&#8217;s organizer, John Caddell. My goal was to get a feel from this group of fellow early adopters about what they like/dislike about Wave so far, and about what they see as the future implications of the technology.</p>
<p>Here are my takeaways on the question, Will Google Wave affect the way business is done?</p>
<p><strong>Google Wave will change project management.</strong> It&#8217;s clear that Wave is superbly suited for small project teams who need to collaborate on projects, often in real-time.</p>
<p><strong>Google Wave will change how we think about documents.</strong> Right now the paradigm within business is that a document is a document is a document. An after-action review, a set of product specs, an informal memo, and a legal contract are created, versioned, and stored in similar ways. The current way of thinking about, creating, and storing documents makes sense for things like contracts and records that are <em>meant</em> to become static. But that way of thinking is inadequate for documents about things like best practices, bios and CVs, and marketing research. Wave will prompt business to differentiate between &#8220;static documents&#8221; and &#8220;living documents.&#8221;</p>
<p><strong>Google wave is the wiki for the rest of us.</strong> Enterprises currently attempt to create &#8220;living documents&#8221; (and a management/storage system for them) by setting up internal wikis. The problem is, getting a wiki up and running—and more importantly, getting people to actually <em>use</em> it—is difficult at best. Compared to a wiki, Google Wave is fun. Even if Wave is not completely intuitive and simple, it&#8217;s more intuitive and simple than a wiki. The impact of Google Wave on knowledge management should not be underestimated.</p>
<p><strong>Google Wave reinvents the message board.</strong> Message boards, forums, and BBs have been falling out of favor throughout the past decade. They&#8217;re most alive in the tech community, but adoption within other sectors has fallen off. The similarity of a wave to a message board thread is close enough that Google Wave may make a good modern-day replacement for phpBB and other forum software.</p>
<p><strong>Google Wave makes messages more social.</strong> Including someone new in a wave is easy and doesn&#8217;t require introductions, unlike adding someone to a conversation taking place between multiple people via e-mail. Wave also allows newcomers to the conversation to catch up by watching how the wave evolved over time, using the (really cool) &#8220;playback&#8221; feature. What&#8217;s more, if you find yourself in a wave with a participant you weren&#8217;t connected with before, adding them to your contacts (and thus, to your personal network) is a breeze.</p>
<p>What do you think? Are these predictions pie in the sky? Are there other ways you see Wave impacting business processes in the near future?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ydop.com/google-wave-change-business/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

