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.
Continue reading: Intranet design principles
Launching the University’s first intranet has thrown up some interesting challenges, says Intranet manager Steve Wright.
Two weeks ago, we released a beta version of a new intranet for staff and postgraduate researchers. We’ve designed with mobile devices in mind, applied content design best practice, and met accessibility standards.
So far, so commonplace you might say. But it’s been an unusual project for quite a few reasons.
First, it’s totally new. Surprisingly (and it was a big surprise to me when I started here in July 2018), the University hasn’t had a global intranet before. Internal-facing content and information has historically been stored at the local level: on faculty, school or division sites. Continue reading: Modernising the staff experience