<?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: It’s all about me</title>
	<atom:link href="http://paulclarke.com/honestlyreal/2010/04/it%e2%80%99s-all-about-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://paulclarke.com/honestlyreal/2010/04/it%e2%80%99s-all-about-me/</link>
	<description></description>
	<lastBuildDate>Mon, 21 May 2012 08:48:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Rollo</title>
		<link>http://paulclarke.com/honestlyreal/2010/04/it%e2%80%99s-all-about-me/comment-page-1/#comment-996</link>
		<dc:creator>Rollo</dc:creator>
		<pubDate>Tue, 06 Apr 2010 15:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://paulclarke.com/honestlyreal/?p=548#comment-996</guid>
		<description>Paul, just after reading your blog I came across the Employee Authentication Service (EAS) from PA (http://www.paconsulting.com/our-thinking/improving-security-and-access-of-shared-information/). There&#039;s a video overview of the EAS, which I think nicely illustrates the problems of issuing authentication to secure services, and how processes can get out of hand. It&#039;s worth considering that Leeds CC (as used as an example in the video) has over 30,000 employees - so that would require a considerable number of people to administer the EAS. Ah, it&#039;s all so simple...</description>
		<content:encoded><![CDATA[<p>Paul, just after reading your blog I came across the Employee Authentication Service (EAS) from PA (<a href="http://www.paconsulting.com/our-thinking/improving-security-and-access-of-shared-information/" rel="nofollow">http://www.paconsulting.com/our-thinking/improving-security-and-access-of-shared-information/</a>). There&#8217;s a video overview of the EAS, which I think nicely illustrates the problems of issuing authentication to secure services, and how processes can get out of hand. It&#8217;s worth considering that Leeds CC (as used as an example in the video) has over 30,000 employees &#8211; so that would require a considerable number of people to administer the EAS. Ah, it&#8217;s all so simple&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hadley Beeman</title>
		<link>http://paulclarke.com/honestlyreal/2010/04/it%e2%80%99s-all-about-me/comment-page-1/#comment-993</link>
		<dc:creator>Hadley Beeman</dc:creator>
		<pubDate>Mon, 05 Apr 2010 21:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://paulclarke.com/honestlyreal/?p=548#comment-993</guid>
		<description>I agree, this IS complicated.  Hugely so, and (if done properly) should impact pretty much every last corner of government.  It&#039;s an enormous project.

But paying for a government that is highly inefficient, and duplicative, at times, is an expensive luxury. One the budget figures say we can&#039;t afford.

So it sounds like now is the time to attack the complexity, take it seriously and dedicate adequate resources to it.  To work, this solution needs to involve an overhaul in the business of government and a serious citizen focus (from the strategy all the way out to the UX design).  There are a lot of potential pitfalls and each must be carefully addressed for such significant changes to be implemented and carry on delivering government services. Otherwise, as you have so eloquently described, this project will go down the route of those predecessors.  

We have a stronger motivation this time (those budgetary and economic concerns - our deficit isn&#039;t sustainable), and I&#039;m hoping that means that the project will be taken seriously.  I still (thus far) think this CAN be done.  I just hope we&#039;ll have the right group in place to do it.  I can&#039;t agree with you more on the intricacy and complexity of this challenge.</description>
		<content:encoded><![CDATA[<p>I agree, this IS complicated.  Hugely so, and (if done properly) should impact pretty much every last corner of government.  It&#8217;s an enormous project.</p>
<p>But paying for a government that is highly inefficient, and duplicative, at times, is an expensive luxury. One the budget figures say we can&#8217;t afford.</p>
<p>So it sounds like now is the time to attack the complexity, take it seriously and dedicate adequate resources to it.  To work, this solution needs to involve an overhaul in the business of government and a serious citizen focus (from the strategy all the way out to the UX design).  There are a lot of potential pitfalls and each must be carefully addressed for such significant changes to be implemented and carry on delivering government services. Otherwise, as you have so eloquently described, this project will go down the route of those predecessors.  </p>
<p>We have a stronger motivation this time (those budgetary and economic concerns &#8211; our deficit isn&#8217;t sustainable), and I&#8217;m hoping that means that the project will be taken seriously.  I still (thus far) think this CAN be done.  I just hope we&#8217;ll have the right group in place to do it.  I can&#8217;t agree with you more on the intricacy and complexity of this challenge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Watts</title>
		<link>http://paulclarke.com/honestlyreal/2010/04/it%e2%80%99s-all-about-me/comment-page-1/#comment-992</link>
		<dc:creator>Rich Watts</dc:creator>
		<pubDate>Mon, 05 Apr 2010 09:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://paulclarke.com/honestlyreal/?p=548#comment-992</guid>
		<description>Great post, Paul. As someone who has to grapple with this stuff most days (within the field of social care), a lot of it rings true.

I think a lot of what you write above holds internally (i.e. an organisation&#039;s relationship with its staff) as well as externally (i.e. an organisation&#039;s relationship with its &#039;clients&#039;). I&#039;m struck at work in general by how simple everyone thinks everything is - even from issuing annual leave forms, starting a staff suggestions box, ensuring documents/materials are available in alternative formats - when the reality of implementing this stuff is much harder.

For me, being a manager is therefore recognising the complicated nature of all this stuff and enabling staff to work to overcome it. We may be able to anticipate 25% of the terrain we&#039;ll need to navigate, but the remaining 75% will need to be somewhat reactive once we know the real problems that come up.

If that&#039;s right, then the implications for determining a technological solution - which I think needs 75% sure up front, 25% to be tweaked after - are not too fun.</description>
		<content:encoded><![CDATA[<p>Great post, Paul. As someone who has to grapple with this stuff most days (within the field of social care), a lot of it rings true.</p>
<p>I think a lot of what you write above holds internally (i.e. an organisation&#8217;s relationship with its staff) as well as externally (i.e. an organisation&#8217;s relationship with its &#8216;clients&#8217;). I&#8217;m struck at work in general by how simple everyone thinks everything is &#8211; even from issuing annual leave forms, starting a staff suggestions box, ensuring documents/materials are available in alternative formats &#8211; when the reality of implementing this stuff is much harder.</p>
<p>For me, being a manager is therefore recognising the complicated nature of all this stuff and enabling staff to work to overcome it. We may be able to anticipate 25% of the terrain we&#8217;ll need to navigate, but the remaining 75% will need to be somewhat reactive once we know the real problems that come up.</p>
<p>If that&#8217;s right, then the implications for determining a technological solution &#8211; which I think needs 75% sure up front, 25% to be tweaked after &#8211; are not too fun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steph Gray</title>
		<link>http://paulclarke.com/honestlyreal/2010/04/it%e2%80%99s-all-about-me/comment-page-1/#comment-991</link>
		<dc:creator>Steph Gray</dc:creator>
		<pubDate>Sun, 04 Apr 2010 14:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://paulclarke.com/honestlyreal/?p=548#comment-991</guid>
		<description>Interesting, and I&#039;m glad you&#039;ve teased out some of the challenges behind MyGov (and its predecessors).

You&#039;re right too to ask about the nature of &#039;personalisation&#039; that&#039;s at stake. There&#039;s a risk of disappearing into a rabbit warren of authentication systems, and lose sight of the bigger picture.

I&#039;ve not seen the research for a while, but here&#039;s my gut feel: people don&#039;t necessarily want &#039;personalised&#039; services; they want easy to access, ease to use services.

I don&#039;t mind logging into Amazon with one set of details, and into PayPal with another. I don&#039;t expect the private sector half of the economy to join that stuff up, and I&#039;d be sceptical if they claimed to. But if registering to buy a book takes me more than 30 seconds, I&#039;ll be grumpy; if it takes me more than a couple of minutes to pay for something the first time with PayPal, ditto. But my bank account is another matter - the four screens of details I have to work through to check my balance is a good nuisance, to me at least. Probably ditto for my tax and health information, were they both to be online. But not for renewing a library book, getting a newsletter about training, getting help with a new business, or buying my car tax disc.

There are a few challenges here, then:

- making transactions easy to accomplish, like buying a book from Amazon
- developing authentication &amp; identity management systems which fit the nature of the task and expectations of privacy (and don&#039;t err on the side of caution, just because)
- making transactions easy to find, so I know where to start and who&#039;s responsible for administering Tax X or Service Y these days

I don&#039;t underestimate the complexity of the hidden wiring behind achieving this, which is one reason why I&#039;m so impressed every year when I renew my car tax online (three cheers DVLA, IBM &amp; Directgov). But I think there&#039;s an opportunity for a simpler approach to delivering public services online in a way which satisfies users:

1. Think less about the &#039;single account&#039; and more about the single place to start. We have those: Directgov and Business Link.

2. Think less about an identity management system, and more about usable online account management. One account for my taxes, one for my business, one for my health, one for my council - that&#039;s still just about OK, as long as they match my expectations of the privacy and security behind them. Only ask me for the information you need. 

3. Make the supersites into very simple customisable portals. That sounds shockingly old-school, but I think it&#039;s what would deliver the greatest benefit. Let me tell you a little bit about my lifestyle (like, 10 questions max) and give me a cut of the stuff that&#039;s helpful. No car? Don&#039;t show me the motoring stuff. Live in Scotland? Show me what&#039;s a Scottish service, and what&#039;s UK-wide, plus a widget of good stuff from my local council. Got kids? Show me the health/money/activities info that&#039;s right for their ages in my area. Above all, keep the questions simple, and show me why it&#039;s worth me 20 seconds to tick some boxes.

That&#039;s a workable, deliverable MyGov, from where I&#039;m sitting. 10 straightforward questions, a clear explanation of why you&#039;re asking and what I&#039;ll get back, a page that looks a bit like Netvibes, and a bookmark in my favourites. A user account I can stay logged into for months at a time, only having to enter more sophisticated authentication info when I&#039;m entering my tax details or talking to someone official about my sexual history.

Does that make me a White Knight? ;-)</description>
		<content:encoded><![CDATA[<p>Interesting, and I&#8217;m glad you&#8217;ve teased out some of the challenges behind MyGov (and its predecessors).</p>
<p>You&#8217;re right too to ask about the nature of &#8216;personalisation&#8217; that&#8217;s at stake. There&#8217;s a risk of disappearing into a rabbit warren of authentication systems, and lose sight of the bigger picture.</p>
<p>I&#8217;ve not seen the research for a while, but here&#8217;s my gut feel: people don&#8217;t necessarily want &#8216;personalised&#8217; services; they want easy to access, ease to use services.</p>
<p>I don&#8217;t mind logging into Amazon with one set of details, and into PayPal with another. I don&#8217;t expect the private sector half of the economy to join that stuff up, and I&#8217;d be sceptical if they claimed to. But if registering to buy a book takes me more than 30 seconds, I&#8217;ll be grumpy; if it takes me more than a couple of minutes to pay for something the first time with PayPal, ditto. But my bank account is another matter &#8211; the four screens of details I have to work through to check my balance is a good nuisance, to me at least. Probably ditto for my tax and health information, were they both to be online. But not for renewing a library book, getting a newsletter about training, getting help with a new business, or buying my car tax disc.</p>
<p>There are a few challenges here, then:</p>
<p>- making transactions easy to accomplish, like buying a book from Amazon<br />
- developing authentication &amp; identity management systems which fit the nature of the task and expectations of privacy (and don&#8217;t err on the side of caution, just because)<br />
- making transactions easy to find, so I know where to start and who&#8217;s responsible for administering Tax X or Service Y these days</p>
<p>I don&#8217;t underestimate the complexity of the hidden wiring behind achieving this, which is one reason why I&#8217;m so impressed every year when I renew my car tax online (three cheers DVLA, IBM &amp; Directgov). But I think there&#8217;s an opportunity for a simpler approach to delivering public services online in a way which satisfies users:</p>
<p>1. Think less about the &#8216;single account&#8217; and more about the single place to start. We have those: Directgov and Business Link.</p>
<p>2. Think less about an identity management system, and more about usable online account management. One account for my taxes, one for my business, one for my health, one for my council &#8211; that&#8217;s still just about OK, as long as they match my expectations of the privacy and security behind them. Only ask me for the information you need. </p>
<p>3. Make the supersites into very simple customisable portals. That sounds shockingly old-school, but I think it&#8217;s what would deliver the greatest benefit. Let me tell you a little bit about my lifestyle (like, 10 questions max) and give me a cut of the stuff that&#8217;s helpful. No car? Don&#8217;t show me the motoring stuff. Live in Scotland? Show me what&#8217;s a Scottish service, and what&#8217;s UK-wide, plus a widget of good stuff from my local council. Got kids? Show me the health/money/activities info that&#8217;s right for their ages in my area. Above all, keep the questions simple, and show me why it&#8217;s worth me 20 seconds to tick some boxes.</p>
<p>That&#8217;s a workable, deliverable MyGov, from where I&#8217;m sitting. 10 straightforward questions, a clear explanation of why you&#8217;re asking and what I&#8217;ll get back, a page that looks a bit like Netvibes, and a bookmark in my favourites. A user account I can stay logged into for months at a time, only having to enter more sophisticated authentication info when I&#8217;m entering my tax details or talking to someone official about my sexual history.</p>
<p>Does that make me a White Knight? <img src='http://paulclarke.com/honestlyreal/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

