<?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: Migrating to a new intranet – how do you support the content owners?</title>
	<atom:link href="http://www.jboye.com/blogpost/migrating-to-a-new-intranet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jboye.com/blogpost/migrating-to-a-new-intranet/</link>
	<description>J. Boye Blog</description>
	<lastBuildDate>Wed, 28 Jul 2010 23:49:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Greg kerchhoff</title>
		<link>http://www.jboye.com/blogpost/migrating-to-a-new-intranet/comment-page-1/#comment-3815</link>
		<dc:creator>Greg kerchhoff</dc:creator>
		<pubDate>Fri, 26 Feb 2010 11:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=5270#comment-3815</guid>
		<description>All this is sound advice from a few years ago when the intranet ( ie welll designed web pages containing official company information) was the only game in town. Today you have to think about the right tool for the job. Today there is the opportunity to reduce the scope and workload of a migration by focusing only on the `what everyone must know&#039; stuff and using blogs, wikis, team sites and discussion forums as repositories for the local, detailed, informal, personal and temporary information that got caught in the intra net in the past. By all means make everything findable via search but group the results by source and list the official sources first.  Most organisations can&#039;t afford to maintain a gold standard for all the information that gets published internally; so do less but do it better would be my mantra.</description>
		<content:encoded><![CDATA[<p>All this is sound advice from a few years ago when the intranet ( ie welll designed web pages containing official company information) was the only game in town. Today you have to think about the right tool for the job. Today there is the opportunity to reduce the scope and workload of a migration by focusing only on the `what everyone must know&#8217; stuff and using blogs, wikis, team sites and discussion forums as repositories for the local, detailed, informal, personal and temporary information that got caught in the intra net in the past. By all means make everything findable via search but group the results by source and list the official sources first.  Most organisations can&#8217;t afford to maintain a gold standard for all the information that gets published internally; so do less but do it better would be my mantra.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Intranet o enterprise 2.0? Guarda la governance e lo saprai &#124; Intranet Management</title>
		<link>http://www.jboye.com/blogpost/migrating-to-a-new-intranet/comment-page-1/#comment-3658</link>
		<dc:creator>Intranet o enterprise 2.0? Guarda la governance e lo saprai &#124; Intranet Management</dc:creator>
		<pubDate>Mon, 25 Jan 2010 13:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=5270#comment-3658</guid>
		<description>[...] vi segnalo un bel post di Jane McConnell che da alcuni consigli sulla governance, e un altro post  di J. Boye su come supportare al meglio i &#8220;content owner&#8221; nei progetti intranet che coinvolgano una migrazione di contenuti [...]</description>
		<content:encoded><![CDATA[<p>[...] vi segnalo un bel post di Jane McConnell che da alcuni consigli sulla governance, e un altro post  di J. Boye su come supportare al meglio i &#8220;content owner&#8221; nei progetti intranet che coinvolgano una migrazione di contenuti [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->