<?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: Personalisation vs segmentation</title>
	<atom:link href="http://www.steptwo.com.au/papers/cmb_personalisation/index.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html</link>
	<description>Beyond The Idea</description>
	<lastBuildDate>Sat, 20 Mar 2010 01:32:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Intranet Personalization that Works - Intranet Blog - ThoughtFarmer</title>
		<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html/comment-page-1#comment-1208</link>
		<dc:creator>Intranet Personalization that Works - Intranet Blog - ThoughtFarmer</dc:creator>
		<pubDate>Thu, 03 Dec 2009 18:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=195#comment-1208</guid>
		<description>[...] debate about personalization vs. segmentation on the intranet has been much discussed and researched by many pioneering intranet designers and [...]</description>
		<content:encoded><![CDATA[<p>[...] debate about personalization vs. segmentation on the intranet has been much discussed and researched by many pioneering intranet designers and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Implicit Personalization on the Intranet &#171; Dachis Group Collaboratory &#124; Social Business Design</title>
		<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html/comment-page-1#comment-1207</link>
		<dc:creator>Implicit Personalization on the Intranet &#171; Dachis Group Collaboratory &#124; Social Business Design</dc:creator>
		<pubDate>Thu, 03 Dec 2009 17:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=195#comment-1207</guid>
		<description>[...] debate about personalization vs. segmentation on the intranet has been much discussed and researched by many pioneering intranet designers and [...]</description>
		<content:encoded><![CDATA[<p>[...] debate about personalization vs. segmentation on the intranet has been much discussed and researched by many pioneering intranet designers and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html/comment-page-1#comment-24</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Wed, 27 Aug 2008 21:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=195#comment-24</guid>
		<description>Of course, both approaches require a fair bit of research, planning, implementation and management. Which is the real challenge.</description>
		<content:encoded><![CDATA[<p>Of course, both approaches require a fair bit of research, planning, implementation and management. Which is the real challenge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geir</title>
		<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html/comment-page-1#comment-21</link>
		<dc:creator>Geir</dc:creator>
		<pubDate>Wed, 27 Aug 2008 12:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=195#comment-21</guid>
		<description>In my experience, often the best solution is a combination of the two. Use segmentation to reduce information overload and personalization to overcome the fact that segmentation never will be granulated enough to secure all the specific needs of all employees. This means that the employees should be allowed to choose what is given to them from the whole system, not just within her segment.</description>
		<content:encoded><![CDATA[<p>In my experience, often the best solution is a combination of the two. Use segmentation to reduce information overload and personalization to overcome the fact that segmentation never will be granulated enough to secure all the specific needs of all employees. This means that the employees should be allowed to choose what is given to them from the whole system, not just within her segment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html/comment-page-1#comment-19</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Wed, 27 Aug 2008 08:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=195#comment-19</guid>
		<description>The two are certainly not mutually exclusive! In terms of how things can be segmented, there are three common approaches, as outlined in this article: &lt;a href=&quot;http://www.steptwo.com.au/papers/cmb_staffsegments/&quot; rel=&quot;nofollow&quot;&gt;Segmenting staff information needs&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>The two are certainly not mutually exclusive! In terms of how things can be segmented, there are three common approaches, as outlined in this article: <a href="http://www.steptwo.com.au/papers/cmb_staffsegments/" rel="nofollow">Segmenting staff information needs</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.steptwo.com.au/papers/cmb_personalisation/index.html/comment-page-1#comment-14</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 26 Aug 2008 15:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=195#comment-14</guid>
		<description>I take it that you can provide personalization within a segment?  Segment can be products or services...the single-login with role-based filtering would be a way to go?</description>
		<content:encoded><![CDATA[<p>I take it that you can provide personalization within a segment?  Segment can be products or services&#8230;the single-login with role-based filtering would be a way to go?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
