<?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: What are the common Service Design pitfalls?</title>
	<atom:link href="http://www.31v.nl/2009/03/what-are-the-common-service-design-pitfalls/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.31v.nl/2009/03/what-are-the-common-service-design-pitfalls/</link>
	<description>+31 30 890 3220 / energie@31v.nl</description>
	<lastBuildDate>Mon, 05 Dec 2011 09:00:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Justin Knecht</title>
		<link>http://www.31v.nl/2009/03/what-are-the-common-service-design-pitfalls/comment-page-1/#comment-1106</link>
		<dc:creator>Justin Knecht</dc:creator>
		<pubDate>Thu, 23 Apr 2009 10:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.31v.nl/?p=1883#comment-1106</guid>
		<description>As far as any special skills, no. On the customer side, I think you learn more from those people at extremes of use. Power users. People who have switched. Front-line employees should be chosen in relation to having contact with customers at key points of contact.</description>
		<content:encoded><![CDATA[<p>As far as any special skills, no. On the customer side, I think you learn more from those people at extremes of use. Power users. People who have switched. Front-line employees should be chosen in relation to having contact with customers at key points of contact.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aletha Bitter</title>
		<link>http://www.31v.nl/2009/03/what-are-the-common-service-design-pitfalls/comment-page-1/#comment-1100</link>
		<dc:creator>Aletha Bitter</dc:creator>
		<pubDate>Thu, 16 Apr 2009 19:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.31v.nl/?p=1883#comment-1100</guid>
		<description>Thank you for your comments. Can you ask just any customer or front-line employee to participate in an service design project or do they need special skills? I know a service designer guides them through the process, and the customer/ front-line employee knows a lot about the services offered, but are you asking random people to help designing or do you select certain people?</description>
		<content:encoded><![CDATA[<p>Thank you for your comments. Can you ask just any customer or front-line employee to participate in an service design project or do they need special skills? I know a service designer guides them through the process, and the customer/ front-line employee knows a lot about the services offered, but are you asking random people to help designing or do you select certain people?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Knecht</title>
		<link>http://www.31v.nl/2009/03/what-are-the-common-service-design-pitfalls/comment-page-1/#comment-1099</link>
		<dc:creator>Justin Knecht</dc:creator>
		<pubDate>Thu, 16 Apr 2009 14:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.31v.nl/?p=1883#comment-1099</guid>
		<description>I think as service designers we need to pay special attention to the aspect of service implementation and training. It&#039;s all very exciting and glamorous doing service and experience mapping, but you can&#039;t forget that you&#039;re going to have to get buy-in and behaviour change from front-line employees. As well as understanding if and how the implementation can scale.</description>
		<content:encoded><![CDATA[<p>I think as service designers we need to pay special attention to the aspect of service implementation and training. It&#8217;s all very exciting and glamorous doing service and experience mapping, but you can&#8217;t forget that you&#8217;re going to have to get buy-in and behaviour change from front-line employees. As well as understanding if and how the implementation can scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://www.31v.nl/2009/03/what-are-the-common-service-design-pitfalls/comment-page-1/#comment-1092</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Mon, 06 Apr 2009 16:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.31v.nl/?p=1883#comment-1092</guid>
		<description>It&#039;s a challenge getting some senior managers, who have been promoted to those positions because they know how to fix the service, to recognise that the front line staff and customers know better than they do!

It&#039;s a challenge giving the delivering something tangible to the customer that they can point to and say &quot;that was worth £xxxx!&quot; It&#039;s either a large format, hi def illustration of the new service, or some qual / quant evaluation of it. But the service is often so intagible. The more they are involved in the design the more this expectation can be managed

It&#039;s a challenge getting subcontractrs to play ball

It&#039;s a challenge defending scope creep - there&#039;s always another layer of complexity in any service, but only so much the client is willing to pay to fix!</description>
		<content:encoded><![CDATA[<p>It&#8217;s a challenge getting some senior managers, who have been promoted to those positions because they know how to fix the service, to recognise that the front line staff and customers know better than they do!</p>
<p>It&#8217;s a challenge giving the delivering something tangible to the customer that they can point to and say &#8220;that was worth £xxxx!&#8221; It&#8217;s either a large format, hi def illustration of the new service, or some qual / quant evaluation of it. But the service is often so intagible. The more they are involved in the design the more this expectation can be managed</p>
<p>It&#8217;s a challenge getting subcontractrs to play ball</p>
<p>It&#8217;s a challenge defending scope creep &#8211; there&#8217;s always another layer of complexity in any service, but only so much the client is willing to pay to fix!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

