-
Notifications
You must be signed in to change notification settings - Fork 0
Assumed Design System user needs
As a service designer, I will need to know how to design a service that has the fewest number of pain points.
Reviewing existing user patterns to find out how to structure my new service is essential. Working out what common entry and exit points have been previously tested and how users work their way through a service. These include how searches should be presented, what error pages should look like and how much I should split up complex tasks.
As a visual designer, I will need to know what components and styles are on offer.
I need to see a list of common components with advice on when and how to use them. Knowing and understanding how components should be used, ordered and nested and what considerations need to be made is important to me. I need advice on how to use components easily within the prototype kit and what options are available. Advice on typography and colours to ensure I stay on-brand is also a key requirement.
As a content designer, I will need to understand our content strategy.
I need hard rules on things such as date formats that I can follow when writing for a service as well as guidelines on things like language, tone and spelling.
Advice on how to write links in an accessible manner and how long to make headings would be helpful as well as common page structures and hierarchies.
As a frontend developer, I will need to be able to understand how to implement components in my service.
I need to be able to find the HTML, CSS and JavaScript for any component as well as the Nunjucks macro if I am using Nunjucks. I need to be able to understand how I can use components in services where Nunjucks is not available. Knowing how components can be extended or customised would be useful.
Information regarding typography and other styles will help me ensure I can fully replicate the visual designer's prototypes.
As a product owner, I will need to see examples of how my service could look and explore common patterns in services such as the design system itself.
I need to be able to see live examples of cookie banners, accessibility statements and other parts of a service beyond the core offering that I need to consider.
Examples that I can link to in order to communicate my ideas would be helpful.
As a tester, I will need to validate prototypes and built services against set standards.
Having a single source of truth for components, patterns and styles allows me to compare the finished product against a public-facing, established look and feel in terms of both visual design as well as semantic HTML standards.
As a performance analyst/analytics specialist, I will need advice on how to set up, maintain and measure the performance of a service.
I need to be able to establish metrics in a consistent and useful manner and understand how existing tracking patterns have helped make good decisions in order to shape services for the user.
As an accessibility specialist, I will need advice on how to ensure consistent accessibility standards to our services.
Having information about the latest standards and guidance will allow me to help create accessible services that meet the service standard.
I would also benefit from being able to link to and share information from the design system in order to help boost knowledge and confidence around accessibility within the organisation.
As a member of the branding team, I will need somewhere open and accessible to document and share our brand standards from a web perspective.
I need details such as how we use colours, typography and visual imagery to create a consistent and powerful brand image across all our services.