<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Analogues of service</title>
	<atom:link href="http://greatemancipator.com/2009/11/05/analogues-of-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://greatemancipator.com/2009/11/05/analogues-of-service/</link>
	<description>A discussion point on electronic government performance</description>
	<lastBuildDate>Fri, 16 Jul 2010 07:10:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Miley Mason</title>
		<link>http://greatemancipator.com/2009/11/05/analogues-of-service/#comment-691</link>
		<dc:creator>Miley Mason</dc:creator>
		<pubDate>Mon, 28 Dec 2009 22:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://greatemancipator.com/?p=1001#comment-691</guid>
		<description>I bookmarked your site, this is very useful, thank you. Please check mine : &lt;a href=&quot;http://www.mbi.com.tr/eng/&quot; rel=&quot;nofollow&quot;&gt;crm - customer resource management&lt;/A&gt;</description>
		<content:encoded><![CDATA[<p>I bookmarked your site, this is very useful, thank you. Please check mine : <a href="http://www.mbi.com.tr/eng/" rel="nofollow">crm &#8211; customer resource management</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neville Higman</title>
		<link>http://greatemancipator.com/2009/11/05/analogues-of-service/#comment-635</link>
		<dc:creator>Neville Higman</dc:creator>
		<pubDate>Fri, 06 Nov 2009 12:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://greatemancipator.com/?p=1001#comment-635</guid>
		<description>I was very taken with this article too, particularly the second of these two paragraphs:

‘Carey is convinced that one of the problems with government e-services and digital systems is that they try to replicate analogue systems in a digital environment. For example, digitising a 36 page analogue form and expecting people to fill it out, resulting in “appalling” completion rates.

‘“That may mean simplifying the tax system, for instance, or the benefits system,” he suggests. “You may have to round up some benefits and tax bands for rough justice, but you would save so much money if you did it.”’

That set me thinking.

Imagine if the complexity of personal tax assessment was fixed by an upper limit on the number of questions that could be asked - particularly if that number was based on measures of completion rates and data cleanliness.  It would force an outside-in customer-focussed system design. Economy of flow would be driven right through the system starting from the customers&#039; perspective. It would discourage well intended but centre-driven tampering with the rules: if a new rule requires supplementary questions, a counter-productive (and measurable)cost is paid through added complexity to the form.

If my kids can identify most things in the universe by asking twenty questions on a long car journey, it should be possible to make a just assessment of tax from a limited set of questions.</description>
		<content:encoded><![CDATA[<p>I was very taken with this article too, particularly the second of these two paragraphs:</p>
<p>‘Carey is convinced that one of the problems with government e-services and digital systems is that they try to replicate analogue systems in a digital environment. For example, digitising a 36 page analogue form and expecting people to fill it out, resulting in “appalling” completion rates.</p>
<p>‘“That may mean simplifying the tax system, for instance, or the benefits system,” he suggests. “You may have to round up some benefits and tax bands for rough justice, but you would save so much money if you did it.”’</p>
<p>That set me thinking.</p>
<p>Imagine if the complexity of personal tax assessment was fixed by an upper limit on the number of questions that could be asked &#8211; particularly if that number was based on measures of completion rates and data cleanliness.  It would force an outside-in customer-focussed system design. Economy of flow would be driven right through the system starting from the customers&#8217; perspective. It would discourage well intended but centre-driven tampering with the rules: if a new rule requires supplementary questions, a counter-productive (and measurable)cost is paid through added complexity to the form.</p>
<p>If my kids can identify most things in the universe by asking twenty questions on a long car journey, it should be possible to make a just assessment of tax from a limited set of questions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
