<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why your company should ban Facebook</title>
	<atom:link href="http://www.hallam.biz/blog/2010/02/why-your-company-should-ban-facebook.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.hallam.biz/blog/2010/02/why-your-company-should-ban-facebook.html</link>
	<description>Internet marketing training and consultancy for small businesses in the UK</description>
	<lastBuildDate>Mon, 06 Sep 2010 13:43:59 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Spencer</title>
		<link>http://www.hallam.biz/blog/2010/02/why-your-company-should-ban-facebook.html/comment-page-1#comment-1881</link>
		<dc:creator>Dave Spencer</dc:creator>
		<pubDate>Fri, 26 Feb 2010 10:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.hallam.biz/?p=2585#comment-1881</guid>
		<description>It&#039;s easy to see the risks to organisations and you hear all the time about instances where people are being sued or that someone mucked up and posted something they shouldn&#039;t have, take the Vodafone incident as a prime example. However, wouldn&#039;t a better policy be to educate people? As time and time again, something comes along, organisations try to impose restrictions and people always find a way around it. Engaging with your workforce and educating them what you can and can&#039;t do is usually a more productive process and generally leads to greater adoption of policies and practices than imposing an outright ban, when they most likely haven&#039;t done anything to warrant it....</description>
		<content:encoded><![CDATA[<p>It&#8217;s easy to see the risks to organisations and you hear all the time about instances where people are being sued or that someone mucked up and posted something they shouldn&#8217;t have, take the Vodafone incident as a prime example. However, wouldn&#8217;t a better policy be to educate people? As time and time again, something comes along, organisations try to impose restrictions and people always find a way around it. Engaging with your workforce and educating them what you can and can&#8217;t do is usually a more productive process and generally leads to greater adoption of policies and practices than imposing an outright ban, when they most likely haven&#8217;t done anything to warrant it&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Proctor</title>
		<link>http://www.hallam.biz/blog/2010/02/why-your-company-should-ban-facebook.html/comment-page-1#comment-1861</link>
		<dc:creator>Ben Proctor</dc:creator>
		<pubDate>Thu, 25 Feb 2010 09:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.hallam.biz/?p=2585#comment-1861</guid>
		<description>I agree absolutely with the risks that you identify and banning facebook would certainly be one way to reduce those risks. I don&#039;t think it will be sustainable in the medium term because social media is starting to permeate the working space. In, say, five years banning access to social networking sites will be as bizarre as banning e-mail. The challenge for organisations is to find a way to move from where we are now to that point while managing the risks that your identify above.</description>
		<content:encoded><![CDATA[<p>I agree absolutely with the risks that you identify and banning facebook would certainly be one way to reduce those risks. I don&#8217;t think it will be sustainable in the medium term because social media is starting to permeate the working space. In, say, five years banning access to social networking sites will be as bizarre as banning e-mail. The challenge for organisations is to find a way to move from where we are now to that point while managing the risks that your identify above.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
