You may be familiar with WhatDoTheyKnow, our website which simplifies the process of making a freedom of information request.
mySociety also provides the underlying software as a service for councils: it sits on the council website, templated and branded to fit their site’s style. When someone submits a request, it goes directly into the council’s own back-end processes.
Just like WhatDoTheyKnow, the system publishes all requests, and their answers, online. This helps the council show a commitment to transparency – it also has the effect of cutting down on duplicate requests, since users can browse previous responses.
Brighton and Hove Council are the first council to implement the software.
Now, ordinarily, when we sign off a new project for a client, we write up a case study for our blog. But this time, we were delighted to read an interview by Matt Burgess on FOI Directory, which has done all the hard work for us. With Matt’s permission, we are reproducing the piece in full.
The number of Freedom of Information requests public authorities receive is generally rising and central government dealt with more requests in 2012 than in any year since the Act was introduced. One council has decided to try and open up access to their requests using custom software from mySociety.
Brighton and Hove City Council have implemented a custom version of the popular WhatDoTheyKnow website where more than 190,000 requests have been made.
The council hope it will allow others to easily browse requests that have been made and make them more accountable.
We spoke to council leader Jason Kitcat about why the council decided to implement the new system – which was soft-launched at the beginning of November.
Why did you decide to implement the new system?
JK: I personally, and we collectively as a Green administration, believe passionately in openness and transparency. That’s the primary motivation. So digital tools to support making it easier for citizens to access council information I think are strongly in the interest of our city and local democracy.
We also were seeing an increase in the number of FOI requests, many of them similar. So using a system like this helps people to find the information that’s already published rather than submitting requests for it, when it’s actually already been published.
How does it work?
JK: It’s a customised version of the mySociety WhatDoTheyKnow site, delivered by mySociety for us in the council’s branding. It allows anyone to submit their FOI request in a structured way through the web and others can see the requests and any responses. The requests are linked in with the main WhatDoTheyKnow site to help further reduce duplication of requests and enable consistent commenting.
Behind the scenes it also offers workflow management to assist the council team who are responding to the requests.
What benefits will the system have to those answering and making FOI requests?
JK: It opens up the process, helps others to see what is going on even if they aren’t making requests themselves. Particularly important is that it by default puts requested information out there on the web without any more effort by the council or those making the requests.
Were there any obstacles in setting the system up and how much did it cost the council?
JK: Obstacles were mainly stretched resources within the council to prepare for the changed workflow, making sure our information governance was ready for this and that our web team could support the minor integration work needed.
Given this is a web-based ’software as a service’ offering it’s pretty straightforward to implement in the grand scheme of things. I don’t have the final costs yet as we’ve been doing some post-launch tweaks but, as is the way with nimble organisations like mySociety, I think pricing is very reasonable.
Do you think it will improve the council’s performance in responding to FOI requests and make the council more transparent to the public?
JK: Yes absolutely. Not only will the council’s FOI performance be more publicly accountable but I’m hoping we can reduce duplicate requests through this so that our resources are better focused.
Would you say it has been worth creating and why should other public authorities follow suit?
JK: Yes it’s worth it. I think we as councils have to be ever more open by default, use digital tools for transparency and relentlessly publish data. I believe this will result in better local democracy but also is one of the ways we can truly challenge cynicism in the whole political system.N.B.: The website current shows a large number of requests that appear to be unanswered. We asked about these and it includes the number of historic requests that were loaded into the site.————————————Many thanks to Matt of FOI Directory for allowing us to reproduce this interview in full.
When we built FixMyStreet in 2006, our primary focus was to create a tool for citizens. We wanted to make it easy, quick, and effective to report street problems, even if the user had no prior knowledge of where their reports should go. And while the tool obviously had to work for the councils who were receiving reports, it never crossed our minds to research, or try to key into, prevailing council strategies.
But over the last few years, and to the benefit of both sides, council strategy has become strongly aligned with several of the qualities that FixMyStreet was founded on. The development of our specialised software, FixMyStreet for Councils, cemented that further, based, as it is, on consultation with local authorities.
If your current strategy focuses on any or all of the following points, then FixMyStreet is extremely well-positioned to help you.
UK local authorities are fully aware of the channel shift theory by now: put reporting online, make it self-service, and see efficiency rise while costs fall.
It sounds simple, but it hinges on one important factor – you have to get the reporting interface right. Otherwise, all those hassle-free online transactions turn into irate residents on the phone, seeking help.
On first impressions, many assume that FixMyStreet is just a public platform for grumbling – so it can be quite a surprise to discover that it often has the opposite effect. By allowing everyone to see what the problems are in their own community, it provides a platform for engagement, debate – and, sometimes, solutions.
FixMyStreet is a superb tool for councils who are looking for ways to encourage residents to take a stake in their own communities.
Any council web team worth its salt will be anxious to maximise usability across the website. FixMyStreet was designed with the user at its heart: from minimising the number of clicks it takes to make a report, to making sure that every step is as easy and comprehensible as possible.
Modern society is demanding transparency across a vast array of organisations, not least government. By putting a record of every report online, FixMyStreet helps you fulfil those demands. And there are side benefits, too.
First, FixMyStreet brings previously ‘hidden’ work into the open, allowing your residents to understand the degree and quantity of work you do on their behalf.
And second, having reports online allows citizens to see at a glance whether their problem has already been reported, thus cutting down on duplicates – and saving you time.
FixMyStreet is efficient when used on a desktop; it also works very easily on mobile devices, meaning that your residents help you crowd-source information. You’re effectively multiplying your inspection capabilities by a factor of hundreds, and your residents become your ‘eyes and ears on the ground’, as one of our client councils has said.
Find out more
Drop us a line now and we’ll get right back to you.
Image credit: Dennis Skley (cc)
FixMyStreet.com has always tried to make it as simple as possible to report a street problem. When we built FixMyStreet for Councils, we wanted to simplify things for local authority employees too.
So, as well as offering the option to integrate with council back-end systems, we also put together this nifty dashboard (right – click to see full-size). It’s one of several extra features councils get when they purchase the FixMyStreet for Councils package.
What do councils need?
- At-a-glance statistics, for all kinds of reporting. Perhaps the local newspaper have asked how many potholes have been fixed this year, or internal staff need a report on which types of problem are most rapidly fixed.
The top half of the dashboard allows for this sort of analysis. The drop-down category list means you can filter the view to show one category of problem – say, fly tipping – or all of them. Results are shown across a variety of timeframes.
FixMyStreet for Councils allows councils to designate their own progress statuses, beyond our standard ‘fixed’ and ‘open’. So, in this case, the statuses include ‘in progress’, ‘planned’, ‘investigating’, etc. Each of these is shown separately.
- A realistic picture of how long it takes to deal with issues. The ‘average time to council marking as fixed’ is a great measure of just how much time it is taking to get reports resolved.
Perhaps just as important, though, is the ‘average time to first council state change’ – that could just mean the report has been acknowledged, or that its status has changed to ‘under investigation’ – but these are still valuable mileposts for keeping residents informed of progress.
- Quick access to problems, as they’re reported. At the foot of the dashboard, there are links to all problems reported within the council boundaries.
There’s an option to filter them by any of the statuses, as above.
- Access for multiple people, in different locations. The dashboard is web-based, so it can be accessed by any employee with internet access – or several at once.
- But at the same time, complete security. It’s password-protected, so it’s only accessible to those who have been granted access.
- A responsive provider. mySociety believe that the launch of new software is only the beginning of the story.
When people start using new products, they often do so in surprising ways. They often ask for features that would never have occurred to us, and indeed might never have previously occurred to them.
We will remain in active development, of the dashboard, and of FixMyStreet for Councils as a whole. We’ll be soliciting feedback, and listening to it very carefully.
The FixMyStreet for Councils dashboard is only available to councils as part of our FixMyStreet for Councils package – find out more here.
Over the last 6 months or so, mySociety has been doing increasing amounts of work with local councils, not only helping them with problem reporting and online petitions, but also advising them on the impact of digital by default and how changing customer expectations are affecting digital service provision. To paraphrase Tom, for an ever-increasing number of customers, “local councils don’t have websites, local councils are websites”.
More specifically, we’ve been helping councils use user-centred techniques to kick-start the process of digital transformation: taking existing services that cause unnecessary frustration, figuring out how they should work for the customer in an ideal world, identifying the process changes needed, and helping make them happen.
How do you know where to start?
Most consultancies in this area will publicise their patented 5-step approach, or shower you in platitudes about talking to users and involving service managers, but I thought it would be more useful to walk through in detail what we actually do on a project like this. In this post, I’m going to describe only the first step (I’ll talk about others in future posts): given all the stuff that councils do, how do you know where to start?
Clearly, not every council service is susceptible to digital transformation. If you work in children’s services or benefits advice, your service is more likely to rely on cups of tea and conversation than on your website. But there are high volume transactions that involve exchanges of information or of money that do not, or rather *should not*, require any human intervention. Unfortunately, because of mistakes in how websites are structured and processes organised (that often go right back to decisions about management structure and procurement priorities), unnecessary demand is placed on contact centres.
What are your users trying to do?
So if you want to know what mistakes you’re making with your online presence, the first place you should look is the volume of calls to your contact centres and what questions the callers are asking. Here’s a complete list of all the places you can look for useful data on what your customers are actually trying to do and what you might be doing wrong:
- Contact centre logs: the records of what people who call you are actually asking about. This is the best place to look to identify the areas where your web presence is under-performing.
- Internal site search terms: the things people type in most often in the search box on your website. Generally speaking, use of search on a website is an indicator that your navigation and page structure have failed. Therefore the search terms people use on your site are another very interesting indicator of things you’re not doing well enough.
- Referring search terms: the most frequently used search terms that drive traffic to your website. What are people looking for and what words have they actually put in to Google (or indeed any other search engine) for to arrive at your website?
- Popular pages: data on the most frequently visited pages and sections of your website doesn’t tell you what you should improve or how, but it does give you a feel for where the demand is.
If you look at all of those things, you’ll have a lot of data to go through and make sense of. If you’re short on time, focus on the first one – it’s the juiciest source of insights.
Talking to service managers
Another approach we pursue in parallel to this one is to talk to a group of service managers and ask them for their opinions: if the decision on where we should focus our redesign efforts was up to them, what single thing should we start with that would make the biggest difference? How this actually happens in practice is that we get a group of people in a room together and ask them to write down (almost certainly on post-it notes) the top 3 – 5 services that they think are in need of a digital redesign. We then discuss and consolidate all of these before grouping them, trying to identify those that are the most susceptible to automation and where the complexity of the change needed internally is low enough to be approachable.
The final part of figuring out where to start is to make a decision: which of these areas are you going to start redesigning first? You now have two sources of data on where to start: the results of your analysis of customer behaviour and the views of your employees who are closest to the action. Here we’ll make a recommendation, but leave the final decision to our council client: they know their organisation a lot better than we do.
With a focal point for the transformation efforts decided on, so begins the daunting-yet-exciting task of researching and designing the changes to be made: the bit where you actually talk to users, make prototypes or mockups of what the service’s digital touchpoints should look like (no specification documents here please) and then figure out together what process changes need to be made for it all to work in practice. Which, of course, are the topics for future blog posts.
This is the third of our recent series of Open311 blog posts: we started by explaining why we think Open311 is a good idea, and then we described in a non-techie way how Open311 works. In this post we’ll introduce our proposed extension to Open311, and show how we use it in FixMyStreet.
The crux of our suggested improvement is this: normal people want to know what has happened to their problem, and Open311 currently isn’t good enough at telling them whether or not it has been dealt with. To be more specific, our additions are all about reports’ status change, by which we mean something like this:
I just totally fixed it.
That’s robot-311 from the previous post, if you’ve dropped in here without reading the previous posts. Once again we’re blurring the distinction between client and user (the girl you’ll see below) a little, to make things simpler to follow.
Every month in the UK, thousands of problems are reported on www.fixmystreet.com and, moments later, sent on to the councils who will fix them. Here’s what happens with a problem report for something like a pothole or a flickering streetlight:
- You create the report on FixMyStreet.
- FixMyStreet sends that report to the right department at the right council.
- That body puts it into its own back-end system.
- Later, when the council fixes the problem, FixMyStreet is updated, and everyone knows it’s fixed.
On the face of it, you might think we need only care about 1 and 2. But really, FixMyStreet isn’t just about dispatching reports, it’s about helping to get things like potholes actually fixed. And neither citizens nor local governments benefit if work gets done but nobody finds out about it – which is part 4 on the list above.
What do we mean by “status change”?
The example at the top of the page shows the robot effectively changing a problem’s status to “fixed”.
Actually, statuses can be simple, such as either OPEN or CLOSED, or more detailed, such as “under investigation”, “crew has been dispatched”, “fixed”, and so on. But since we’re only concerned here with the status changing, that specific vocabulary deployed doesn’t really matter – it can be anything.
In situations where FixMyStreet is not integrated with council systems (i.e we just send email problem reports) FixMyStreet problems still frequently get marked as fixed, because anyone can change the status of a report just by visiting the page and clicking the button. Obviously, though, we prefer to have FixMyStreet directly connected to the local government back-end databases, so that news of a fixed report can be automatically bubbled from the back-office up into FixMyStreet and out onto the net.
And here’s where the problem lies: Open311 doesn’t quite support this business of getting problem updates from the back office out to the public. So first, we’ll show you how it can be done today, using Open311, and we’ll explain why this isn’t a good option. Then we’ll show our preferred solution, which we’ve proposed as an extension.
Looking at everything just to spot one change (bad)
One way to notice if any problems’ statuses have changed is to use Open311 to ask for every single service request, and see if any of them have a different status since the last time you checked.
Tell me all the service requests you’ve ever received
request 981276 the pothole on the corner by Carpenter Street is now CLOSED (I filled in the pothole)
request 988765 the pothole by bus stop on Nigut Road is now CLOSED (I filled in the pothole)
request 998610 gaping hole at the end of Sarlacc Road is now OPEN (the pothole fell through)
request 765533 where the street was cracked outside Taffey’s Snake Pit is now CLOSED (I filled in the pothole)
. . .
continues for thousands of requests
Um, OK. Now I’ll look at all these and see if any have changed since I last asked *sigh*
Obviously there are some problems with this. Even though Open311 lets you ask for quite specific service requests, you have to ask for all of them, because by definition you don’t know which ones might have changed. Remember, too, that problems can potentially change status more than once, so just because it’s been marked as CLOSED once doesn’t mean it won’t become OPEN again later. This exchange is very wasteful, very slow and ultimately (with enough reports) may become de facto impossible.
Asking for just the changes (good)
So here’s a better way of doing it. We’ve actually been doing this for some months, and now seems the time to share.
The client asks the server for just the updates on a regular basis, so any requests that have recently changed get updated on FixMyStreet automatically, usually just a few minutes later.
Have you changed the status of any of service requests today?
Yes, request 981276 was CLOSED at 3 o’clock (I filled in the pothole)
Or, more practically for keeping FixMyStreet up to date:
Have you changed the status of any of service requests in the last 15 minutes?
This is handled by our extension to Open311,
GET Service Request Updates. There’s also an optional equivalent call for putting updates into the server (
POST Service Request Update), which would apply if the client changed the status after the service request had been submitted.
Note that the server identifies the problem with its own reference (that is,
981276is the council’s reference, not a FixMyStreet ID, for example). This is important because not all these requests necessarily came from this particular client. Remember that all service requests are available through the Open311
GET Service Requestscall anyway (as shown above). So the server doesn’t send each service request back in its entirety: just its ID, the new status, when it changed, and a brief description.
In practice the client wouldn’t usually ask for “today”. In fact, we typically send a request asking for any updates in the last 15 minutes, and then at the end of the day ask for the whole day’s updates, just to check none were missed.
The technical bit
From a client’s point of view, this is simply an extra call like others in the Open311 API. So it’s just a request over HTTP(S) for XML (or JSON, if required).
We deliberately make the client poll the server for updates and pull them in, rather than expecting the server to push updates out. This frees the server from any obligation to track which clients (for there may be more than just one) care about which updates. The requests themselves are sent with unique IDs, allocated by the server, so the client can dismiss duplicates. It’s also robust in the event of connection failures, so if there are timeouts or retry logic, that’s for the clients to worry about, not the server. Basically, this is all to make it as light on the server as possible: the only real issue is that it must be able to provide a list of updates. This usually means adding a trigger to the database, so that when a problem’s status is updated a record of that update is automatically created. It’s the table of those “service request update” records that incoming requests are really querying.
Is that it?
Yup, that’s it.
This extension is in addition to the Open311 specification — it doesn’t break existing implementations in any way. Obviously this means FixMyStreet’s Open311 implementation is compatible with existing Open311 servers. But we hope that others working on Open311 systems will consider our extension so that clients are kept better informed of the status of the problems being fixed.
Why are statuses so important that it is worth extending the Open311 spec?
mySociety didn’t originally build FixMyStreet because we wanted to get potholes fixed. We built it because we wanted nervous, politically inexperienced people to know what it felt like to ask the government to do something, and to be successful at that. We wanted to give people the buzz of feeling like they have a bit of power in this world, even if the most tiny amount.
If the government fixes a problem and the citizen doesn’t find out it’s a double loss. The citizen becomes disillusioned and weakened, and the government doesn’t get the credit it is due. Everyone loses. We think that Open311 is a key mechanism for making large numbers of people feel that the government does respond to their needs. It just needs a bit of an upgrade to do it better. We hope very much that the wider community tests and endorses our extensions, and it can be folded in to the next official version of the Open311 standard.
In the previous blog post we explained why we think Open311 is a good idea. In this post we’ll explain what it actually does.
Open311 is very simple, but because it’s fundamentally a technical thing it’s usually explained from a technical point of view. So this post describes what Open311 does without the nerdy language (but with some nerdy references for good measure). At the end there’s a round-up of the terms so you can see how it fits in with the actual specification.
We’re using an unusual example here — a blue cat stuck up a tree — to show how applicable Open311 is to a wide range of problems. Or, to put it another way, this is not just about potholes.
So… someone has a problem they want to report (for this discussion, she’s using a service like FixMyStreet).
There’s one place where that report needs to be sent (in the UK, that’s your council). That administrative body (the council) almost certainly has a database full of problems which only their staff can access.
I have a problem :–(the “client”
I fix problems!the “server”
In this example, FixMyStreet is an Open311 client and the council is an Open311 server. The server is available over HTTP(S), so the client can access it, and the server itself connects to the council’s database. In reality it’s a little bit more complicated than that (for now we’ll ignore clients that implement only part of Open311, multiple servers, and decent security around these connections), but that is the gist of it.
Although it’s not technically correct to confuse the client with the user, or the server with the council, it makes things a lot easier to see it this way, so we’ll use those terms throughout.
To start things off, the client can ask the server: what services do you provide?
Until the client has asked the server what problems it can fix, it can’t sensibly request any of them.
What services do you offer?
POT: fix potholes
TELE: clean public teleports
PET: get pets down from trees
JET: renew jetpack licenses …
FixMyStreet can use the response it gets from such a service discovery to offer different categories to people reporting problems. We actually put them into the drop-down menu that appears on the report-a-problem page.
In the Open311 API, this is handled by
GET Service List. Each service has its own
service_codewhich the client must use when requesting it. Note that these services and their codes are decided by the server; they are not defined by the Open311 specification. This means that service discovery can easily fit around whatever services the council already offers. The list of services can (and does) vary widely from one council to the next.
Some services require specific information when they are requested. For example, it might be important to know how deep a pothole is, but it’s not relevant for a streetlight repair.
Tell me more about the PET service!
I can get pets down from trees, but when you request the service, you *must* tell me what kind of animal the pet is, OK?
In the Open311 API, this is handled by the
GET Service Definitionmethod. It’s not necessary for a simple Open311 implementation. In fact, it only makes sense if the service discovery explicitly told the client to ask about the extra details, which the server does by adding
metadata="true"to its response for a given service.
Requesting a service
This is where it gets useful. The client can request a service: this really means they can report a problem to the server for the body to deal with. Some submissions can be automatically rejected:
My hoverboots are broken :–( I need BOOT service!
404: Bzzzt error! I don’t fix hoverboots (use service discovery to see what I *do* fix)
Hey! Blueblue is up a tree! I need PET service (for cats)!
400: error! You forgot to tell me where it is.
If the report is in good order, it will be accepted into the system. Open311 insists that every problem has a location. In practice this is usually the exact position, coordinates on planet Earth, of the pin that the reporter placed on the map in the client application (in this case FixMyStreet.com).
I need PET service (for cats)! Blueblue is stuck up the biggest tree in the park :–(
200: OK, got it… the unique ID for your request is now 981276
In the Open311 API, this is handled by
POST Service Request. You need an API key to do this, which simply means the server needs to know which client this is. Sometimes it makes sense for the server to have additional security such as IP address restriction, and login criteria that’s handled by the machines (not the user).
Listing known requests
The server doesn’t keep its reports secret: if asked, it will list them out. The client can ask for a specific report (using the ID that the server gave when the report was submitted, for example) or for a range of dates.
Did anyone ask you for help yesterday?
Yes, I got two requests:
request 981299: TELE dirty teleport at the cantina (I’m waiting for a new brush)
request 971723: POT pothole at the junction of Kirk and Solo (I filled it in)
In the Open311 API this is handled by
GET Service Request(s). The client can indicate which requests should be listed by specifying the required service request id, service code, start date, end date or status.
Does Open311 work?
Oh yes. On the Open311 website, you can see the growing list of places, organisations, and suppliers who are using it.
The technical bit
In a nutshell: Open311 responds to HTTP requests with XML data (and JSON, if it’s wanted). There’s no messing around with SOAP and failures are reported as the HTTP status code with details provided in the content body.
You can see the specification for Open311 (GeoReport v2). It doesn’t feature blue cats, but if you look at the XML examples you’ll be able to recognise the same interaction described here. And remember the specification is an open standard, which means anyone can (and, we think, should) implement it when connecting a client and server in order to request civic services.
In the next blog post we’ll look at how FixMyStreet uses Open311 to integrate with local council systems, and explain why we’re proposing, and utilising, some additions to the Open311 specification.
Illustrated especially for us by René Carbonell.
The Internet has thrown up a host of challenges for governments, large and small. Most people are familiar with the problems presented by issues like hacking, but there is another challenge which probably worries local governments just as much.
The challenge is this – how can a local government cheaply and efficiently cope with the fact that the public wants to request many services through a rapidly expanding plethora of different channels – phones, websites, email, apps, and Twitter? And how can it keep control of costs when new channels are being invented all the time?
The good news is there’s an answer that can prevent each new channel leading to ever-greater costs – a free technology called Open311. The bad news is not many people know it exists, let alone how to use it, or how it works.
In this post, and two more to follow, we’ll explain how Open311 can help governments (and citizens), how it functions, and what mySociety is doing to make Open311 work a bit better.
Background – the status quo
At mySociety, we’ve been running services for years that send messages of different kinds to government bodies, on behalf of our users. Since the very beginning we’ve always been keen that any public servant or politician who receives a message via one of our systems gets it in a familiar form that doesn’t require any special knowledge or training to read or reply to. That’s why for the first few years FixMyStreet sent all its problem reports via email, WhatDoTheyKnow sent all its FOI requests via email, and WriteToThem sent all its letters to politicians via email and fax (remember fax?).
However, despite the fact that reading and responding to emails doesn’t require governments to procure any new technology or any new skills, these days this approach can clearly be bettered. Today, an email report of a broken paving slab will typically be received by a public servant working in a call centre. This person will normally cut and paste text from the email into a new database, or into a new email, before dispatching it for someone else to consider, and action.
Now, imagine that instead of this, a problem report about a broken paving slab could be sent directly from a citizen and placed into the electronic to-do list for the local government team who fix paving slabs. This would do more than just cut costs – it would make it much easier for the citizen to get sent a notification when their problem is marked as ‘resolved’ in the official database.
This is not an original idea. The team at mySociety are not the only people who think that enabling citizens to directly slot requests, messages and problem reports into local government ‘to do’ databases is desirable. In the USA a group of civic minded technologists at OpenPlans were concerned by the same issue. They decided to do something about it – and they launched a project under the banner of Open311.
In the USA a number of cities have non-emergency government telephone helplines, accessible at the phone number 311. As a consequence ‘311’ has come to refer to more than just a phone line – it has come to mean the entire process of handling service requests from citizens around a whole range of non-emergency issues, from garbage to noisy neighbours.
To the ears of some American public servants the name ‘Open311’ consequently conjures up an image of a better, nicer more ‘open’ way of handling such non-emergency requests from citizens.
So what is Open311?
Beyond a brand, what is Open311? The answer is simple: Open311 is standardised way for computers to report problems (like potholes or fallen trees) to the computers run by the bodies that can fix them (like local governments or city departments). It’s an open standard that was started by the lovely people at OpenPlans, and which is now slowly iterating with the help of people inside and outside of governments.
In other words, Open311 is the mechanism through which citizens can slot their service requests directly into the computerised ‘to do’ lists of local government staff, and the way they those citizens can get back progress updates more quickly and easily.
Why is an Open Standard a good thing?
An open standard is just a way of communicating that anyone can implement it, without paying any money for permission to use the technology. The good thing about open standards is that once several technology systems start using the same ones, different systems from different manufacturers can talk to each other. When you phone someone else’s telephone, you are using an open standard – this means you don’t have to have the same brand of phone as the person at the other end.
What this means for a government is that if you can make your database of pothole reports speak to the outside world using Open311 then you don’t have to worry if reports are coming from two, ten or a thousands different websites or apps. You just run one system and it copes with all of them. This is not actually a new idea at all – local government call centres don’t worry what telephone network people are phoning from, or what brand of phone they are using.
However, it is a new idea in the realm of government IT systems for storing things like pothole repair requests, or school-admission applications. Traditionally these systems have not been set up to speak a common language with the outside world. Unfortunately, this failure to speak a common language has not always been by accident. Unscrupulous suppliers will sometimes intentionally set up systems so that the government has to pay extra money if they want any new channels to be added. Using Open311 is both a way to lower your future costs, and a way to make sure your current supplier can’t lock you into expensive upgrades.
Isn’t opening our systems to the outside a security nightmare?
Open311 is not about opening up private data, such as exposing the home addresses of vulnerable children. Open311 can be configured to open up government systems where that is appropriate, and everything that needs to stay private will stay private. There are no fundamental security problems to using an Open311 system.
Is this just about pothole reports?
No. Open311 isn’t limited to street-fixing services like FixMyStreet, even though that kind of problem is where Open311 started. As more and more public bodies offer their services online, they all face the same problem of spiralling costs as the public demands access through more and more diverse channels. In the future it should be possible to renew parking licenses, pay local taxes and do other complex transactions via Open311. But for today we encourage everyone interested to start at the simpler end of the scale.
How does mySociety use Open311?
We will still happily connect FixMyStreet to systems that don’t use Open311, but we always explain to clients that Open311 is the most desirable way of connecting their new FixMyStreet deployment with their current problem databases. We even offer lower prices to governments who use Open311.
We offer lower prices this partly because our costs go down, but also because we want to leave local governments with street-fault reporting systems that can connect not just to FixMyStreet, but to any new services in this area that emerge in the future. If Google maps or Twitter suddenly add street fault reporting, why should the local governments have to pay more money to handle those problems, when it could get them for free using Open311?
In short, we see Open311 as a solid foundation for building local government services without locking our clients into a relationship with mySociety as suppliers. In future we will also recommend the use of Open311 for services like ‘Please send me a new recycling bin’, ‘Please tell me what jobs you have open’ and ‘Please answer this FOI request’.
In the next post we’ll cover how Open311 works in a bit more detail (but still as clearly as we can), and in a third post we’ll explain how our work with FixMyStreet for Councils has led us to propose some improvements to the Open311 standard.
Photo by Rupert Ganzer (CC)
How do you get everyone working together when the community needs it most – like when there’s a heavy snowfall?
Recently, we posted a conversation with Chris Palmer of Barnet Council, where he talked about integration of FixMyStreet with the council website.
Barnet also use another mySociety tool – Pledgebank – and Chris explained how it helps them within the Barnet communities.
Turning complaints into action
“We took on Pledgebank in the belief that the council needs to get out of people’s way. Online communities are good at complaining about things: it’s easy to get instant outrage on the web, and actually we need mechanisms that allow people to get together creatively.
“One of the issues we had during the heavy winter of 2010 was that people complained the council wasn’t coming round and clearing their paths. Well, the council never came round and cleared the pavement outside those particular houses.
“Many people said, well if the council allowed us to, we would do it ourselves. Pledgebank allowed us to get parents at 25 schools to sign up last year. They pledged to come and spread grit and clear the snow from outside just in return for free shovels and a ton of grit.
“That kind of thing encourages residents to be active, it frees them from the frustrations that the political system gives them. If people feel, ‘Oh, there’s a legal process stopping me doing this’, it moves the council forward, to being an enabler rather than a provider of services.
“A parent can spend 15 minutes in the morning and then be confident their child will be at school for the day and that they can go off to work, so for the parents, it’s win-win.
“One of the things that surprised us was the response of local residents who live in the street but don’t necessarily have children at the school. They felt that they should be helping to clear the snow. It gave a group of active residents who we hadn’t even asked, a chance to be involved”.
Tapping into community interest
Why do you think that is? Is it just that people just want to contribute within their community?
“I genuinely think people just aren’t interested in councils. I couldn’t tell you the name of my council leader where I live, never mind the name of cabinet members. However, I am very interested in the services the council provides: the only public meeting I’ve ever been to was about parking, because it directly affected my street. And I’d probably say there’s a rule, where people will take responsibility for the space outside their own house, and be prepared to extend that a few houses either side. And this just gives people a mechanism to be involved in their local community.
“With Pledgebank, we can leave people to do things amongst themselves, with the understanding that the council is not just a provider of services, but a catalyst to people doing those things themselves”.
What else have you done with Pledgebank?
“We’re hoping residents will play a part in keeping their streets tidy with our Adopt-a-Street scheme. There’s a real sense of ownership if somebody controls the green space outside their house: do they plant the bottom of trees in the street with wild flowers, do they plant bulbs in what’s currently a grass verge? We can give them that element of ownership, and give them control of their local environment.
“So with Adopt-a-Street, we found one or two people locally with an interest in doing it, and we’re looking now at how we encourage them to leaflet their neighbours, get in contact with their neighbours.
A challenge for the marketing department
“It’s worth adding, though, that Pledgebank has taken us a lot of learning. It’s quite easy to imagine that anything you bung up on the web suddenly becomes viral: it doesn’t.
“One of the challenges for us is how we link into what we’re doing, how we publicise what we’re doing with Pledgebank and the web. So we have to look at it not so much as, here’s an interesting web device, but here’s a device that enables residents to do things. But the council has a responsibility to publicise it.
“The key challenge for us is making information available to the relevant people. It’s all about defining communities, and making information available to those communities – and mySociety has been tremendously helpful with that.
“It’s changed the way we’re using our information now and it’s fair to say it’s informed how we’ve built our new website.”
Barnet have been inventive with Pledgebank. As well as using it during the snows, they’ve managed street parties for the Jubilee and Royal Wedding; got volunteers to give IT training to residents; and encouraged visits to carehomes.
If you’re from a council and you think Pledgebank might work for you, drop us a line to find out more.
Image credits: Snow Big Dig by Shashi Bellamkonda, Lakeside Daisy by Matt MacGillivray, and Diamond Jubilee Street Party on Kenyon Clough by Dave Haygarth, all used with thanks under the Creative Commons licence.
Lichfield residents are the latest to enjoy FixMyStreet functionality on their council website.
We’ve been working with Lichfield District Council to integrate FixMyStreet into their snazzy site design. The resulting interface echoes their purple and green colour scheme, and sits comfortably within their own page layouts.
What happens to reports when councils include FixMyStreet for Councils on their website? There’s a two-way mirroring process. All reports made via the Lichfield website will also appear on the main FixMyStreet.com site. And all Lichfield reports made via FixMyStreet are published onto their website too. That way, we cut down on the possibility of duplicate reports, and Lichfield residents can use whichever site they prefer.
So, Lichfeldians, there’s never been a better time to report that nagging problem on your street. Do let us know how you find it!
Governments, companies and large organisations of all kinds regularly spend astonishing amounts of money on computer systems that are either completely broken, or which are instances of what I call Hateware – software that appears to have been designed by people who actually hate users.
Why does this happen? Obviously there are multiple, terribly complicated factors. But I’m going to boil down one of the biggest problems to a little story.
[Dreamy fade sequence]
Imagine you have been made responsible for replacing the desk chairs in your office. The old ones have gone all sweat coloured, and you’re worried one might collapse.
So you put out a competitive tender for furniture companies. You wait, vet and score all their bids, and finally you invite the finalists in to make their pitch.
In they come: smart, sober, dressed in a way that suggests success whilst avoiding ostentation. They set up their presentation, and start to tell you about the range of office furniture they have. The pitch is fantastic. They’ve already thought about all your concerns. They have an impressive array of happy clients who are just like you. Their slides are polished and focussed. They’ve brought fabric swatches to flick through. The chairs are handsome, with just the right number of pleasing gizmos. And they can ship next week.
The presentation draws to a close – any questions?
“Well, that was fantastic – I particularly like your X1 basic office chair. Just one question, what’s the cost?”
A few minutes pass as they reflect on the wide range of maintenance contract options, chair customisations and bulk purchasing reductions. Eventually, with a little nudging, you get the price for one chair.
“The base price of the X1 office chair is currently one millions pounds, with a £500,000 yearly licensing contract. Plus tax.”
Moments later the presenters, laptops, suits and fabric swatches bump to earth on the pavement outside the office door. Security is instructed never to let anyone from the company in, ever again.
How does this little story explain anything about ICT?
Well, re-read the story above, but replace ‘chair’ with ‘payroll system’. And replace ‘fabric swatch’ with ‘lovingly photoshopped mockups, customised for your company branding’. Go on – I’ll wait.
The pitch no longer seems so crazy, and you certainly wouldn’t kick someone out when they announce the price. Why? Because you don’t know what is a sane price for a payroll system, and what’s an absurd, insulting price.
The moral here is quite simple: you can’t make good decisions if you are lacking even the most basic frame of reference about what something should cost, or how it works.
The problem is that when it comes to identifying technology needs, and procuring successfully to fill them, you can’t simply rely on general life experience to save you. It’s a specialist skill, and one that requires knowledge to be constantly relearned and unlearned as technologies change.
Too few large organisations understand this. They see buying a new computer system as very much like buying new furniture – it’s just ‘all stuff the office needs’, along with car parks, printer paper or tea bags. This attitude fails to see that many modern organisations don’t have IT systems and websites, they are IT systems and websites. They can no more delegate this to some junior staffer than they can delegate the strategy of the whole business.
Almost all large organisations today need at least one person right up at the top level of the company who can spot the million pound chairs without the help of subordinates.
Once organisations understand that they are regularly buying million pound chairs, their CEOs and boards face another problem: how do they know which of their staff can actually spot the million pound chair, if any?
Unfortunately, the solution isn’t obvious.
As of right now there are no professional qualifications that would guarantee the right skills set. Worse, there’s even an unfortunate association in my mind between people with lots of qualifications like ‘MSCE’ and ‘SAP Certified Associate’ and projects that are triply gold plated, entirely missing user-centered design, and inevitably compromised by a tribal loyalty to one vendor.
So what’s a CEO to do? The answer, for now, unfortunately has to be to hire through trust and reputation networks. Find people who appear to have delivered nimble, popular user-centred projects on limited budgets, and get them to help you hire and restructure.
Trust networks, of course, can backfire: trust the wrong person and you can be in trouble. But the Enterprise computing world has backfired into the laps of leaders and managers enough times in the last two decades.
It is time for leaders to bring some people who have got their hands dirty in the guts of digital projects into the decision making rooms, and onto the decision making boards.
Tom will be talking more on this theme at the Local Government Association Conference next week.