Intranet design principles

Posted on by Jeremy Torrance

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

(more…)

Content sprinting – part three

Posted on by Charlotte Brewer
Fees and funding web content - show and tell
The show and tell for our latest sprint was held virtually, via Skype.

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.  
 (more…)

Love the problem

Posted on by Jeremy Torrance

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. (more…)

Seven things you need to do to make your content accessible

Posted on by Charlotte Brewer

Our previous accessibility blog post explored some of the barriers that people face when they read online content. Barriers that stop people from being able to use the content.

Creating clear and accessible content has always been important. It means everyone can use and understand it.

However, as more and more services move online, it’s even more important that we reduce these barriers. It’s even more important to create clear and accessible content.

Accessibility symbols
Symbols highlighting different needs. Mobility issues, cognitive problems, hearing problems and vision impairments.

Here are seven things every content professional needs to do to make their content accessible. (more…)

UX writing: making our microcopy clear, concise and useful

Posted on by Miles Taylor

UX manager Miles Taylor on the benefits UX writing can bring to the usability of forms, instructions and error messages.

Major upgrades are afoot to a raft of University systems that support student recruitment and the students themselves once they arrive here.

At the coal (inter)face of each are forms that facilitate tasks and activities students need to complete. Things like booking on an open day, uploading documents to support their application, providing their accommodation preferences or accessing support.

Improving our forms’ usability

Typically, the Digital Communications team has been brought in right at the end of the development process to ‘sign-off’ on accessibility. But we’ve noticed so many more issues with the way we display form than just poor accessibility. (More about our accessibility testing in another post.)

While internal stakeholders have been consulted, users haven’t always had much of a look-in. Research hasn’t always been conducted or designs tested, beyond the purely aesthetic. As a result, several of these forms have been overly long, complex and confusing to complete.

We’ve been working with project teams on each of these systems to offer advice and guidance on form design best practice to improve layout and flow.

And we’ve introduced them to the importance of UX writing to improve the clarity, consistency and usefulness of their forms’ instructions, labels, buttons and error messages.

In preparation, I put a workshop together for our Content Team. Here’s the guidance I stole synthesised from several excellent blog posts on the subject. (more…)

Content sprinting – part two

Posted on by Charlotte Brewer

The second part of digital officer Charlotte Brewer’s series on content sprinting. 

In my last blog post about the sprint way of working, I introduced it as a concept and looked at how we did sprint planning. In this post, I’ll show what it’s like to do the work as part of the content team in a sprint.

Do the work 

Once the sprint planning meeting is over, we get stuck into the list of tasks.   

Each task is a specific, distinct thing that we need to do to complete the goal of the sprint. For our students’ Top Tasks sprint, these included:  

  • Draft a template invitation email 
  • Book rooms  
  • Contact an International Officer to get list of international students  
  • Email these students an invitation to a focus group 
  • Contact the Mature Student Adviser to get list of mature students  
  • Email these students an invitation to a focus group 
  • Collate a list of URLs across the website that answers students’ FAQs (spoiler: there is a lot of duplication) 

Once we finish one task, we move onto the next task. Some of these are small enough for one of us to easily complete it. Others are bigger and need us all to work on it at once. Some tasks are straightforward, while some become blocked. This is where daily stand-ups come in.   

(more…)

Untangling our duplicate content

Posted on by John Bourne

Senior digital product manager John Bourne looks at some of the problems in how we showcase our courses to prospective students.  

At Bristol we spend a lot of time and effort gathering and publishing information about our courses. Most of this is done centrally through our online prospectus, but this information also appears in a variety of other places. 

The University of Bristol homepage with course finder

Duplicated content across our site causes maintenance problems for staff. More importantly it means prospective students don’t really know where to find the most useful information to meet their needs.

(more…)

Content sprinting – part one

Posted on by Charlotte Brewer

It’s not only software that benefits from being delivered in sprints. Digital officer Charlotte Brewer discusses the practicalities of “content sprinting”. 

Sprinting – an act or short spell of running at full speed. That’s the traditional definition. Since the times of the Ancient Greeks, the sprint has been seen as the pinnacle of the athletic world. And in the last decade or so, it’s also become popular in the world of work.  

Software teams have been taking up ‘Agile’ practices that quickly deliver lots of small but functional improvements. Sprinting is fundamental to this. Like the sporting version, sprinting involves a lot of effort over a short space of time.   

In the Digital Comms team, we’ve started to adopt this approach in the way we deliver new content. Our newly–formed content team has now completed five sprints since we started this new way of working in October.  (more…)

Content scrum in practice

Posted on by Alex Pardoe

Deputy head of digital comms Alex Pardoe on how our newly-formed content team has transformed the way we deliver content. 

This post is about the new way of working for the Digital Officers. Where previously we assigned project work to individual staff members through the project framework, now we’re assigning projects to the newly-formed “content team” and they’re using a modified version of Agile Scrum to get them not just done, but done-done. 

Scrum for content? 

Scrum has been used for years in software development, and we liked it for its simplicity and open-ended application. We felt it could work well for discovery and content design work as a team activity. Jeff Sutherland’s wife, Arline, adopted Scrum practices to improve communication and productivity in local churches. It’s not just for coding. 

(more…)

The rise of conversational content and how it will affect content creators

Posted on by Geraint

Digital officer Geraint Northam attended a couple of conferences over the summer where conversational content was discussed. For him, it’s a fascinating area with potentially huge implications for the type of content we’ll be creating in the future, particularly within the higher education sector. 

Conversational content tries to mimic the natural way humans talk to each other, to help solve various tasks. You may have come across this type of content when using text ‘chatbots’ – artificial intelligence software.  

Conversational content is very different to the more traditional content (text, images, video) that we’re used to working with. 

(more…)