Neil Williams has written an excellent post on the Government Digital Service blog about what constitutes a government policy and how the single gov.uk website (now in beta) should present information about it to citizens.

The post sets out how the gov.uk team is using as a working definition of policy "statements of the government's position, intent or action".

This includes mandatory information on the issue and actions being taken in response to it, plus optional information on the policy background, who is engaged with it, who is being affected by it, the legal framework, partner organisations and related news and publications.

It highlights just how much unpacking the simple word 'policy' seems to require.

Occasionally the government talks in a language that implies there are policies and meta-policies.

The original motivation behind the development of departmental business plans was not so much for Whitehall to achieve something itself, but for it to put in place the frameworks, systems and incentives for others to achieve it.

In which case the 'policies' may become more diffuse, being developed and implemented by a variety of local providers and getting blurred with the day-to-day decisions and delivery, operations and implementation.

Anyway, this post aims to suggest a couple of ways in which the presentation of policy information online could be used to significantly enhance political accountability, in line with my personal definition of eDemocracy.

There are two classes of information, open data and freedom of information releases, which might implicitly be covered by the phrases "statements about actions" or "related publications" but which would benefit from being explicitly mentioned given their potential importance.

They might not be relevant in every scenario, but as well as the statements and speeches about what the government says it is doing, policy pages should also include the datasets which might provide some kind of evidence about what it is actually achieving.

Given that some of the most significant policies (those in the departmental business plans at least) have targets or intended outcomes associated with them, and deadlines, it should be possible to pull out the data from the information strategies which is being used as an indicator for delivery success.

Progress on each of the business plan objectives is already being tracked in monthly updates, but more could be made of this information than is currently the case.

Some data visualisations of this information might also be a massive step forward for visibility and accountability, certainly on the headline commitments if not on every last detailed policy.

Further down the road, gov.uk could also go further on some of the other open data that's out there and relate spending figures to policies so everyone can see how much a policy costs.

Another significant step would be to publicly assign the policy to people or bodies in the departmental organograms which are available now, so it is also clear who is responsible for it.

Adding in this kind of information (gov.uk might be planning some of this already for all I know) – and making it available for re-use and publication anywhere else – could significantly transform the quality of information available to citizens about what their government is both trying to do and actually delivering.

 

Liberal Democrat logoThe Liberal Democrats have published the findings of their policy review on technology issues ahead of their party conference this September.

I covered their initial discussion paper, and it is great to see that eDemocracy issues reached the final conclusions.

As the document notes, the party has not updated its ICT policies since 2003, which explains why it had little to say in response to the Conservative and Labour general election manifesto commitments on issues such as open data.

eDemocracy strategy (three cheers)

Perhaps the most significant proposal in the paper (which is not official policy until agreed by the conference) is the creation of an eDemocracy centre.

This would "initiate and encourage the use of tools by individuals, communities and government at all levels, funded by central government on a permanent basis".

It would perhaps go some way to addressing the continuing complaint of this blog, which is the lack of a UK eDemocracy strategy.

Parliament online (three cheers)

Also of note is the commitment to publishing more understandable information about the legislative process.

"A simple way of ensuring that this happens would be for Parliament to move from a 'document-based' approach to a 'work-flow' approach. This would mean that information presented about Parliamentary business would be aimed at 'the man on the Clapham omnibus', rather than those with a thorough grasp of procedure, as at present."

The implications of a change like that for Parliament's existing legislative data programme would potentially be quite profound.

The policy document also says citizens "should have the right to be consulted on policy decisions that affect them".

"Online public consultations should begin during the writing stage, not merely as rubber stamps after the fact."

That sounds rather like the public reading stage which the government has already begun trialing.

Also of note is a call to liberalise the rules governing online use of parliamentary footage.

ePetitions (two cheers)

While the government's new petitions website has been inundated since its launch, the Lib Dems also call for further improvements to the level of engagement offered by the system.

"[W]e believe that the system should also encourage the formation of communities around both supporters and opponents of the proposition. Petitioning should be more than just a signature; it has the potential to foster more genuine involvement in the political process, making it easier for people to express their views effectively."

This is could be a really important step forward, but ran into cost-cutting reality during the building of the ePetitions site.

The specification for the site indicated that there were no funds available for moderating comments on the site.

Much would depend, though, on whether alternative implementations could be found such as ranking comments or only reactively moderating those which are reported as abusive by other users.

It is an issue that needs addressing, and on heated issues like the death penalty even reactive moderating could lead to a significant workload.

Unless I've missed something, I've not yet seen a government department brave enough to outsource its moderation policy to the public. If cost remains an issue, though, someone might need to take the plunge and try it (The policy document does suggest that there should be more legal protection for websites which publish user comments, so perhaps the government could then make use of its own laws).

The other interesting point to note about the Lib Dem position on ePetitions is how close it is to the Conservative technology manifesto.

"The Conservative Party believes that government websites should not be treated like secure government offices or laboratories, where public access is to be controlled as tightly as possible. We see government websites as being more like a mixture of private building and public spaces, such as squares and parks: places where people can come together to discuss issues and solve problems."

A point of agreement for the coalition partners, it would seem.

eVoting (half a cheer)

On eVoting, the paper says that while "some work has been done" to answer the party's concerns, "the case for widespread implementation of remote electronic voting remains insufficiently strong to warrant abandoning the current voting system".

"However, we recommend that selective pilots are carried out to determine whether remote electronic voting might be a more suitable, secure and convenient option for the electorate than postal voting."

Having written about the case in favour of eVoting, and noted how recent announcements have made it impossible to implement, the call for more pilots at least keeps some momentum behind the issue.

But this proposal doesn't seem to make a huge amount of sense.

The costs of rolling out the system would be incured anyway, but the benefits restricted to a small number of people. And if, as the paper says, it is more "secure and convenient" than postal voting which is currently used then surely it also meets the standards required to be properly implemented.

And if I really wanted to cast my vote electronically and knew how to manipulate the system, I would presumably register for a 'postal vote' and then vote online. So it allows anyone access to the system but just puts a needless obstacle in their path.

Changing the law (three cheers)

Beyond eDemocracy issues, the paper also considers topics ranging from cloud computing to intellectual property.

On the Digital Economy Act, it puts forward two options for the party conference to decide on.

The first would repeal of sections three to 18 of Act, which relate to copyright infringement and the 'three strikes' controversy.

The second would repeal of sections 17 and 18 (site blocking) and offers the weaker formulation that sections 9-16 (technical measures to limit the internet access of repeat illegal filesharers) "should not be commenced until the government can demonstrate that the measures would be necessary and effective".

The #twitterjoketrial issue is also covered, with a call to rethink the clause that led to the conviction of Paul Chambers.

"[We] recommend amendment of primary legislation such as section 127 of the Communications Act 2003 so that messages are read in their correct context and so that people are not prosecuted for what are clearly attempts at humour, and where there is no intention to harm."

There are also concerns about cloud computing if it results in "large corporations taking control of enormous quantities of public or private data outside the reach of national law".

eGovernment (two cheers)

In the world of eGovernment there is support for open standards and an "assumption that public non-personal data belongs to the nation, so should be freely available".

"The government should ensure that it owns the code that it has paid for, and then share it for free within the public sector in order to avoid different parties paying external firms to develop the same software. We would like to see the public sector embrace collaborative development along the lines of websites such as Github."

There is also an interesting and potentially significant statement on supporting the use of open source software.

"One way of promoting open source would be for the government officially to support the use of those open source community websites which perform public services to a similar or better standard than official publicly-funded websites.

"The government could also consider providing resources to the creators responsible. Formerly it has been known for the government to attempt to replicate the work of such websites."

In part this seems to back the work of AlphaGov (which the paper also calls a "positive step") and the Martha Lane Fox review which called for content and services to be made available as APIs.

But it also seems to go further than that in suggesting that the government should avoid building some services altogether and simply help others to do so (perhaps a task for HMG Skunkworks).

It also adds that the evidence shows that "government ministers and senior civil servants – with a few honourable exceptions – do not 'get' information technology, and do not understand the social and political impact of their technology-based decisions".

To address this it calls for a new government office to "advise all other departments of ways in which IT can improve efficiency and quality of service to the public, and engender a culture of online engagement with the public".

"It would have responsibility for procurement policy and oversight of all major IT contracts across government, thereby promoting interconnectivity. It would also provide support with appropriate project management techniques."

How this would fit in with the the Government Digital Service and the Major Projects Authority is not discussed.

 

Update 19/08/2011: See also Simon Dickson's review of the policy paper on the Puffbox blog

 

The Commons public administration committee has just published its keenly anticipated report on government IT.

It's well worth a read, and has interesting sections on engaging users in service design and opening up online channels for service delivery by third parties.

The report says the government could "transform the way it delivers public services... by using technology to involve users in the design and continuous improvement of its services".

As discussed in this post and work done by the AlphaGov team, the MPs say that public feedback "need not be limited to the initial design process alone: technology offers Government the opportunity to refine and improve the design of its services based on the real time flow of citizen feedback".

"We recommend that Departments exploit the internet and other channels to enable users to provide direct online feedback both in the design of services and in their ongoing operation and improvement."

The MPs add:

"IT enabled public services should be provided on an open platform with open interfaces. Government should provide the necessary open infrastructure that empowers people inside and outside of Government to innovate. Making this happen will be part of the transition we have mentioned above from an organisation-centric view of public services to one based on the needs of the citizen. There are obvious parallels between this approach and the Government desire to open up the delivery of public services to non-state actors as part of its Big Society agenda.

"Government should open up online service delivery to non-public sector organisations and explore ways in which public services can be offered through other websites, applications, devices and providers. This should be developed by providing an open Government platform around which others can innovate and improve, built on the principles of open data, open standards and open source.

"In doing so Government will need to address issues of liability for the external delivery of Government services. Moving to a model where third parties provide online Government services will require clarity about where citizens should turn for help when they encounter difficulties, as well as clarifying who is accountable for service delivery."

This final point is interesting, and arguably one of the less-discussed effects of the Martha Lane Fox and AlphaGov-led moves towards allowing third parties to deliver online services via APIs.

 

What shape is a feedback loop?

This is a question prompted by some slides published by the Alphagov team which look at ideas for "closing the feedback loop" by improving online consultation and policy engagement across government.

Co-author of the slides Steph Gray has been seeking "some more first-principles thinking on consultation", and many of the important issues have been covered in the explanatory post from Neil Williams and in follow-ups by Simon Burall of Involve here and here (the comments on these posts are worth reading).

This Andrea Di Maio post on where to use technology in the policy-making process is also worth reading in the Alphagov context and in light of the specification for the new DirectGov ePetitions system which tends to suggest the costs of moderating comments on government websites is a problem.

Anyway, there is not much I could add to what has already been covered elsewhere, so instead this post is heading off at a tangent to deconstruct the metaphor of the feedback loop.

This is excessively pedantic, I realise. In principle, obviously the concept of feedback and corrective action is great. But perhaps there are some distinct senses in which this can be analysed and applied.

A traditional policy cycle

In its Green Book, the Treasury explicitly spells out its view of how the policy cycle begins with a rationale which leads to objectives, appraisal, monitoring, evaluation and feedback.

The ROAMEF cycle

Whether policy-making can actually be done in neat cycles like this is an issue discussed in the Institute for Government (IfG) report Policy-Making in the Real World.

Interestingly, the IfG comes to a similar set of conclusions to the Alphagov team, suggesting that "we need to bring the policy process closer to the real world, and bring the real world closer to the policy process".

While policy design is a broader topic of which consulting and seeking feedback is a subset, the desired outcomes are essentially the same.

Still, if there is an underlying assumption to both the Alphagov and IfG thinking, it seems to be that through feedback and iteration, policies can be improved over time by taking them in a particular direction.

To me, though, that idea seems fairly top-down and Whitehall-centric.

I think there is a parallel here with Simon Burall's post which argued that the idea there is a "real, knowable Public Opinion waiting to be discovered" should be abandoned.

The idea that there is a platonic policy on any issue which the government can slowly move towards is equally fanciful.

So perhaps a feedback loop really looks something like this (as you can tell, I'm not a graphic artist).

Representation of a branch and twigs

Here each loop may be some localist microinnovation broadly heading in the same direction as the thrust of government policy.

But there is still something missing, I think, around understanding the complexity of a landscape which has more localism and diverse service providers and greater personalisation.

Zooming out

Maybe a better image, then, would be this.

Graphical representation of a tree

Image from 123rf.com

Here the trunk of the tree is the original policy intention.

In the case of, say, health service or school reforms then the trunk might be the plan to create new GP consortiums or more academies, but there would also be a pretty significant branches near the base of the trunk given that the opt-in nature of these bodies means that existing structures can continue almost in parallel.

Feedback on one set of policies or organisations might be entirely different to feedback on another. This points to why the idea of a single loop is problematic.

The Alphagov team also suggests using the website to gather feedback on both the delivery and policy at the point at which citizens interact with a government service.

However, the tree image can prompt us think about the blurred line between policy and delivery.

If the trunk is the policy, by the time we reach one of the many individual leaves at the end of the branches then we may well be talking about operational issues.

This might range from the seating arrangements in a Jobcentre Plus in Norfolk to the visiting hours at a hospital in Swansea.

But it can be unclear at which point along the branches the policy becomes an operational judgement. To take a current example, are recent criticisms of the Care Quality Commission due to management misjudgements or policy confusion? Will citizens know enough to be able to make a meaningful distinction?

And if the policy is fundamentally flawed in some way, no amount of feedback and tinkering with delivery is going to improve it (what impact would feedback on the Child Support Agency have had?).

So having deconstructed to death the word 'loop', my conclusion seems to be that even circles can be too linear.

A question of leadership

One other thing is missing so far from both the loop and tree metaphors though: Where is the beginning?

In part this is an issue about co-creation and how early in the process citizens get to have their say (even to the extent of defining what the problems are that need to be addressed).

But it is also a question of leadership and not ignoring the role of politics and politicians in this process.

One purpose of consultation and engagement in the policy sense is to help leaders make better decisions with a broader range of information and a wider spread of views.

Another purpose is to educate the participants in the difficulties of making choices in government.

A minister, or indeed a civil servant, needs to lead debate online as they do in other media if they are to do their job effectively. This is particularly the case when ministers have manifestos to implement and political agendas which they are elected to follow.

Public feedback is never going to be the only driver of innovation or policy, so the explanations of choices which might be provided back to citizens as part of the loop may be intensely political. But that is not a negative thing.

What makes policy trees bear fruit?

Let's stick with the tree imagery a moment longer and consider that co-creation may perhaps be viewed as the roots, the trunk is policy, branches are innovation and leaves are delivery.

In the terminology of Sir Michael Barber (head of the Number 10 Delivery Unit under Tony Blair), a line drawn from the trunk to any given leaf would constitute the delivery chain.

The current government's approach to structural reform and incentivisation, however, would seem to suggest that feedback at the level of each individual leaf is what matters.

This is stretching the metaphor of the tree beyond breaking point, but it might just point to one more lesson about these contrasting approaches.

Under Labour it was the flow up through the trunk and out to the leaves which was important.

The coalition believes that it's the sunlight of transparency and competition at the leaf level which matters most.

But actually both are needed if the tree is to remain healthy.

Update June 6: This additional post from Involve and this one from the Democratic Society are also well worth reading.

© 2012 eDemocracyBlog.com Suffusion theme by Sayontan Sinha