Use what you already have

When planning a new project or activity, it’s easy to decide to get something new.

For instance, you might see it as the perfect opportunity to buy a cool web service to help you deliver this piece of work.

Or maybe you know that you could do a great job customising WordPress to do exactly what you want.

Hold on for a minute, though. What have you already got available to you that you could use to make this happen?

It might not be the perfect fit you would like in a perfect world, but it might be good enough. It might also come with a few advantages:

  • you can start work right away
  • no problems with access or other IT issues
  • your users will be more likely to be familiar with the way it works
  • there will be internal knowledge of the system to help you get stuff done

I’ve an example to share in a future post, where I resisted the temptation to do something new, and instead used what was already there and already familiar, in my work at the Department of Health.

Loving lurkers

I couldn’t agree more with Mozilla’s Laura Hilliger:

We can’t force people to participate, and if we really care about educating people, we shouldn’t try. We should build and design for the people who are participating, and we should be careful to ensure that the lurkers feel welcome. We should create safe spaces of learning and mentorship where even those who don’t complete the call to action still start to develop trust in us, in our products. The fact is you are always a lurker before you participate, so we should be careful not to push people away by implying that they don’t count if they aren’t like us. If we work to love our lurkers, maybe some of them will find their reason to participate.

Embrace constraints

Sometimes it’s better to embrace constraints. Why not even invent some?

Constraints don’t need to make things harder – they can make things easier.

Why take a year to deliver something if you can get it out of the door in months?

Constraints focus the mind, especially on what is important and what isn’t.

Say you’re handed a project at work. It feels like something ought to be delivered within six months. How about seeing what can be achieved in six weeks?

It might end up being a bit rough and ready, but there’s lots of pros to outweigh that con:

  • The positive feeling of having delivered something
  • The ability to get feedback from users on what you’ve done
  • Reducing the level of risk in the project

So rather than playing safe and asking for more time, more money, and more people, why not embrace some constraints and see what can be done quickly, cheaply and with a small group?

Why some centralising of local gov digital is needed

An ongoing debate this. Ben Proctor has had his say recently, and it feels fairly sensible.

There are two issues at stake here – one is whether some kind of ‘GDS’ for local government is needed; second is whether we need a website for every council.

These two things are not necessarily bound to one another.

My view is that some centralising is vital for the sector, for two main reasons.

First, financial. It’s nuts that there are hundreds of broadly similar, publicly funded organisations out there paying again and again for broadly the same thing. There has to be savings to be made here with a bit of rationalisation.

Second, and most important for me, quality. The standard of digital services in local government is variable to say the least. Lots of people are doing brilliant work. Lots more people, it would appear, are being prevented from doing even competent work by some circumstance or other.

I think the first thing local government needs to do is to admit that there is a problem. The majority of services delivered within the sector do not provide an adequate level of quality user experience.

In other words, the current system isn’t working.

The problem, as many have pointed out, is that making this happen would be hard. Who has the mandate to get this done? How to get around political issues, particularly local pride, and so on? Big national IT projects? Arrrgggggh!

… and so on.

However, none of the arguments are strong enough to make this not worth trying. If we can save the sector millions of pounds a year, then putting a few noses out of joint will probably be worth it.

Key to success for me will be:

  • Ownership by local government. Lots of models have been discussed. I would look strongly at putting a mutual together, owned by the sector, where councils pool money by investing in the mutual. This should provide a mandate as well as scale to get things done
  • Focusing on achieving realistic things. Follow the GDS model of building prototypes and getting stuff out quickly. Don’t build the single local government domain as the first job.
  • Quality above all else. Everything that comes out of the mutual should be of the highest quality, firstly because it should be the minimum standard anyway but also to demonstrate to the sector what can be achieved
  • Share everything openly. Even those who choose not to be a part of the mutual should still be able to make use of its products and services.

I’m sure there are lots of holes in these – admittedly very sketchy – ideas. However, so much could be achieved so quickly if even just a handful of forward thinking local authorities got together and made this happen.

In praise of the clipboard manager

A clipboard manager is an insanely useful bit of productivity kit. It’s one of those things that you may not know even exists, but once you start using it, you can never go back.

A quick reminder: the clipboard is the bit of memory on your computer (or phone, tablet, fridge etc) where the content you have just copied or cut from the screen is store, so that you can paste it elsewhere.

One of the drawbacks of the clapboard is that it can only store one bit of content at a time – it overwrites itself every time you cut or copy something new.

However, with a clipboard manager, your history of cut and copied content is available to you whenever you want it – so you’re no longer limited to that one clipping!

Here’s an example of when this is handy. Say you’re copying lots of bits of text from one document to another. Normally, you’d copy a chunk, flip to the other document and paste it in; then back to the original, copy, flip, paste, and back again.

With a clipboard manager in place, you just copy all the different chunks in the original, then flip to the destination document and paste them all in.

It’s so easy! You’ll wonder how you ever coped without it.

I use Alfred on my Mac to manage my clipboard (it does a load of other neat stuff too). If you’re on Windows, Ditto seems like a good option.

Load more posts!