In Regional Services Division (RSD), we use the GOV.UK Design System so that the look and function of the products is similar across the suite, and to GOV.UK.

However, each team has interpreted and applied the design system to their context. This means that the products may be meeting similar or the same needs, but the solutions look or function differently.

Over time we want our suite of products to become consistent, so that it's easier for users to learn and use multiple products.

By creating a library of design patterns and applying these to meet user needs, we will create this similarity and also:

  • it will be quicker to design and build our products
  • we will spend less time solving problems which other teams have already solved
  • it will make it easier to maintain the suite of products once they are managed by Service Support

We have had some user feedback that it's easy to use a product because they are familiar with another product which works similarly. We have also had feedback that where one product does something but another product does not, it's confusing and they waste time trying to work out how to achieve their goal.

We will continue to gather insight from users to understand where inconsistency is causing them problems, and where consistency may help them.

Rolling-out design patterns across RSD

When designing something new or improving an existing design

We check the user needs database (opens on DfE intranet) to see if a user need we have identified is documented for other products.

If it is:

  • the need will link to any associated design patterns used in existing products
  • we apply the pattern or re-use the design
  • we update the user needs database to reflect the user need and pattern

If it is not, we:

  • document the new need in the user needs database
  • create a new design
  • capture our reasons for deviating from the design pattern in the user needs database

We have an existing design which we are not planning to iterate

Over time we want to update existing designs to follow our design patterns as well.

If we do not have the opportunity to apply a design pattern to new work or an iteration, we prioritise 2 aspects of our products to update and follow a design pattern.

Ceremonies

We use our programme's interaction design community of practice (14:00 every Wednesday) to share designs at an early stage and discuss design patterns. RSD's Head of UCD joins these sessions to support teams to do this.

We use our UCD community meetings (14:00 Monday, monthly) to discuss iterations to existing patterns, and potential new patterns.

Prioritisation

We prioritise design patterns through our programme's 'front door' prioritisation process. This means our Senior Leadership Team and PMs input into prioritisation.

Our cross-cutting UCD group suggest a shortlist of design patterns as candidates for prioritisation, based on weighted shortest job first (WSJF) and input from across the programme.