This project – Guerilla Policy – is about developing a movement of people and organisations who use and provide public services, working together to create better social policy. Do we need to write a manifesto?
Our project is based on the critique that much social policy is made by people who have little or no direct experience of the public services and issues that policy relates to – and that this direct experience matters. We’ve put forward ten reasons why we think social policy would be better if it was developed by and with the people who use and provide public and voluntary services – that they have the necessary expertise, experience and insight that good policy development requires. Guerilla is a movement that we hope will serve to bring these people and organisations together in order to create better social policy.
It might sound somewhat portentous, but movements often start with and coalesce around manifestos. Most obviously, we think of political and social movements when we hear ‘manifesto’, but there could also be useful analogies in the manifestos developed by the proponents of open and free software. Here are some examples that in various ways could serve as inspirations for our own manifesto – we’d welcome your own suggestions for other examples, and indeed your views on whether we need a manifesto at all.
- The GNU Manifesto was written by Richard Stallman in 1985 at the beginning of the GNU free software project, and it became a key document in the free software movement. (‘Free software‘ is where the users have the freedom to run, copy, distribute, study, change and improve the software). The Manifesto put forward the reasons and aims of the project, why free software was so important and how it would benefit users, rebutted the objections to free software, and set out how programmers could support the project.
- The Cathedral and the Bazaar is the book of essays first published online in 1997 by ‘hacker philosopher’ Eric S. Raymond on the impact of open source software on technology and indeed the wider world. The title comes from Raymond’s analogy for two fundamentally different ways of developing free software: the ‘cathedral’ model in which source code is available with each software release but the code developed between releases is restricted to an exclusive group of software developers; and the ‘bazaar‘ model in which the code is developed over the internet in full view of the public. Raymond argues that the latter approach is better – the more widely available the source code is for public testing, scrutiny and experimentation, the more rapidly all software bugs will be discovered. Raymond’s evangelism helped to persuade Netscape to release their browser as open source software and promoted Linus Torvalds and the Linux project.
- Out of Netscape came the Mozilla project. ‘Mozilla’ is the everyday name for the free and open source software project founded in 1998 to create a next-generation range of software for the internet, most famously the Firefox browser and Thunderbird email application. The organization was formally registered as a non-profit organization in 2003 as the Mozilla Foundation. Mozilla’s Manifesto sets out the organisation’s principles which it believes are critical for the internet to continue to benefit the public good as well generate commercial activity – the project uses a community-based approach to create world-class open source software and to develop new types of collaborative activities.
Even if you’re not interested in software or in technology generally, these manifestos are worth reading for the revolution in thinking and practice that they represent, and which continues to affect our lives everyday. And of course they also echo and have inspired much of our thinking in this project on how we can collaborate in order to improve social policy.
So, do we need a manifesto? We’ll be discussing this – and exchanging ideas about what this manifesto could include – on our new site. If you haven’t already, register by clicking on the link on the top right, create your profile, and go into the group ‘Developing a Guerilla Manifesto’. We’ll see you there.
We’ve got lots of plans for the next few months as we develop Guerilla Policy. Our ambition is to create a movement of people and organisations who use and provide public services, working together to create better social policy. This is just the start. One of the things we’d love to do is create a hub for frontline practitioners and service users to blog about their work, their experiences and how they think policy needs to change.
We’ve written before here about our love of public and voluntary service bloggers, and how we’d almost always rather read a dispatch from the frontline than (largely) warmed-over opinion from a Westminster-centric commentator. At their best, frontline bloggers capture the day-to-day reality of public services in a way that no-one else can, including the dirty, difficult, and sometimes dangerous experiences that form the basis of real expertise and so the insights we need to improve social policy. For example, read BendyGirl‘s writing on the reality of welfare reform at Benefit Scrounging Scum (shortlisted for the 2012 Orwell Prize). These blogs are often highly informative, contentious, challenging, and sometimes as dull as real life – which after all is the reality of life at the frontline.
These bloggers often engage directly in policy issues, but from a practical, pragmatic and informed perspective that could surely be incorporated into policymaking before we’ve wasted millions of pounds (and harmed people’s lives) introducing policies that are destined to fail. So much ‘professional’ commentary is dominated by that week’s ‘inside baseball’ nonsense, to the exclusion of how policy effects real lives and how it could be improved. Frontline bloggers make policy real, sometimes uncomfortably so from the perspective of policy wonks – which is probably why their views aren’t usually invited into national policy debates (Guardian Professional Networks is a notable exception, along with parts of the trade press).
We want to put the real insiders where they belong – at the centre of policy. What we’re looking for are practitioners and services users who can provide a real-life perspective on policy – just as BendyGirl does on the reality of welfare. It doesn’t matter if you don’t consider yourself an expert – in fact, we’d prefer it if you didn’t (self-proclaimed ‘expertise’ often denoting an arrogance and insularity from other viewpoints). It doesn’t matter if you don’t know the ‘right’ words, because writing that’s worth reading doesn’t depend on anything other than your proximity to the reality of public and voluntary services. And it doesn’t matter if you can’t write for us every week (you have a life to live and a job to do, after all) – we’d prefer it if you posted when you have something to say and a bit of time to reflect.
If you already blog, we’d love to syndicate you here and hopefully add to you readership. And if you’ve never blogged before, why not give it a go – your voice deserves to be heard as much as anyone else’s. If you’re interested or have any questions, just fill out the form below and we’ll get back to you asap. We can’t pay you – but we can help you to put your name on policy.
This is the tenth in a series of posts on why social policy should be developed by and with the people who use and provide public and voluntary services. We welcome your comments on the whole series.
In this series we’ve suggested that we need a new approach to developing social policy, one that involves the people who use and provide public and voluntary services in the research and development of policy. We’ve put forward a range of benefits that we think this approach would produce – namely policy that is better quality, more implementable, more representative, more inclusive, more timely, more cost-effective, more innovative, and would help to produce the better public services we want. For these reasons, and because it reflects social and technological change, we think this is the future. There’s one last reason to add to this list: it’s the right thing to do.
Public and voluntary services don’t belong to policymakers or policy wonks. Public services belong to all of us. We pay for them, and although it might not always feel like it, we own them – literally if they are publicly provided services, and figuratively if we rely on them. They’re our GP surgeries and hospitals, our schools and nurseries, our police forces and courts. More than this, we are all public services. Co-production reveals that the people who use services are as critical to their effectiveness as the practitioners who deliver them. Indeed, services wouldn’t exist without the people who use them – they’d just be buildings and equipment and staff standing around.
All of which leads to the point that it’s our policy as well – not one person excluded. This challenges some deep-seated (but rarely articulated) notions about politics and policy – about who has the ‘right’ to be involved in policymaking and who is sufficiently ‘expert‘ to be brought into the charmed circle.
Talking about this project with a lot of people over the past few months, we’ve been encouraged by plenty of positive reactions and offers of support. But we’ve also heard some ‘concerns’. These usually start with ‘yes I love the idea of course, but how are you going to…’, followed by one or more of the following:
- …make sure that people will want to be involved;
- …make sure that they will continue to want to be involved;
- …go beyond the ‘usual suspects’ who get involved in anything;
- …manage people who are unmanageable;
- …manage people’s expectations when the world doesn’t change overnight;
- …find money to develop the project when there’s no money around;
- …respond when other think tanks don’t like the idea;
- …react when you realise that no-one actually wants better social policy, rather what they really want is more funding for their prejudices;
- …produce policy given that practitioners and service users can’t write (this was actually said to me);
- …feel when you discover that it’s been done before, and by implication, hasn’t worked.
Some, any or all of these ‘concerns’ might be true. Some of them could be considered patronising to what the media refers to as ‘ordinary people’ (i.e. anyone who doesn’t work in the media or isn’t interviewed regularly by those who do). But ultimately, none of these concerns matter. Even if they were all true, it would still be worth trying to develop a new, more inclusive way to create better social policy – because it’s the right thing to do.
No piece of policy will make everyone happy, but then this project isn’t about policy reflecting what practitioners and the public feel, rather it’s about policy reflecting what they know. It’s about policy research and analysis that engages more of the people who know what they’re talking about because they experience the services and issues at first hand. It’s about examining a problem, developing policy options, evidencing the best option, and considering how this option could be implemented most effectively (the kind of thing that few think tanks actually do that often). Not everyone will be happy with the outcome, but everyone should have the right to contribute to the process.
In the main then, as we’ve suggested throughout this series, this project is about harnessing the practical benefits that we think would derive from the greater involvement in policy work of the people who use and provide public services. But then, even if none of these benefits were realised or realisable, even if there were no other reasons to support this approach, and even if the problems and barriers often seemed insurmountable, we still think it would be worth trying – because it would still be the right thing to do. Join us from 1st June if you agree.