Competitive policy making
Before I explain what some of those might be, letâ€™s be clear on terms. I am not advocating the outsourcing of policy functions and I am not sure Jeremy Heywood was either when he suggested that the Civil Service should lose its policy making monopoly. â€˜Outsourcingâ€™ implies that we are going to give Deloitte or KPMG a massive contract to do climate policy for four years. We can all agree that this is probably a bad idea.
Contestability of policy making is rather different â€“ itâ€™s the idea that a certain amount of the governmentâ€™s policy spending might be up for grabs. This is hardly a new idea: consultancies already play a significant if sometimes controversial role in public policy formation. But that role is usually executed away from the public gaze. I think it should be out in the open and that work should go to a wide range of potential policy advisors. For me, contestability is about pluralism, not privatisation.
So if what Jeremy Heywood meant is that we should make departments bid for some of their policy budget against social enterprises, consultancies, service providers in the public and voluntary sectors, or consortia comprising a number of these, then he might be on to something. Some of the benefits might include:
1. Access to a wider range of expertise â€“ why should ministers limit themselves to what the Civil Service can offer? If a project requires specialist expertise, why rule out the opportunity to hire people with that expertise from outside.
2. Promoting joined up government â€“ set up central budgets held in the cabinet office for strategic priorities, then let departments and others bid for the money to do policy and implementation work. All of a sudden, departments will be bidding to show how effectively they can join up with others, rather than talking a good game but failing to deliver.
3. Improve implementation â€“ if some of the people commissioned to make policy are practitioners (eg the VCS and local government officers) then youâ€™re developing policy that is already embedded in the delivery system. Thatâ€™s got to be a good thing. For an example of it working in action, see page 65 of this Demos report.
4. Upskilling the Civil Service â€“ a little contestability can go a long way towards encouraging civil servants to continuously improve their own skills and ensure that they are in a strong position to win work. At the moment that pressure is sorely lacking.
5. It brings in innovation and creativity: the Civil Service recognises that itâ€™s not good at innovation. Indeed, many civil servants Iâ€™ve interviewed are not sure they should be innovative â€“ their job is to weed out bad ideas, protect ministers and deliver implementable and effective policy. Itâ€™s not to come up with Hilton-esque ideas. So contestability could bring in a different culture.
None of this has to destroy organisational memory or civil service capacity. I would expect that contestable projects would still have some significant civil service involvement as client and probably as participants in cross-cutting teams. Done well, this sort of system could strengthen both policy making and the Civil Service itself.