<?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>Backdrifter &#187; office</title>
	<atom:link href="http://www.backdrifter.com/tags/office/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.backdrifter.com</link>
	<description>The personal site of Jared Hanson</description>
	<lastBuildDate>Tue, 22 Jun 2010 22:16:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Google Acquires JotSpot</title>
		<link>http://www.backdrifter.com/2006/11/01/google-acquires-jotspot/</link>
		<comments>http://www.backdrifter.com/2006/11/01/google-acquires-jotspot/#comments</comments>
		<pubDate>Thu, 02 Nov 2006 06:18:30 +0000</pubDate>
		<dc:creator>Jared Hanson</dc:creator>
				<category><![CDATA[google]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.backdrifter.com/2006/11/01/google-acquires-jotspot/</guid>
		<description><![CDATA[Yesterday, Google announced their acquisition of JotSpot, a company that developed wiki applications.  Wikis are collaborative websites that a group of people can edit and update with new information.  This acquisition is another sign of Google&#8217;s office intentions, and reveals in greater detail that collaboration is their focus.
Read/WriteWeb has a wealth of information [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday, <a href="http://www.google.com/">Google</a> announced their acquisition of <a href="http://www.jot.com/">JotSpot</a>, a company that developed wiki applications.  Wikis are collaborative websites that a group of people can edit and update with new information.  This acquisition is another sign of Google&#8217;s office intentions, and reveals in greater detail that collaboration is their focus.</p>
<p>Read/WriteWeb has a <a href="http://www.readwriteweb.com/archives/google_acquires_jotspot.php">wealth</a> of information about JotSpot, past and present.  JotSpot&#8217;s product and engineering strengths will fit nicely with various Google offerings, including <a href="http://docs.google.com/">Docs &amp; Spreadsheets</a> and <a href="http://groups.google.com/">Groups</a>.  Of course, the future implications are what make this move interesting.</p>
<p>Google is making <a href="http://googleenterprise.blogspot.com/2006/10/wikis-for-work_31.html">designs</a> for <a href="http://www.google.com/enterprise/">enterprise</a> software, pushing further into <a href="http://www.microsoft.com/">Microsoft</a>&#8217;s territory.  Niall Kennedy <a href="http://www.niallkennedy.com/blog/archives/2006/10/google-collaboration-server.html">presents</a> his theory on how the pieces are falling into place, and it appears compelling.</p>
<p><span id="more-14"></span></p>
<p>Thus far, Google&#8217;s enterprise strategy has consisted of appliances and hosted services.  Appliances, like <a href="http://www.google.com/enterprise/mini/index.html">Google Mini</a>, can be deployed on a company&#8217;s private network, indexing internal documents.  Hosted services, such as <a href="http://www.google.com/enterprise/apps/index.html">Apps for Your Domain</a> are prime candidates for transition to an appliance as well.</p>
<p>Another component is the software installed on individual computers, <a href="http://desktop.google.com/">Google Desktop</a> and <a href="http://www.google.com/talk/">Google Talk</a> being two indispensable applications.  A bit of integration, utilizing standard protocols like <a href="http://www.xmpp.org/">XMPP</a>, could link everything together.  Data could transition seamlessly from the desktop, to the internally deployed appliances, and out to the Google-powered cloud.  Wouldn&#8217;t <a href="http://www.backdrifter.com/2006/10/15/office-201/">that</a> be interesting?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.backdrifter.com/2006/11/01/google-acquires-jotspot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Office 2.0.1</title>
		<link>http://www.backdrifter.com/2006/10/15/office-201/</link>
		<comments>http://www.backdrifter.com/2006/10/15/office-201/#comments</comments>
		<pubDate>Sun, 15 Oct 2006 18:27:35 +0000</pubDate>
		<dc:creator>Jared Hanson</dc:creator>
				<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.backdrifter.com/2006/10/15/office-201/</guid>
		<description><![CDATA[As a follow on to my entry on the opening day of the Office 2.0 Conference, I thought I&#8217;d take a look at the challenges facing both office 2.0 applications and the enterprises seeking to adopt 2.0 methodologies.  For background, I recommend reading the post show analysis from IT&#124;Redux, where Ismael Ghalimi presents a [...]]]></description>
			<content:encoded><![CDATA[<p>As a follow on to my <a href="http://www.backdrifter.com/2006/10/11/office-20/">entry</a> on the opening day of the <a href="http://www.office20con.com/">Office 2.0 Conference</a>, I thought I&#8217;d take a look at the challenges facing both office 2.0 applications and the enterprises seeking to adopt 2.0 methodologies.  For background, I recommend reading the post show <a href="http://itredux.com/blog/2006/10/14/what-i-learned-at-the-office-20-conference/">analysis</a> from IT|Redux, where Ismael Ghalimi presents a rundown of what occurred and offers worthwhile insights.</p>
<p><span id="more-9"></span></p>
<p>Office 2.0 is currently targeting individual users and small businesses.  Enterprises have demanding reliability, scalability, and security requirements that aren&#8217;t currently being adequately addressed by office 2.0 applications.  I believe that the hosted model seen in many web applications is a primary cause of not meeting these requirements.</p>
<p>As things move forward, I expect it will become more and more common for corporations to adopt a hybrid approach of both hosted services and internally deployed applications.  Web protocols such as SOAP and REST over HTTP will serve as the foundation that allows the hybrid approach to be integrated.</p>
<p>The catalyst for this change will come as mobile access to information is demanded by employees.  Mobile phones, such a the various <a href="http://www.blackberry.com/">BlackBerry</a> models, are important tools for staying connected while away from the office.  The sheer variety of mobile devices means that web languages like HTML and JavaScript become the dominant client-side application platform.</p>
<p>The hybrid hosted-internal architecture will allow enterprises to meet their security and reliablilty needs, while allowing workers to access and manage data as they move on and off the corporate network.  The standards-based technologies that power this movement will force vendors to abandon proprietary stacks and adopt open interfaces.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.backdrifter.com/2006/10/15/office-201/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Office 2.0</title>
		<link>http://www.backdrifter.com/2006/10/11/office-20/</link>
		<comments>http://www.backdrifter.com/2006/10/11/office-20/#comments</comments>
		<pubDate>Thu, 12 Oct 2006 05:46:43 +0000</pubDate>
		<dc:creator>Jared Hanson</dc:creator>
				<category><![CDATA[google]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.backdrifter.com/2006/10/11/office-20/</guid>
		<description><![CDATA[On the opening day of the Office 2.0 Conference, Google decided to merge Writely and Google Spreadsheets into Google Docs &#38; Spreadsheets.  Google&#8217;s been playing it coy with their office-suite plans, but recent maneuverings make their intentions clear.
(Aside: Is it just me, or is Google second only to Microsoft in poor product naming?  [...]]]></description>
			<content:encoded><![CDATA[<p>On the opening day of the <a href="http://www.office20con.com/">Office 2.0 Conference</a>, Google decided to merge Writely and Google Spreadsheets into <a href="http://docs.google.com/">Google Docs &amp; Spreadsheets</a>.  Google&#8217;s been playing it coy with their office-suite plans, but recent maneuverings make their intentions clear.</p>
<p>(Aside: Is it just me, or is Google second only to Microsoft in poor product naming?  I&#8217;m not here to criticize brand strategies, but Writely was a fantastic name.  Google prefers Google This and Google That, and when <a href="http://video.google.com/">those</a> don&#8217;t work out, they go and spend $1.65 billion on <a href="http://www.youtube.com/">YouTube</a>, a site in which a good portion of the value lies in the brand.  I don&#8217;t get it.)</p>
<p>Both Om Malik and Steve Gillmor are blogging the conference.  Om <a href="http://software.gigaom.com/2006/10/11/office-20-the-conference-the-concept/">claims</a> the office 2.0 idea need refinement, and has to move away from away from traditional notions.  Gillmor, as he regularly does, recognizes what is not being said and <a href="http://gesturelab.com/?p=33">points</a> in the direction things are moving.</p>
<p><span id="more-7"></span></p>
<p>The typical corporation is heavily wrapped up and invested in &#8220;process management&#8221; and &#8220;workflow solutions.&#8221;  These solutions often have their roots in purchasing decisions made a decade ago, when a corporate network was just that.  Data is siloed up in proprietary databases with arcane access restrictions, more often that not a hindrance to modern &#8220;workflow.&#8221;</p>
<p>Today, the Internet has allowed Google and others to bring communication and collaboration tools directly to the individual.  Documents no longer have to be copied, or locked, or hand merged.  In a networked world, they can be linked to and edited by multiple people.  They can be chat rooms, where changes are discussed before being committed.  The documents are the collaboration.  They are the workflow.</p>
<p>It&#8217;s the difference between centralized and decentralized thinking.  Corporations and their enterprise software vendors have a hard time getting beyond rigid, restricted processes.  They need to change their mindset, and quickly.  Better, more efficient tools are being piped directly to every employee&#8217;s desk from beyond the corporate firewall.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.backdrifter.com/2006/10/11/office-20/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
