A design system is not one single deliverable but rather a collection of deliverables which can be updated / changed as the clients needs change. It should evolve constantly with the product, technology and company. We’re big fans of design systems because they give our clients the flexibility and freedom to implement consistent updates to their website or product in the future. Essentially we’re giving them the tools to do more themselves.
On the surface, they might look similar but actually, there are key differences to be aware of. A design system isn’t just a collection of assets and components you use to build a digital product. In its fullest form, it’s much more than a pattern library which is often nothing more than a sketch file containing a bunch of different content designs which can be assembled any way you like.
Just because the pieces are all consistent doesn’t mean the end result will be. The end result must be more than just the sum of its parts - it has to have structure and represent the overall design. That’s what a design system does - it contains different blocks and elements which are designed to fit together and be reused in new and different ways to always form a complete, consistent picture.
Acting as a comprehensive brand guideline tool for designers and developers, a design system should always contain:
It should also contain more abstract information such as:
Design systems are good because they ensure that everyone is working from the same starting point and using the same information. As an agency which doesn’t offer development, we find that this makes for a smooth hand over from design to build, whether that’s to another agency or an in-house dev team. Here are some examples from the BBC design system which is readily available online. We link to it later on.
Before starting to put anything together, it’s important to align teams around a clear set of shared goals. This helps building a vision and making sure everyone looks in the same direction. These goals will evolve and change with time and this is completely normal. If changes happen they should be communicated to all parties.
Values could for example be a manifesto that the company follows. Here, we follow a set of six guiding principles in everything we do - this would be our manifesto.
It’s important to remember that ‘design principles’ are more than just the visual aspect of a project. They are the guiding principles which help teams reach the purpose of the product thanks to the design.
The identity should be in line with the strategy and the objectives of the brand. When thinking about the brand you need to consider all the different elements which will be used. I’ve listed the common ones below : -
These brand elements need rules which will be “the grammar” of the design system. This will explain how it all fits together and are guidelines which show good examples of their use.
Components are at the heart of the design system. Everything mentioned above will help you create the components (usually in Sketch or XD) and ensure they are always consistent.
A good design system will ensure that the money you have invested at the research and design stage pays off in the long run. You will be able to refer back to it when adding any new content or making any decisions. Anyone who has used the BBC website knows they have a consistent design across all of the pages (including news, sport, weather etc).
This is an example of a design system, in this case BBC GEL (Global Experience Language). It contains a list of their components, brand language and ‘How to’ guides.
Another very simple example of a Design System but consistent is the Government's own Gov.uk site.
Having a good design system is something you can be proud of as an organisation. It goes beyond a simple asset library / brand guidelines and it grows and works with you as your company develops. And hey, guess what? We can help - get in touch and find out more.