Basic Design system use cases
...
Persona | Role description | Priority | Actions (supposed) | Notes |
Design system developer | Сreates the system in which designers and developers use the same resources and technologies. Developer can be accounted as a system designer developer, as well as any person involved in design system creation, audit & updating processes. | High | Creates a consistent experience across a range of products. Creates, audits, updates design system. |
Fixes detected bugs. | |||
Design system QA | Tests the design system components, creates testing cases and scenarios, reports the issues. | High | Tests the created |
components, is involved into the |
standards' creation. |
Design system designer / UI / UX | Designs fundamentals for design system. | High | Designs the components, styles, layout, fonts etc. Revises designs after developers' and stakeholders' audit. |
Developer - DS user | Responsible for websites functionality and interfaces development, updating, audit, data flows etc. They use components code base of design system, submitted standards and rules. | High | Reuses functional elements–components within design system to update or create websites. Exports the required elements, change styles & customize components according to the brand |
requirements & standards submitted. Uses design system usage guide. |
Designer / UI / UX - DS user | Responsible for websites design development. They use design basics, style guides, |
tokens & components etc. submitted within design system. |
Medium | Replicate and update designs quickly by utilizing premade UI components and elements. |
Models up new designs for |
components which are not included into the design system but are needed. References to created design tokens. |
QA |
Responsible for quality |
assurance of all websites functionality and interfaces. They use standards base in design system. | Medium | Uses accessibility, performance and other standards submitted in design system documentation. |
Copywriter | Responsible for texts' and other content development for the website | Medium | References to design system during content preparation. | |
Content manager | Audits, updates, creates content within the website. | Low | Uses design system outputs in course of content preparing and updating. Uses recommendations for organisms content modelling. |
| |
Project manager | Responsible for the website related project plan implementation. |
Low | Uses design system as a tool while planning and executing websites related project aims |
ВА | Responsible for project documentation development. | Low | Uses design system outputs as a source of truth while preparing related documentation. | |
Reckitt company | Brand-agnostic visual changes are required due to a change in standards | |||
CDO brand requests a significant change to site structure, requiring new templates but no new functionality | ||||
A CMU requests new functionality that is very specific to their local market needs only. | ||||
A brand changes its visual identity and needs to roll out across multiple markets, but potentially in 'batches' rather than all at once. | ||||
A powerbrand local variant (e.g. http://napisan.it is lysol or http://neophos.dk is Finish) need a modification to the styles of the Powerbrand. | ||||
A CMU chooses to launch or shut down direct-to-consumer shopping capabilities. | ||||
A part of the Husky stack is added, removed or adjusted. | ||||
A CMU requests extra functionality in a template so they can "slide in an extra bit of content between these two areas". | ||||
A market wants to significantly adjust their site map from the globally recommended format laid down by CDO brand. | ||||
A CMU requests new functionality that is of value beyond just them and not currently available. | ||||
A CDO brand requests a function update that is only relevant to that brand or a portion of brands. | ||||
Markets activate A/B testing for CRO. GDPR markets face cookie issues and want to explore server-side testing. | ||||
A Reckitt brand with a separate site, app and Alexa skill wants to combine all three into the same headless stack. | ||||
Reckitt brands want to start moving into content personalisation | ||||
A CMU extends its site to offer multi-lingual support | ||||
A market wishes to consolidate multiple brands into one region-wide site for efficiency | ||||
Reckitt chooses to restructure individual domains under a gTLD |
from http://airwick.co.uk to airwick.com/uk) | ||||
An existing component is improved by extending and should be available widely (e.g. adding 'callouts' to product cards - new, bestseller) | ||||
Accessibility or performance issues have been found in a component already released and in use across the sites using the system. |
Detailed use cases analysis
...