I’m really pleased to be sharing our Digital Comms roadmap for the next quarter. It’s the first time we’ve publicly shared it. It’s our way of explaining what we’ve done, what we’re doing and what we think we’re going be doing next.
Continue reading: Our new roadmap
I published a post last summer about the positive effect a new project management framework was having for us and those we work with. A lot has happened since then, but, through it all, DPAB has doggedly and determinedly continued to meet every Wednesday to triage, assess and prioritise. We couldn’t do without it. So, what is DPAB and why do you need one?
Continue reading: Why every digital team needs a ‘DPAB’
We’ve been investing significantly in an intranet for University staff and postgraduate research students (PGRs). Previously our intranet content was scattered across our external website, seriously old internal content management systems, wikis and random crevices that only staff who’ve been at the University for decades would be able to find.
As we’ve just moved it out of beta and into live I thought it was a good opportunity to detail the design principles we’ve been using to inform its development.
It’s important to add we’re still at the early stages of a long journey. There’s a large roadmap of development ahead. But we believe that by sticking with these principles we can continue to build an intranet that will prove invaluable to all our staff and PGRs.
The third part of digital officer Charlotte Brewer’s series on content sprinting.
This post was actually written a while ago. We planned to release it as part of our series on ‘Content Sprinting’. Then lockdown started. Hitting the publish button fell down the list of priorities.
Despite lockdown, and despite everyone working from home and all the challenges that has brought, we’re actually still working in exactly the same way. We’re still sprinting. We’re still doing everything we did before. Everything in this blog post remains accurate. The only difference is that all our meetings and our conversations are via Skype.
Continue reading: Content sprinting – part three
When colleagues from across the University come to us for help with their website, the first thing we ask them is: what’s your problem?
That sounds a bit rude and abrupt. Let me explain.
In any digital project or product this is the single most important question that needs answering. If there’s no problem to solve then there’s no work needed.
What do we mean by problem? What we don’t mean is that your website looks ugly, that it doesn’t look good on a mobile device, it doesn’t have the right tone, or that it’s not structured in a way that mirrors your team’s structure.
These aren’t problems, they’re solutions looking for a problem.Continue reading: Love the problem
We introduced a new project management framework and governance function a year ago. It’s transformed our ability to respond effectively and flexibly to priority business needs. In the first of two posts, deputy head of digital comms Alex Pardoe explains how.
Where we were
When I started in this role in early in 2017, the team was really struggling to cope with the competing demands from across the University. These sort of things:
- Work requests could arrive from anywhere: email, phone calls, Yammer comments, meeting minutes, post-it notes on desks, chats in kitchen area, chats in the pub etc.
- Objectives undefined/entirely absent – why are we going to do this work?
- Scope of work undefined – what are we going to do, when do we know we’ve done it… and do they agree?
- No one talked about cost.
- And many, many more…