<?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 for Intranet Matters</title>
	<atom:link href="http://intranet-matters.de/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://intranet-matters.de</link>
	<description>Next Generation Social Information, Collaboration and Communication Platforms</description>
	<pubDate>Fri, 30 Jul 2010 19:24:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on The Name of the Intranet by Neil</title>
		<link>http://intranet-matters.de/2008/09/30/the-name-of-the-intranet/#comment-718</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Wed, 14 Jul 2010 12:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=84#comment-718</guid>
		<description>For WWF our intranet is called Connect.</description>
		<content:encoded><![CDATA[<p>For WWF our intranet is called Connect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Name of the Intranet by Stephan Schillerwein</title>
		<link>http://intranet-matters.de/2008/09/30/the-name-of-the-intranet/#comment-717</link>
		<dc:creator>Stephan Schillerwein</dc:creator>
		<pubDate>Wed, 14 Jul 2010 08:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=84#comment-717</guid>
		<description>Not sure if I fully understand the nature of our business, Trish, but here're some quick ideas :
- iGuardian
- iCare
- Careline
- Homeplace
- MyHome</description>
		<content:encoded><![CDATA[<p>Not sure if I fully understand the nature of our business, Trish, but here&#8217;re some quick ideas :<br />
- iGuardian<br />
- iCare<br />
- Careline<br />
- Homeplace<br />
- MyHome</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Name of the Intranet by Trish</title>
		<link>http://intranet-matters.de/2008/09/30/the-name-of-the-intranet/#comment-716</link>
		<dc:creator>Trish</dc:creator>
		<pubDate>Tue, 13 Jul 2010 19:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=84#comment-716</guid>
		<description>Here's a challenging one.  Need Portal name for Home Health Care organization!  Any suggestions?</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a challenging one.  Need Portal name for Home Health Care organization!  Any suggestions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intranet Case Study: Chr. Hansen A/S by Stephan Schillerwein</title>
		<link>http://intranet-matters.de/2010/03/18/intranet-case-study-chr-hansen-as/#comment-711</link>
		<dc:creator>Stephan Schillerwein</dc:creator>
		<pubDate>Tue, 06 Jul 2010 15:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=114#comment-711</guid>
		<description>Even though personas are used for websites more often than for intranets, I think that the amount of positive experience with personas for intranets is quite substantial. Positioning the personas with your stakeholders can sometimes be a bit tricky in the beginning, but apart from that, it's a concept that you'll benefit your project in every step. Of course only if done right.

Here's a link to a good starter into the topic: "Using Persona Advocates to develop user-centric intranets and portals" by Howard McQueen: http://www.mcq.com/article-persona</description>
		<content:encoded><![CDATA[<p>Even though personas are used for websites more often than for intranets, I think that the amount of positive experience with personas for intranets is quite substantial. Positioning the personas with your stakeholders can sometimes be a bit tricky in the beginning, but apart from that, it&#8217;s a concept that you&#8217;ll benefit your project in every step. Of course only if done right.</p>
<p>Here&#8217;s a link to a good starter into the topic: &#8220;Using Persona Advocates to develop user-centric intranets and portals&#8221; by Howard McQueen: <a href="http://www.mcq.com/article-persona" rel="nofollow">http://www.mcq.com/article-persona</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 5 Thesen zur Zukunft des Intranets als universelles Arbeitsmittel by Stephan Schillerwein</title>
		<link>http://intranet-matters.de/2010/05/04/5-thesen-zur-zukunft-des-intranets-als-universelles-arbeitsmittel/#comment-703</link>
		<dc:creator>Stephan Schillerwein</dc:creator>
		<pubDate>Thu, 10 Jun 2010 13:19:40 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=119#comment-703</guid>
		<description>Unter http://www.intranet-summit.de/impressionen/best-of-videos.html?vid=xxhmb steht der Videomitschnitt der Keynote frei zugänglich zur Verfügung.</description>
		<content:encoded><![CDATA[<p>Unter <a href="http://www.intranet-summit.de/impressionen/best-of-videos.html?vid=xxhmb" rel="nofollow">http://www.intranet-summit.de/impressionen/best-of-videos.html?vid=xxhmb</a> steht der Videomitschnitt der Keynote frei zugänglich zur Verfügung.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 5 Thesen zur Zukunft des Intranets als universelles Arbeitsmittel by hyperkontext &#124; Weblog</title>
		<link>http://intranet-matters.de/2010/05/04/5-thesen-zur-zukunft-des-intranets-als-universelles-arbeitsmittel/#comment-701</link>
		<dc:creator>hyperkontext &#124; Weblog</dc:creator>
		<pubDate>Mon, 07 Jun 2010 06:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=119#comment-701</guid>
		<description>&lt;strong&gt;Mai 2010 im Kontext...&lt;/strong&gt;

Themen: Webtermine.at; Accessibility, CSS und B&#252;cher zu HTML5. Chefsache: Die Chance, sie nicht zu nutzen. F&#252;hrungskr&#228;fte werden oft mehr zum Teil des Problems, als ein Beitrag zur L&#246;sung....</description>
		<content:encoded><![CDATA[<p><strong>Mai 2010 im Kontext&#8230;</strong></p>
<p>Themen: Webtermine.at; Accessibility, CSS und B&#252;cher zu HTML5. Chefsache: Die Chance, sie nicht zu nutzen. F&#252;hrungskr&#228;fte werden oft mehr zum Teil des Problems, als ein Beitrag zur L&#246;sung&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Recipe for Failure&#8230; the Senior Management Blog on the Intranet by Senior Manager blogs and non-blogs &#124; 2010 Intranet Trends &#124; Globally Local&#8230; Locally Global &#124; Globally Local&#8230; Locally Global</title>
		<link>http://intranet-matters.de/2010/01/29/recipe-for-failure-the-senior-management-blog-on-the-intranet/#comment-694</link>
		<dc:creator>Senior Manager blogs and non-blogs &#124; 2010 Intranet Trends &#124; Globally Local&#8230; Locally Global &#124; Globally Local&#8230; Locally Global</dc:creator>
		<pubDate>Sun, 23 May 2010 13:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=112#comment-694</guid>
		<description>[...] short while ago Stephan Schillerwein wrote a blog post entitled &#8220;Recipe for failure, the senior management blog on the intranet&#8220;. Following on from Stephan&#8217;s post and the conversation that followed, I&#8217;d like [...]</description>
		<content:encoded><![CDATA[<p>[...] short while ago Stephan Schillerwein wrote a blog post entitled &#8220;Recipe for failure, the senior management blog on the intranet&#8220;. Following on from Stephan&#8217;s post and the conversation that followed, I&#8217;d like [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Name of the Intranet by Matt Varney</title>
		<link>http://intranet-matters.de/2008/09/30/the-name-of-the-intranet/#comment-693</link>
		<dc:creator>Matt Varney</dc:creator>
		<pubDate>Fri, 21 May 2010 18:42:49 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=84#comment-693</guid>
		<description>One for the list, our employee intranet at KCTCS, simply called "thePoint". Launched in March, 2009, it is based on SharePoint 2007.   

KCTCS is a mouthful of an acronym for the Kentucky Community and Technical College System, which is even more of a mouthful.  Coming up with a brand and name for the intranet for our employees had just a few requirements, one of which was "make it simple and not a mouthful".  Basing it on the SharePoint name and concept made the decision easy.</description>
		<content:encoded><![CDATA[<p>One for the list, our employee intranet at KCTCS, simply called &#8220;thePoint&#8221;. Launched in March, 2009, it is based on SharePoint 2007.   </p>
<p>KCTCS is a mouthful of an acronym for the Kentucky Community and Technical College System, which is even more of a mouthful.  Coming up with a brand and name for the intranet for our employees had just a few requirements, one of which was &#8220;make it simple and not a mouthful&#8221;.  Basing it on the SharePoint name and concept made the decision easy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Name of the Intranet by Robin Farr</title>
		<link>http://intranet-matters.de/2008/09/30/the-name-of-the-intranet/#comment-691</link>
		<dc:creator>Robin Farr</dc:creator>
		<pubDate>Thu, 20 May 2010 19:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=84#comment-691</guid>
		<description>Great collection!

Here's ours: The British Columbia Public Service intranet is called @Work.</description>
		<content:encoded><![CDATA[<p>Great collection!</p>
<p>Here&#8217;s ours: The British Columbia Public Service intranet is called @Work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Name of the Intranet by JohnO</title>
		<link>http://intranet-matters.de/2008/09/30/the-name-of-the-intranet/#comment-690</link>
		<dc:creator>JohnO</dc:creator>
		<pubDate>Thu, 20 May 2010 18:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://intranet-matters.de/?p=84#comment-690</guid>
		<description>I manage the intranet at David Evans Associates Inc. in Portland, Ore., which is called Merlin. Comes complete with tiny animated wizard.</description>
		<content:encoded><![CDATA[<p>I manage the intranet at David Evans Associates Inc. in Portland, Ore., which is called Merlin. Comes complete with tiny animated wizard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
