BOPS design system and pattern library
What is a design pattern?
Reusable solutions to commonly occurring design problems or user needs. They describe a proven approach to an interaction, behaviour, or way of organising content. Patterns define concepts or a general solutions. they don't dictate specific visual styles.
What is a service pattern?
Reusable, end-to-end user journeys or major interactions that guide users through completing a significant task or goal. They define the structure, flow, and key touchpoints required to achieve a specific service outcome, often integrating multiple design patterns and components.
About this design system
This library is a public collection of reusable service patterns and components. We created these by documenting the design and build of the Back Office Planning System (BOPS).
The aim of this library is to help teams design and build their own back-office products, both inside and outside of government. By providing evidence-backed patterns and components, we can help other teams create a consistent and accessible user experience. We hope this will also increase the efficiency of developing and iterating on BOPS and other digital services. We welcome contributions from the wider design community and add these patterns to existing design libraries.
Our first pattern: the review process
We've started with the review process because it's a common task across many back-office teams. It's often the final step in a case management journey before a case is finalised or closed. Because it's a shared process, we believe this pattern could be widely useful for other services.
What's next
We will be testing this first pattern with designers from other government departments. This helps us make sure it's useful and easy to use for a wider audience, not just within the BOPS project. If this pilot pattern proves to be valuable, we'll continue to grow this library with other service patterns from BOPS.