Dave Briggs wrote about the Department of Health (DH) Digital Team’s work on a digital passport and asked for feedback. It’s part of their work to increase the digital capability of all staff in the department. The aim is to: “equip [DH’s] people with the confidence they need to be able to do great work, using the best tools and approaches available to them”. This is my feedback.
I really like the idea of having a clear set of digital things everyone is expected to know and do. I like that it is a simple list. I think it covers a sensible range of topics and I like that it focuses on useful things people would need to know to deliver their objectives, rather than learning about digital for its own sake. One of my bugbears is the attitude that digital isn’t something you need to plan, monitor or involve yourself in the delivery of, it’s just something that you don’t give much thought to and chuck over to an agency. The passport shows that this isn’t the case.
There are three things I’d change, though.
1. Put users first
This one might sound semantic but is really important to me. The line about users should come before agile. If you understand your users, you have a chance of doing a good project without using agile (though I’d recommend you do work in an agile way). If you don’t understand your users, you might as well go home, whatever way of working you choose.
2. Shift the focus from understanding digital, to being able to think and talk about how it can be used
Lots of the parts of the passport are about ‘understanding’ digital. I think it needs to go further, from understanding digital to thinking and talking about it. In my experience, many people are easily able to understand digital in principle, but don’t know how to talk about it or how it can be used. This limits their confidence. I’ve had many conversations where colleagues eagerly agree that they “need to be more digital”, but it all gets a bit uncomfortable and fizzles out when the digital people start talking about it in more detail, or suggesting ideas, and the colleagues can’t take the conversation, and so the project, further.
3. Emphasise being able to make digital delivery happen
The list talks about getting support and guidance inside and outside DH. I think this could go further to equip people with a bit more understanding of how they can make digital delivery happen e.g. in-house digital team, suppliers, what you might be able to start doing within your team. This might help shift the idea that digital is something you automatically put out to tender, or that it’s something only a few people within the department can do.
My second and third suggestions make the passport much harder to achieve and teach. But I think they would make it more impactful.
Good luck to Dave and the team in refining and using the digital passport. I’m looking forward to seeing how it develops.