Seeing Mr Speaker

I had an appointment to meet Mr Speaker today – John Bercow. I had requested this meeting as I wanted to suggest to him (gently) that Parliament still probably had a bit of a way to go to really engage with people using  technology to make it more accessible.

This is about opening it all up. Things have improved in the website now works better. But most of the best internet developments have come from outside the official Parliamentary structures, e.g. They Work for You and Write to Them both are more popular and have a wider range of functions than the official locations for similar information. These are sites where people can go to find out just what their own MP is doing. You can find what questions your MP has asked, what they have said in any debate and so on.

There is a culture issue here and that holds things back a lot. For example – uploading clips of MPs speaking onto YouTube. It’s taken months to review, and the arguments are over points the rest of the world has largely moved on from years ago like there might be an advert on the page!

Also – the way information about progress of legislation through Parliament is made available makes it very hard for others to then make use of the data. It’s as if the Met Office insisted people come to its website to find the weather forecast and didn’t like people taking its data and reproducing and reusing it elsewhere. Hence the ‘Free Our Bills’ campaign.

So – my visit to Mr Speaker was to suggest that he set up an Advisory Board to help move this agenda forward. It is crucial that it is non-partisan (this is about bringing parliament to life), and includes external experts as well as officers and possibly MPs.

There are a number of simple, significant steps a Speaker can take but the Speaker is very busy and to actually get stuff to happen needs support to make it happen.

Which is why I have suggested to him this Advisory Board. Mr Speaker seemed relatively enthusiastic – and is going to think how to best progress this. I didn’t go into any suggestions or details of things that I think should or could happen – that is for the group.

I think what Mr Speaker will want to do is to sound out the other Parties and officers etc – and then he suggested that we all get together for a brainstorm to see where this could go and how it could happen.

So – I was really pleased that he was open to the idea – and we will see what happens next.

0 thoughts on “Seeing Mr Speaker

  1. I am continually impressed by how the government manages to take months over the simplest of things. If it was down to me then I’d just have implemented all this stuff as soon as it was suggested. I’m not at all convinced that another committee is going to get anything done. Look at the Technology Advisory Board, which spent a great deal of time and effort in setting itself up, with proclamations of knowing specific things that needed doing (which we never saw), and at last report six months ago was trying to create a list of priorities, and hasn’t really done anything but talk since then.

    You don’t need another committee. You need at least one person who is in a position to act to say “What can I do this week that’s useful? Okay, let’s do that *now*”. Take the ‘free our bills’ thing as an example – they have some simple and clear issues with how the process works. If I was in a position where I was familiar with the systems and had access to the data (for example, the office that runs the website, but there are probably other places it could be done) and had no other demands on my time, then I would expect to have a prototype solution running by the end of the week, that dealt with most of their main objections (assuming a typical support workload, that would stretch out to 2-3 weeks). One month to run it past some sample users and stakeholders, get comments, fix issues they raise. Deployment time would depend on procedures, but should be no more than two months after that. The only thing that matters here is to get somebody to sit down and do it.

  2. Pingback: Top of the Blogs: The Golden Dozen #139