The first thought that so many senior government managers seem to come up with in terms of online service priorities is “get that paper up online!”. Firstly, you can’t bag them out. Thesedays, even the old school senior managers are totally on board with investing in internet development. That’s great, but let’s take a step back and make sure all this effort isn’t wasted. As unfortunate as it is, sometimes its the call of a very senior government manager who makes some bold statement without having any technical understanding of the web, and all those underneath must simply follow his/her commandment - “I want all our ABC123 paper forms and letters online by July 2006!”
All key Government services are about input and output. What information do we want to collect from the citizen or customer, and what information should we display back to them. But converting an organisation’s 150 different individual letters into HTML and PDF format and listing them in a sortable datagrid is not necessarily the answer. “But W3C compliant HTML is great for accessibility, so we’re catering for accessibility, as well as supplying a nice printable, saveable PDF format.” - Spot on, but you haven’t re-thought things seeing as you now have a whole new medium to utilise to get this information out there.
Converting existing paper letters to PDF format is the quick win they all seem to get sucked into. I call these the “phase 1″ systems. They’re great, because at least you can go online and deal with Government and get the information you’re looking for.. But think about paper. Its a medium where there’s no constant reference for anyone to check - the way it works is by sending constant updates when a particular business event triggers a letter to be issued. E.g. A piece of paper arrives saying “Your child support payments have been reduced by $10 this month.” rather than the MONTHLY TOTAL field on some central web page reducing by $10 and you seeing the latest amount at any time. Great, but I don’t want a separate PDF file for every time that happens. In the paper world you would need a letter to tell you this, but on the web, why not just update some core web page. What about a single, clever dynamic web page where all my information is visible from this central hub and it simply updates and highlights when anything changes. This is exactly the type of thinking that a lot of Government departments have missed out on this time round. When the thinking has been there, however, I have seen examples of 10+ paper letter templates replaced by a single, clever, dynamic, data-driven web page. The citizen knows to check this core page, everything happens there. Problem solved and everyone wins.
Similarly, this way of thinking exists with input. They say: “Let’s build ‘web forms’ of all our paper forms”. I’m absolutely not bagging it out, because its great to be able to find every single paper form online in a streamlined web format that you can fill in and hit submit.. But this 1-1 mapping of every paper form to every new web page form is not a decent solution. Perhaps 10 forms could be combined into a new clever application for the citizin like a diary or command center for them to deal with all transactions with a particular agency. There are forms made into web pages named and labelled exactly the same as their paper ancestors. E.g. “KA01 form”. People are really going to find KA01 in the search engines aren’t they.
The worst case is that departments waste a couple of years building these “Phase 1″ secure online systems. Login to read your letters in PDF format etc. Its not the end of the world, but its just frustrating. But as I mentioned, its still progress. The only logical thing left to do after that is make the systems even simpler and better. The information is already on the web servers, just in a different structure, so it isn’t going to be as hard as this initial leap of stepping away from paper everything.