It is not every post you will read which links the choice of web domain name to the results of the civil war, but it is characteristic of this one that that’s exactly what it does. If you are interested in the arcane minutiae of parliamentary structure, this post is for you. But behind the specific points, there is something much more generally significant which should interest everybody, including those who, inexplicably, are not fascinated by parliamentary minutiae.
Computers crystallise systems. That’s fine for as long as the crystallised form remains valuable – and sometimes that can be quite a long time. But it’s not at all fine for systems which need to retain flexibility and adapt to changing circumstances – and that’s quite a lot of systems.
The lack of a fixed, exhaustive ruleset means Parliament is open to exaptation and adaptation. It is evolutionary by design. It is not brittle. It can sway in winds. Computers on the other hand are really not like this. They tend to prefer defined rulesets. They are deterministic. They are dumb. They are brittle.
So the question becomes whether we can get brittle computers to support systems which are not brittle. And that’s a question which matters much more widely than just for parliament.
Eddie Copeland – NESTA
This simple and powerful set of slides does an extraordinarily good job of summarising the key issues in digital transformation, not least in being really clear about the extent to which all of this is a technology issue (not as much as it looks) as opposed to an everything else issue (much more than it first appears). The section on ‘deciding how you want to work’ gets twice as many slides as ‘thinking about your technology needs’, which is a pretty strong indicator of the approach being taken.
It’s certainly possible to challenge some of the details. The arresting assertion that ‘we can broadly take for granted that technology can do whatever we want it to do’ perhaps has more power than precision – though the slightly lesser claim the technology needed to support government processes already exists is indeed a useful reminder that appeals for technological exceptionalism are very likely to be misguided. The insistence that agile projects can’t succeed in organisations which retain traditional approaches to funding and governance is both wrong and unhelpful: wrong because there are plenty of example of where it has succeeded, and unhelpful because every organisation has to start somewhere, and if agile can’t work at all unless everything is agile, there is effectively no way of making that start.
Overall, though, the strengths far outweigh the weaknesses – and this is a beautiful example of doing the hard work to make things simple. As a further bonus, the slides are open for comments, and have already sprouted a rich set of observations from Matthew Cain.
Martin Stewart-Weeks – The Mandarin
If it is hard to think and act systemically about the long term, it’s also worth reflecting on patterns of behaviour which get in the way even of the attempt. The rhetoric of innovation, of openness, of fearless honesty runs into a reality which seems designed to punish and constrain precisely those behaviours. And of course ‘design’ is precisely the wrong word here: these characteristics are emergent rather than intended (which does not, of course, mean that it would be impossible to design them to be different). There are many reasons why that is an unfortunate state of affairs, one which is rightly given some emphasis is that it risks crowding out the strategic and the systemic:
The real dilemma is that we’re so busy honing the efficiency of the pieces that we’ve failed to work out how to put the puzzle together or work out what the puzzle is or should be.
Pia Waugh – Pipka
This is a characteristically excellent post, examining in some detail both what it takes for change to succeed and, perhaps even more importantly, how to scale it.
The short answer is that if you want to change the system, you have to change the system. And to do that on the fifty plus year scale which is the level of ambition behind this post, requires rigour and discipline. Five questions are set out, including the two which are the most critical: what future do you want? And what are you going to do today?
Scaling from an idea of the future to systematic government and national level change can’t be done by exhortation – and simple observation suggests can only with the greatest difficulty be done at all. The recommendations here are an intriguing mixture of the very slow burn (supporting long term varied career development, to reduce aversion to new thinking) to the much more immediate (mandating the use of user research in funding bids).
All that still leaves the question of how best to start this whole process, but this is a manifesto of what should be done, or rather how it should be done; it doesn’t purport to be a set of instructions for making it happen.
Gavin Starks – NESTA
This is an interesting report which asks almost the right question. Government is at little risk of losing its mind, or its short term memory. The two better questions – which in practice are the ones this report starts to address – are whether government can stop losing its longer term memory, and how the power of the government’s mind can be enhanced by better ways of connecting and amplifying its component parts.
Those are important questions. It’s already all too easy to forget how long we have been worrying about the ease of forgetting things. Aspects of the problem have been recognised, and solutions attempted, since the earliest days of what we no longer call electronic government. None has been more than partially successful.
The two questions are also closely related. People are reluctant to incur even the smallest overhead in storing things for the benefit of posterity, so the benefit needs to come from improving the effectiveness of current work. Conversely, tools which facilitate collaboration, sharing and serendipity will often (though with some very important exceptions) also be tools which facilitate the storage and discovery of what has been created. That was one of the key themes of a series of blog posts I wrote a couple of years ago, which covered some (though by no means all) of the same ground – including the observation, echoed in this report, that the web was invented to be an intranet and knowledge management tool; the world wide bit came rather later.
Where this report adds to the debate is in its more explicit recognition not just that we need to be thinking about texts rather than documents, but that a lot of what we need to be thinking about isn’t conventional text in the first place, making the paginated document an even less useful starting point for thinking about all this.
And there is a delicious irony that this blog – and my blogging generally – exists in large part to serve as my outboard memory, now with well over a decade of material created in part as protection against the weaknesses of institutional knowledge preservation.
Beyond even the bonus points for talking about laws being ‘intertwingled’, this is an important and interesting post at the intersection of law, policy and automation. It neatly illustrates why the goal of machine-interpretable legislation,such as the recent work by the New Zealand government, is a much harder challenge than it first appears – law can have tacit external interpretation rules, which means that the highly structured interpretation which is normal, and indeed necessary, for software just doesn’t work. Which is why legal systems have judges and programming languages generally don’t – and why the New Zealand project is so interesting.
Nadia Webster – NZ Digital Government
The rather dry title of this post belies the importance and interest of its content. Lots of people have spotted that laws are systems of rules, computer code is systems of rules and that somehow these two fact should illuminate each other. Quite how that should happen is much less clear. Ideas have ranged from developing systems to turn law into code to adapting software testing tools to check legislative compliance. This post records an experiment with a different approach again, exploring the possibility of creating legislative rules in a way which is designed to make them machine consumable. That’s an approach with some really interesting possibilities, but also some very deep challenges. As John Sheridan has put it, law is deeply intertwingled: the meaning of legislation is only partly conveyed by the words of a specific measure, which means that transcoding the literal letter of the law will never be enough. And beyond that again, the process of delivering and experiencing a service based on a particular set of legal rules will include a whole set of rules and norms which are not themselves captured in law.
That makes it sensible to start, as the work by the New Zealand government reported here has done, with exploratory thinking, rather than jumping too quickly to assumptions about the best approach. The recommendations for areas to investigate further set out in their full report are an excellent set of questions, which will be of interest to governments round the world.
Jennifer Guay – Apolitical
To describe something as ‘policy based evidence making’ is to be deliberately rude at two levels, first because it implies the use of evidence to conceal rather than illuminate, but secondly because it implies a failure to recognise that evidence should drive policy (and thus, though often less explicitly, politics).
Evidence based policy, on the other hand, is a thing of virtue for which we should all be striving. That much is obvious to right-thinking people. In recent times, the generality of that thought has been reinforced by very specific approaches. If you haven’t tested your approach through randomised controlled trials, how can you know that your policy making has reached the necessary level of objective rigour?
This post is a thoughtful critique of that position. At one level, the argument is that RCTs tell you less than they might first appear to. At another level, that fact is a symptom of a wider problem, that human life is messy and multivariate and that optimising a current approach may at best get you to a local maximum. That is of course why the social sciences are so much harder than the so-called hard sciences, but that is probably a battle for another day.
Paul Clarke – honestlyreal
On a morning where transport is disrupted across the UK by snow and cold winds, it’s worth returning to this post from a few years ago, which explains why small amounts of snow here are so much more disruptive than the much larger amounts which are easily managed elsewhere. In short, the marginal cost of being ready for severe weather, when there isn’t very much of it, isn’t justified by the benefits from another day or two a year of smooth operations. That is a very sensible trade off – the existence of which is immediately forgotten when the bad weather arrives.
It’s a trade off with much wider application than snow-covered railway tracks. Once you start looking, it can be seen in almost every area of public policy, culminating in the macro view that everybody (it is asserted) wants both lower taxes and better services. Being more efficient is the way of closing the gap which is simultaneously both clearly the right thing to do and an excellent way of ducking the question, but at best shifts the parameters without fundamentally changing the nature of the problem. Hypothecation is a related sleight of hand – let’s have more money, but only for virtuous things. In the end, though, public policy is about making choices. And letting the trains freeze up from time to time is a better one than it appears in the moment to the people whose trains have failed to come.
The Yorkshire Ranter
This is a follow up to a post covered here a few days ago which looked critically at outsourcing, starting from the fundamental question first posed by Coase on what organisations should do and what they should buy. This second post is at one level a short summary of the first one, but it’s also rather more than that. It puts forward a slightly different way of framing the question, making the point that time and uncertainty are relevant to the decision, as well as pure transaction cost narrowly defined.
There are transactions, which are in the moment, and imply no further commitment or relationship. There are contracts, which are a commitment to future transactions, and depend on shared assumptions about the future conditions in which those transactions will happen. And there are organisations, which exist in the space beyond contractual precision and certainty.
To complete the hat trick, there is also a separate post applying this thinking to Capita. Even for those less interested in the company, it’s worth reading to the end to get to the punch in the punchline:
In important ways, this is the service that Capita provided and still provides: the ability to blame problems on computers and computer people, while ignoring the physical reality of policy
The Yorkshire Ranter
Organisations, including governments, follow fashions. Some of those fashions change on short cycles, others move more slowly, sometimes creating the illusion of permanence. The fashion for outsourcing, for buying rather than making, has been in place in government for many years, but there are some interesting signs that change may be coming. One immediate cause and signal of that change is the collapse of Carillion, but that happened at point when the debate was already beginning to change.
This post goes back to the roots of the make or buy choice in the work of Ronald Coase on the nature of the firm. The principle is simple enough, that it makes sense to buy things when the overhead of creating and managing contracts is low and to make them when the overheads are high. The mistake, it is argued here, is that organisations, particularly governments, have systematically misunderstood the cost and complexity of contract management, resulting in the creation of large businesses and networks of businesses whose primary competence is the creation and management of contracts.
One consequence of that is that it becomes difficult or impossible to understand the true level of costs within a contractual system (because prices quickly stop carrying that information) or to understand how the system works (because tacit knowledge is not costed or paid for).
All very thought provoking, and apparently the first in a series of posts. It will be worth looking out for the others.