Skip to main content

Four bits of advice for new LocalGov websites.

 John Fox recently posted designs for the new Sheffield City Council website on Google+. I applaud anyone who does this and opens their designs up to critique and criticism; it can only produce a better result for the end user. A discussion followed which prompted me to come up with the following four bits of advice if you're creating a new Local Government website:

  1. Treat Google as your home page. Prioritise the SEO work above things like including top tasks on your home page. At least twice as many people will come from Google than visit your home page.


  2. Treat every page as landing page. Assess the tasks one might need associated with this particular service, wherever they might be on the site and whoever might provide them, and link to them.

    For example, if you want to build an extension on your house you'll need to know about Planning Applications and you'll probably need to know about Building Control which are generally in the same areas of a council website.

    Less likely to be in the same category is information about a skip licence. You might need to know about noise pollution or air pollution. You might need to know when the local tip is open and whether you can take certain materials there.

    Treating every page as a landing page will give you an overview of the services and information the viewer might need from the whole of your organisation.


  3. Offer themed pages that live outside the general structure of your content but bring together pages. Be clever and don't group things simply because they happen to start with the same letter, in an A- Z.

    Group things because they have common elements, may be used by similar demographics or are part of a similar user journey. Someone searching for "disability" might be looking for information from Social Care, but equally they might want help with finding employment, a blue badge, help with waste collection or something else.

    Make all this information accessible from one page.


     
  4. Treat your site as collection of re-usable objects, not a bunch of web pages.

    Ensuring you use RDF or similar metadata where applicable will mean that people don't have to visit your site to find out what they need in some cases.

    Visitor numbers alone are not indicative of a good service and this will actually reduce avoidable contact to your website by making your content even easier to find and re-publish in other digital media.

It's not until you start to consider a true polyhierarchical structure, coupled with the ability to syndicate your content you'll start to move your website from rigid set of pages to a fluid set of objects relating to services and information your organisation provides.

We'll be using these principles in our Alpha (alpha.westberks.gov.uk) and I'd welcome any feedback on this work in progress.

Comments

Popular posts from this blog

Digital best practice checklist

This week I finished the draft of a digital best practice check-list. It's not digital strategy, in fact I'm increasingly thinking organisations don't need a digital strategy, they need a delivery strategy. My draft has check-list of seven questions and recommendations, with one overall recommendation regarding best practice for delivering digital. Ideally it would be incorporated into a wider service and information delivery strategy. Below I've omitted the bulk of the content, the reasoning behind arriving at the recommendation from the question because it's still in draft, but here are the seven questions and eight recommendations: 1. Is the council properly promoting its digital services and content, to reduce avoidable contact? Recommendation: Establish a “digital first” ethos to the promotion of services and better targeting what, when and where they're promoted. 2. Are the digital services the council offers, especially where the design and

Carl's Conundrum of Internal Influence

I'm writing this partly as a reply to an excellent piece that Carl Haggerty published about the disconnect between internal and external influence and partly due to various conversations over the past month about how to make using tools like collaboration platform  Pipeline common practice. This isn't really about Carl though, or Devon County Council, or any other council specifically, it's more a comment on the influence of digital teams in local governments, or lack of, and how to resolve this. So here's the question that prompted this piece. How can someone who's been recognised nationally for their work, first by winning the Guardian's Leadership Excellent Award and who has more recently been placed in the top 100 of the Local Government Chronicle's most influential people in local government , "sometimes feel rather isolated and disconnected to the power and influence internally". First, let's consider whether is this a problem to

Pipeline Alpha

In September 2014, officers from 25 councils met in Guildford to discuss a platform to enable collaboration across Local Government. A "Kickstarter for local government" is the missing part to Makers Project Teams , a concept to enable collaborative working across different organisations put forward by LGMakers the design and development strand of LocalGov Digital . Based on the user needs captured at the event, LGMakers created collaboration platform Pipeline and by October people from over 50 councils had signed up . Pipeline is an Alpha, a prototype set up to evaluate how a Kickstarter for councils might work. It is a working site though, and is being used as the platform it is eventually intended to be, at present without some of finer features a live offer might have. So what have I've learnt in the eight months since we launched Pipeline? There's a strong desire to collaborate  LocalGov Digital isn't a funded programme. I wrote about how much it

Superfast highways

You may have seen this slide I put together to help explain digital transformation This week we launched a new beta service to report speeding traffic. It looks fairly simple but to give you an idea of what's happening in the background I thought it might be useful to show you the before and after. So here's the before and as you can see it's completely a manual process. Stuff might be recorded electronically but it takes someone to do something seven time to make the process work and send it to the parish or the district. Here's the after What this doesn't tell you is that it's basing whether the request is for the parish or district on three questions. It's also doing a spatial look up to find the parish and returning the parish clerk details using the Modern.Gov API. Because these are already part of our platform this is data that we currently maintain, so there's no additional work to keep this up to date and we've reduced the h

Defining transformation to a wider audience

For the past month I've been putting together a paper on the next steps of digital transformation, for the organisation I work for. I'm proposing we look at two capabilities and two business areas, and if approved I'll be writing more about it. It's been a great exercise in gathering my thoughts and helping me to define digital transformation to a wider audience and how it fits into the bigger picture of service improvement. Here's some of the stuff I've learnt or had affirmed: Transformation, digital or not, starts with understanding the needs of the user through research. This should be obvious, but in local government too often I've seen "build it and they will come" approach applied. It's unlikely a commercial operation would launch a new product without first researching the market, so why would a digital service be any difference? A couple of years ago I wrote how the phrase "digital transformation" was hindering digit