That coalition website strategy in full
Herewith HMG’s bold master plan to fully seize the opportunities offered by new technology in government, whilst simultaneously heavily reducing actual websites, staff and cash. In one stroke this policy shall put an end to waste, open up brave new possibilities, and compeltely eliminate confusion.
- Announce you’re going to close 3/4 of government websites, claiming you’ll do away with:
- anything unco-ordinated,
- anything unnecessarily expensive,
- anything under-used,
- (in which case, said currently paid-up websites will presumably have to be broken up and re-developed into other sites or DirectGov – see 1.2)
- any vanity sites.
- Announce all new websites will go through Frances Maude’s new senior committee, which will:
- decide if they’ll be useful enough to be allowed,
- decide if they’re usable and used enough to be allowed,
- (for which they will presumably have to quickly gain a lot of technical knowledge to make tactical judgements below their pay grade – see 1.2)
- champion centralised co-ordination in eGov web resources,
- have no remit over print and outdoor ad campaigns, as you obviously never get any kind of poor value there.
- Immediately announce two new websites (admirably cheaply constructed), offering:
- a half-arsed show of consultation (see 2.1), and
- nice videos of George Osborne and Nick Clegg (see 1.4).
- Replicate stage 3 in Facebook, claiming in an online chat with Mark Zuckerberg that actually building a website for stage 3 (as you did) would have been silly as it would have cost “millions if not billions”.
- Call for exclusive use of the web in recruitment as it’s cost effective and transparent, even though:
- your proposal of cutting print job ads might make it harder for 30%+ of the population to access them,
- your idea that local people could investigate ‘non-jobs’ will mean jobs have to be spelled out in much more context to justify them to Have Your Say users (see 1.2).
- Announce a 1/3 cut to DirectGov, the service which co-ordinates government web properties (see 1.1, 1.3.1, 2.3).
Phew! That all clear then?