<?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: Successful intranets move beyond IT and communications</title>
	<atom:link href="http://jboye.com/blogpost/successful-intranets-move-beyond-it-communications/feed/" rel="self" type="application/rss+xml" />
	<link>http://jboye.com/blogpost/successful-intranets-move-beyond-it-communications/</link>
	<description>The international community for web and intranet professionals</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:45:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Kelly Swanson - Intranet/SEO Architect</title>
		<link>http://jboye.com/blogpost/successful-intranets-move-beyond-it-communications/comment-page-1/#comment-4149</link>
		<dc:creator>Kelly Swanson - Intranet/SEO Architect</dc:creator>
		<pubDate>Fri, 09 Jul 2010 16:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2656#comment-4149</guid>
		<description>Our Intranet is run by IT because they should. IT backs it up, restores, creates users, programs, fixes mistakes, and upgrades the servers. But, each department has a role for their sections. Like a branch, each department is independent so they can have total ownership and have a say in their offering. The streaming information area on the front page and department page updates all staff to those department postings and offerings. We have 23 departments that fuel our intranet. Placing it primarily in the hands of one department or a small few that have say over the internal communications of a whole company is a mistake. HR doesn&#039;t know what Facilities is doing nor do they care. Finance doesn&#039;t communicate its changes to the collections department; and training doesn’t consort for permission to post class listings. Each department has a job to do, and from the top down open communication must take place, but if taught, each department will know what to do. If leveraged they will be allowed to make success for the organization. Micro and Macro managing of a company intranet leads to problems. Free communication is key to growth and harmony in the corporate ecosystem. Control will get you so far then it fails. An intranet is an integral part of that cohesiveness.</description>
		<content:encoded><![CDATA[<p>Our Intranet is run by IT because they should. IT backs it up, restores, creates users, programs, fixes mistakes, and upgrades the servers. But, each department has a role for their sections. Like a branch, each department is independent so they can have total ownership and have a say in their offering. The streaming information area on the front page and department page updates all staff to those department postings and offerings. We have 23 departments that fuel our intranet. Placing it primarily in the hands of one department or a small few that have say over the internal communications of a whole company is a mistake. HR doesn&#8217;t know what Facilities is doing nor do they care. Finance doesn&#8217;t communicate its changes to the collections department; and training doesn’t consort for permission to post class listings. Each department has a job to do, and from the top down open communication must take place, but if taught, each department will know what to do. If leveraged they will be allowed to make success for the organization. Micro and Macro managing of a company intranet leads to problems. Free communication is key to growth and harmony in the corporate ecosystem. Control will get you so far then it fails. An intranet is an integral part of that cohesiveness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: La coda lunga dell&#8217;attività in intranet &#124; Intranet Management</title>
		<link>http://jboye.com/blogpost/successful-intranets-move-beyond-it-communications/comment-page-1/#comment-2093</link>
		<dc:creator>La coda lunga dell&#8217;attività in intranet &#124; Intranet Management</dc:creator>
		<pubDate>Mon, 27 Jul 2009 07:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2656#comment-2093</guid>
		<description>[...] Il tema è quello della distribuzione delle informazioni in intranet e anche secondo J. Boyle il &#8220;grosso&#8221; dell&#8217;attività avviene nella coda lunga. [...]</description>
		<content:encoded><![CDATA[<p>[...] Il tema è quello della distribuzione delle informazioni in intranet e anche secondo J. Boyle il &#8220;grosso&#8221; dell&#8217;attività avviene nella coda lunga. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jane McConnell</title>
		<link>http://jboye.com/blogpost/successful-intranets-move-beyond-it-communications/comment-page-1/#comment-1986</link>
		<dc:creator>Jane McConnell</dc:creator>
		<pubDate>Wed, 01 Jul 2009 06:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2656#comment-1986</guid>
		<description>A sign of a mature intranet environment is where ownership of the intranet is a natural extension of the scope and accountability of the person or department in general. 
This applies to publishing responsibilities as well as to top level strategic ownership.
I dream of the day when the intranet will no longer be handled as something different, something with its own governance to define, but simply business as usual.</description>
		<content:encoded><![CDATA[<p>A sign of a mature intranet environment is where ownership of the intranet is a natural extension of the scope and accountability of the person or department in general.<br />
This applies to publishing responsibilities as well as to top level strategic ownership.<br />
I dream of the day when the intranet will no longer be handled as something different, something with its own governance to define, but simply business as usual.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

