<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Admit it, Social Software is goofing off at work</title>
	<atom:link href="http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/</link>
	<description></description>
	<pubDate>Fri, 22 Aug 2008 02:36:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Go Big Always - The most important things at work are Social Objects</title>
		<link>http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-11</link>
		<dc:creator>Go Big Always - The most important things at work are Social Objects</dc:creator>
		<pubDate>Sun, 20 Jan 2008 00:46:34 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-11</guid>
		<description>[...] As I&#8217;ve mentioned, the instant companies make social software available to its employees, it immediately becomes work focused (about productivity). E-mail is the easiest analogy. It&#8217;s (old) social software and it only works because everyone uses it. We all have work e-mail that helps us do our job. Obviously, email is not close to a comprehensive enough productivity tool so we bebop in and around it as needed. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] As I&#8217;ve mentioned, the instant companies make social software available to its employees, it immediately becomes work focused (about productivity). E-mail is the easiest analogy. It&#8217;s (old) social software and it only works because everyone uses it. We all have work e-mail that helps us do our job. Obviously, email is not close to a comprehensive enough productivity tool so we bebop in and around it as needed. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sam</title>
		<link>http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-9</link>
		<dc:creator>sam</dc:creator>
		<pubDate>Thu, 17 Jan 2008 22:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-9</guid>
		<description>eStatusreports, ack! Yeah, that would be pretty horrid. No doubt the natural adoption phases will play their course and the luddites will catch up while the early adopters find a new cul-de-sac to park their cars. In the meantime, we'll just have to help companies talk about the values of these tools vs talking about the tools.</description>
		<content:encoded><![CDATA[<p>eStatusreports, ack! Yeah, that would be pretty horrid. No doubt the natural adoption phases will play their course and the luddites will catch up while the early adopters find a new cul-de-sac to park their cars. In the meantime, we&#8217;ll just have to help companies talk about the values of these tools vs talking about the tools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Kistner</title>
		<link>http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-8</link>
		<dc:creator>Justin Kistner</dc:creator>
		<pubDate>Thu, 17 Jan 2008 19:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-8</guid>
		<description>&lt;blockquote&gt;If the button said, “status report” instead of “blog,” people would go, “oh!” click on it and get started.&lt;/blockquote&gt;

That's a great way of putting it. I've been helping my father with his blog for about a year and he still complains about the word blog. He feels like the language surrounding "blogs" excludes his generation from participating. I wonder if it changing the language to stuff like eStatusreports would help? I think it would ease the transition for those unfamiliar with the tools, but I really feel like they just need to catch up. Understanding a blog post in its essence is a requirement if one wants to predict future applications for the communication format. I think the resistance to the social nomenclature will dissipate once the Luddites see the dust cloud from those who have caught on. I almost don't want to help them because there is so much fresh ground without competitors.</description>
		<content:encoded><![CDATA[<blockquote><p>If the button said, “status report” instead of “blog,” people would go, “oh!” click on it and get started.</p></blockquote>
<p>That&#8217;s a great way of putting it. I&#8217;ve been helping my father with his blog for about a year and he still complains about the word blog. He feels like the language surrounding &#8220;blogs&#8221; excludes his generation from participating. I wonder if it changing the language to stuff like eStatusreports would help? I think it would ease the transition for those unfamiliar with the tools, but I really feel like they just need to catch up. Understanding a blog post in its essence is a requirement if one wants to predict future applications for the communication format. I think the resistance to the social nomenclature will dissipate once the Luddites see the dust cloud from those who have caught on. I almost don&#8217;t want to help them because there is so much fresh ground without competitors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chriskalani</title>
		<link>http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-7</link>
		<dc:creator>chriskalani</dc:creator>
		<pubDate>Thu, 17 Jan 2008 18:57:26 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/admit-it-social-software-is-goofing-off-at-work/#comment-7</guid>
		<description>Anyone who thinks it doesn't help get things done obviously hasn't used the right application.</description>
		<content:encoded><![CDATA[<p>Anyone who thinks it doesn&#8217;t help get things done obviously hasn&#8217;t used the right application.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.250 seconds -->
