Co-creating consistent UI in different systems.
Responsibility:
Create new components, improve old components, help to make design accessible
At Handelsbanken we have 100 different development teams. It is challenging to keep the design consistent.
We have shared common concept that is not a bunch of rules, its a framework with guiding examples.
All designers (we are 30 ) contribute to actively design, develop, test and maintain the design system. The code and components can be used regardless of the platform and are changed when component is renewed.
Firstly we have gathered all the guidelines and examples to one place.
When you start designing there are files with components that you can just pick. All the buttons and colours and Titles are sorted accordingly. They are almost like building bricks that are ready to be picked. Also there are guidelines where and when to use.
This has not been always like that and me and other designers have been co-creating it for a year.
When you need a new component , there is the mutual Definition of done. That includes a table of acceptance criteria.
Example of acceptance criteria:
Is the component functional on all supported screen sizes (320px and up)?
Have you checked that no personal data, such as name of customer corporation, is put in this field are sent to Google Analytics?
Does component have error handling patterns?
Consistent UI and better collaborations between cross- functional teams.
Responsibility for co-creation