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.
Welcome to our new website – and if you’re new here, to our project as well.
This is the next stage of what began as the ‘New Think Tank’ project to improve social policy by involving practitioners and the public.
We launched the project on 1st January this year with a blog site and a Twitter feed. Since then we’ve had nearly 13,000 hits on the blog, picked up more than 1,100 Twitter followers, and received national and international media attention. We’ve recruited a project team – and chosen a name that we think expresses what we’re about.
The interest, encouragement and support we’ve received so far has convinced us that there’s the potential here to build a powerful movement of people and organisations who use and provide public services, working together to create better social policy.
But we always said that we wanted to develop this project in a very different way to a traditional think tank – openly, collaboratively and from scratch – in line with our mission to make policy research and development a collaborative activity open to all. This work continues here. Over the next few months we’ll be designing and developing Guerilla Policy in public, and for everyone.
We know already that there are lots of obstacles to making this project a success – financial, technological, organisational, and just the sheer hard graft of creating something new. But the biggest barrier of all, the largely unspoken obstacle, is probably fear – fear that we don’t know as much as the self-proclaimed experts who went to the ‘right’ schools and use the ‘right’ language, fear that we don’t have the right to create better policy, fear that we’ll look foolish and that no-one else will agree with us.
We’ll do our best to make this a place without fear. The rest is up to you – so step-up, make it yours, and join the movement for better social policy.
You can get involved by:
- Posting comments on this blog;
- Visiting our Facebook page (and formerly New Think Tank);
- Connecting with us on LinkedIn (Guerilla Policy);
- And on Google+ (Guerilla Policy);
- Following us on Twitter: @guerillapolicy (and formerly @newthinktankuk).
This is a new series of posts in which we’ve invited people to give us their reactions to the New Think Tank project. First up: Phillippa Rose from Redfront. Thanks to Phillippa for contributing this post, and we welcome your comments.
Last month I was invited to contribute to a branding workshop for the currently described ‘New Think Tank’ – an experiment to develop new ways of making, and influencing public policy, from the ground up.
The notion of a bottom up think tank is in itself a bit of anomaly. People associate think tanks with ivory towers, white cubes, sometimes intimidating, and organisations steeped in high-level thinking, in all senses. Think tanks are associated with thorough research practice, sometimes publishing insights or data which influence policy, and challenging the status quo. They are rarely associated with people actually delivering public services, testing assumptions in the policies of the day. New Think Tank however advocates that “the people who experience the effects of social policy should have the opportunity to help shape it.”
At the branding workshop we looked at driving forces behind the initiative, role play, future scenario setting etc, to get a sense of the driving forces behind New Think Tank, perceptions in the room, and where this thing is going. It was a fascinating afternoon, with 20-30 people with varied views on the subjects raised. The room was made up of people working at the forefront of policy, business, charities, social enterprises. For me there was only one missing link – front line practitioners and service users. I think there was only one person there who worked in social services.
As a service designer, I have found it refreshing to see the New Think Tank testing assumptions online, consistently iterating and revising its approach in response to contributions and feedback in such an open and transparent way. I believe in Minimal Viable Product and Agile Development – trial and error, learning by doing, and involving user input from the very start. For the New Think Tank to be meaningful and make lasting impacts on policy, it needs to move to the next level, to specifically target service users and practitioners, and involve them on key areas to focus on, and practical action.
The concept and the thinking behind New Think Tank is new, exciting, fresh and has the potential to make a significant impact on policymakers, practitioners, and end users, experiencing these services. The messages are strong, the communications channels are established. With the official launch date June 1st, fast approaching now is the time to focus, perhaps one policy area at a time, or one locality at a time, who knows. It’s time to ask the people working with, and using public services.
Phillippa Rose from Redfront has enjoyed over ten years developing strategies, services and projects in the public and private sector. She has special interests in the following areas: innovation, co-creation, talent development and enterprise. At Redfront, Phillippa specialises in user-engagement, strategic partnerships, service innovation and networks.
We held our branding and communications workshop last week – thanks to all those who participated, and we hope you found the discussion as interesting and worthwhile as we did. Thanks especially to Todd and Carl at Fireplough for their great facilitation of the session, it was much appreciated.
The purpose of the workshop was to kick around ideas for the name of the venture (it won’t be called ‘New Think Tank’), based on the purpose, values and ‘personality’ of what we’re attempting to do.
We’d love to hear your ideas as well. Have a look at the presentation here – New think tank 13th April 2012 workshop – which isn’t final by any means but represents part of our current ‘pitch’, then tell us what you think, either by posting a comment below or sending us an email via the Get involved page.
All (nice) suggestions are welcome – no idea is too stupid, as they say – but we want to avoid anything too think tanky (‘institute’, ‘centre’ etc) or too obvious (like ‘frontline‘, which is also a flea spray for pets of course). So get creative and we look forward to your ideas.
I had a conversation today about this project where I spent a fair bit of the time explaining what it isn’t. For example:
- It isn’t a think tank, commonly understood, because it won’t have the infrastructure or staffing or resources associated with think tanks (indeed this is a critical part of the business model);
- It isn’t a competitor to existing think tanks, because we’re looking mainly at a market that doesn’t commission research at the moment;
- It isn’t a research supplier as such, because the point of our approach is that charities and other provider organisations often have much of what they need in order to conduct policy work already (credibility, experience and expertise, relationships to stakeholders etc).
I don’t mind having to take this ‘isn’t’ approach – though it does make what we’re doing sound more negative than I’d like – but obviously it begs the question of what this is.
One of the difficulties with innovation (if I can call this an ‘innovation’) is describing what you’re doing in a simple, easily-graspable way for others, when by definition it’s something new, and at the same time as you’re still exploring for yourself and potential customers what the ‘is’ is. This is why you find yourself using more ‘isn’ts’ than you’d like (and hedging these often makes it even murkier: “Well, not exactly, it isn’t quite like so-and-so…” etc etc).
One way that anyone developing anything ‘new’ tries to get around this is to compare their ‘it’ to some existing products and services (‘it’s like x but for y’). Or they cite examples of things we’d all like more of and then suggest that their product or service will produce these things more cheaply and easily. We’ve done both of these at various times here. We’ve suggested that it’s like ‘Sourceforge [but] for social policy‘ and that we’d like what we’re doing here to support the production of many more user-led Spartacus-like reports.
Both of these approaches keep some of your options open – but only for a while. (And after all, what does it really mean to claim, as thousands of entrepreneurs must have done over the past few years, that they’re developing ‘the new Facebook, but for [insert niche but potentially profitable audience here]’? And if it’s so much like Facebook, minus of course the hundreds of millions of dollars of investment in functionality that Facebook and its investors have made, then why wouldn’t your target audience just use Facebook instead?)
Inevitably you begin to approach the point when you have to say ‘this is what it is’, in order to give potential partners enough to provide you with an honest response about whether it meets a real need they have – in short whether they’re in or not. But you resist this because you also have to give something up: the idea that your project appeals to everyone or could ever appeal to everyone. Promise and potential (which are nice things that everyone can buy into) has to give way to practical appeal (which of course means a much smaller audience of actual buyers). In this sense, the more you define what it is, the more you make it something that isn’t for some (probably most) of your potential audience.
We’re getting nearer to this point – but we’re not there quite yet.