Intranet design principles

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.

Screenshot of intranet

Continue reading: Intranet design principles

How one small team can support a vast community of publishers

Digital Manager Antony Theobald on how improving our internal support processes will ultimately benefit users of our website.

Here at the University of Bristol, we operate a devolved publishing model for web content.

‘Devolved’ publishing for us means we have nearly 2,000 web publishers creating and updating content across hundreds of sub-sites and pages under bristol.ac.uk.

For us as a digital team, this has some pros and many cons.

Without going into all of those here, we’ve recently started addressing one of the major cons: one small team supporting a vast community of publishers.

Continue reading: How one small team can support a vast community of publishers

Thinking about a product approach

Let’s start with a quote:

“Most web teams I’ve met are being nibbled to death by tiny tasks. They don’t have time to focus on what really matters – the top tasks* – because the org is so vanity-prone, inward-looking and organisation-centric.” Gerry McGovern – Transform: A rebel’s guide for digital transformation, Pg158

I’ll wager most higher education digital teams can relate to this. We’re no different at Bristol. This is exactly the challenge we face. There are so many demands on our time it’s very hard to make the time and space to focus on the important things. But when us digital folk try to kick back, we’re told that each project is utterly crucial, has an unmissable deadline, and has some seriously senior backing.

Many of us will secretly face-palm when we get these responses, but it’s a natural way to think and act. We should be more surprised if our colleagues didn’t respond this way. But the fact remains – we are all too often stymied by ourselves.

So how to change things? How to help refocus our efforts onto what really matters to our users/audience/students? Continue reading: Thinking about a product approach