saas

Quite a mixture of stuff this week – plenty to dig into over the weekend.

1. Interesting job at GDS, promoting the use of gov.uk Verify in local government. You have until the end of Sunday 2nd July to apply – so better get cracking if you fancy it. If you’re on the lookout for a digital-ish job, then I’d thoroughly recommend Matt Jukes’ weekly listing.
2. Startup SaaS Stack – this is a nice way of looking at the small number of software as a service tools that a new organisation might need to have. Not just relevant to startups but any organisations – certainly community, voluntary and charity groups could look at this and get a cutting edge tech stack in place in minutes and almost no cash. It also is an effective introduction to thinking about capabilities rather than systems in planning what technology you need.
3. User-centred digital strategy – a really nice set of slides from Sophie Dennis that explains why strategy is helpful and what good and bad strategy looks like. While you’re there, why not check out her other deck on ‘Adventures in policy land’ which looks at service design in government, and is equally excellent (both via Strategic Reading).
4. Paul Maltby followed up the crowd sourced reading list that I shared last week with three posts on how digital teams and policy teams can work better together, titled ‘A short guide to policy for government digital professionals‘, ‘What digital and policy can learn from each other‘ and ‘Prototyping a One Team Government manifesto‘. All are worth reading and mulling over.
5. Who is responsible for effective, efficient and secure digital government? – watch the video of a wide ranging discussion of the progress made in digitising government. There’s more on the Institute for Government’s work in this area in this blog post, including a link to their report on the topic. I think it’s pretty clear to most people that the wave of enthusiasm for the work of the GDS in particular seems to be waning, not least following the departure of a number of leaders from that team, but also as they start to get stuck into some of the more intractable problems around culture and the back office IT stack. I’d argue that what is needed is not so much management, or even leadership (whatever the hell that is) but authority – someone or some people with the mandate to make change happen and the ability to force it through when bureaucratic (on the government side) and kleptocratic (on the vendor side) intertia starts kicking in.

These have mostly all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.