What is a design system?

Joshua Morris (Senior Front End Developer) explains what a design system is, why you should use one, and what the University has been doing to develop its own design system.

TLDR: A design system is a complete toolkit for managing design at scale, providing reusable ‘components’ and ‘patterns’ along with accompanying standards and governance.

Recently there has been a lot of discussion about how large organisations manage digital design at scale. Many of these organisations have brand guidelines created for printed media such as leaflets and flyers.

They also usually have large digital estates comprised of thousands of pages of content, presented in various ways such as different website page layouts and applications.

Digital teams responsible for the estate often try to apply strict print guidelines to this mixture of content, in a waterfall model, with varying degrees of success. Digital teams make their way through their digital estate updating brand, and then when print guidelines are updated, they restart.

As digital teams are generally smaller, how can you efficiently roll out and maintain a consistent brand across your digital estate?

Introducing a design system – a complete toolkit for managing design at scale.

Continue reading: What is a design system?

Building campaign landing pages, part 2: a sprint to deliver

In this second of two posts on campaign landing pages (read part one), Josh Morris (Senior Front End Developer) and Jamie Forsyth (UX/UI Designer) discuss using a sprint approach to create campaign landing pages at the University.

We brought together experts to work in a ‘sprint style’ fashion over three weeks, aiming to deliver campaign landing pages that could be built and maintained within our institutional content management system (CMS), TerminalFour Site Manager.

Our experts included marketers, external agencies, product managers, content designers, user interface/experience designers, developers and other stakeholders.

Continue reading: Building campaign landing pages, part 2: a sprint to deliver

Building campaign landing pages, part 1: a reusable approach

In this first of two posts on campaign landing pages, Josh Morris (Senior Front End Developer) and Jamie Forsyth (UX/UI Designer) discuss streamlining the process of creating this type of content at the University.

In the past, the Digital Experience team has been very reactive. A stakeholder would give us a task like “I want a new website”, and we would go off and build it. Sounds OK on the face of it, right? However, this type of reactive approach is an inefficient way of working, and more often than not wastes time and resources.

Our team is trying to pivot to a more strategic approach – identifying and solving problems in a more centralised and reusable way.

Continue reading: Building campaign landing pages, part 1: a reusable approach

Putting people at the centre of our research comms

6,000 members of staff and almost 28,000 students, six faculties, 28 schools and departments, 12 institutes, over 250 research groups, groups clusters and networks, and 14 divisions…  The University of Bristol is, if nothing else, a complex institution.
Continue reading: Putting people at the centre of our research comms

Improvements to the Clearing process: A technical overview

My colleague John Bourne recently wrote a post about our clearing application process covering the user experience improvements. In this post I’ll be delving into some of the technical work behind these.
Continue reading: Improvements to the Clearing process: A technical overview

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

Love the problem

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

Untangling our duplicate content

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.

Continue reading: Untangling our duplicate content

Modernising the staff experience

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