<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: 10 Best Intranets of 2006: Nielson Normal Group</title>
	<atom:link href="http://www.fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/</link>
	<description></description>
	<lastBuildDate>Sat, 07 Nov 2009 18:38:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Perry Hewitt</title>
		<link>http://www.fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/comment-page-1/#comment-1456</link>
		<dc:creator>Perry Hewitt</dc:creator>
		<pubDate>Thu, 22 Feb 2007 15:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/#comment-1456</guid>
		<description>Haven&#039;t read the full report, but am pleased to see others using an intranet wiki as a way to catalog/cut through jargon. I&#039;ve built intranets within education and technology firms, and their heavily reliance on internal lingo is daunting. While it&#039;s touted as an onboarding tool, I sense there are as many established employees using it to find out how others are using the same terms...</description>
		<content:encoded><![CDATA[<p>Haven&#8217;t read the full report, but am pleased to see others using an intranet wiki as a way to catalog/cut through jargon. I&#8217;ve built intranets within education and technology firms, and their heavily reliance on internal lingo is daunting. While it&#8217;s touted as an onboarding tool, I sense there are as many established employees using it to find out how others are using the same terms&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shiv Singh</title>
		<link>http://www.fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/comment-page-1/#comment-1426</link>
		<dc:creator>Shiv Singh</dc:creator>
		<pubDate>Wed, 21 Feb 2007 21:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/#comment-1426</guid>
		<description>I must admit I wasn&#039;t too excited about the Neilson Norman Report this year. I liked the examples and there are a lot of useful tips in it but I felt it lacking in its methodology and some of the conclusions. I wrote a long blog post about it here if anyone is interested.

http://www.theworkplaceblog.com/2007/01/dont_buy_jacob_neilsons_new_re.html</description>
		<content:encoded><![CDATA[<p>I must admit I wasn&#8217;t too excited about the Neilson Norman Report this year. I liked the examples and there are a lot of useful tips in it but I felt it lacking in its methodology and some of the conclusions. I wrote a long blog post about it here if anyone is interested.</p>
<p><a href="http://www.theworkplaceblog.com/2007/01/dont_buy_jacob_neilsons_new_re.html" rel="nofollow">http://www.theworkplaceblog.com/2007/01/dont_buy_jacob_neilsons_new_re.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zia</title>
		<link>http://www.fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/comment-page-1/#comment-1421</link>
		<dc:creator>Zia</dc:creator>
		<pubDate>Wed, 21 Feb 2007 19:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/#comment-1421</guid>
		<description>Why is it that there are so few visible examples of cool intranets? Clearly, the companies themselves may want to prevent competitors from seeing how they design their internal collaboration sites but it would seem that a more open &quot;show-and-tell&quot; approach would benefit one and all.</description>
		<content:encoded><![CDATA[<p>Why is it that there are so few visible examples of cool intranets? Clearly, the companies themselves may want to prevent competitors from seeing how they design their internal collaboration sites but it would seem that a more open &#8220;show-and-tell&#8221; approach would benefit one and all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://www.fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/comment-page-1/#comment-1420</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Wed, 21 Feb 2007 17:11:23 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/02/20/10-best-intranets-of-2006-nielson-normal-group/#comment-1420</guid>
		<description>Of most significant value, this report gives you access to the necessary &#039;design patterns&#039; that we are often looking for, for deep analysis. Public access to the intranet designs of major companies is not easy to come by. That alone makes the price of admission well worth it, but I also recommend buying the electronic license and sharing it liberally inside your company (for those in larger organizations). By doing so you can then reference it liberally to reinforce your points (more added value).</description>
		<content:encoded><![CDATA[<p>Of most significant value, this report gives you access to the necessary &#8216;design patterns&#8217; that we are often looking for, for deep analysis. Public access to the intranet designs of major companies is not easy to come by. That alone makes the price of admission well worth it, but I also recommend buying the electronic license and sharing it liberally inside your company (for those in larger organizations). By doing so you can then reference it liberally to reinforce your points (more added value).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
