Research and Insights backlog #4401
Comments
trang-erskine
added
epic
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
trang-erskine
added
epic
Research
This is research we're currently doing or planning to start soon
Explore the needs of users and monitor satisfaction with the Design System and Frontend
Gather data which narrates the benefits of the Design System and Frontend
Undertake a review of insights and feedback shared by users on selected components and patterns
User stories
These are user stories based on insights from research. Labels identify the source of evidence for each story.
User story: As a service owner, I need a way for my team to build, maintain and improve the service in a way that doesn't require a lot of coding knowledge so that I can run the team as cost effectively as possible.
User story: As an experienced user, I need the Prototype Kit to be free from stuff, for example, docs and deprecated code so that it doesn't get in the way of what I'm doing.
User story: As someone without a lot of coding knowledge who doesn't use the Prototype Kit regularly, I need advice and guidance to help me understand how to use it.
User Story: As a user, I need permission to access the Prototype Kit from my organisation so that I can use it to build prototypes.
User story: As a user new to the Design System or my role, I need to understand that the Design System components and patterns are one element of a whole and understand it's relationship to Frontend so that I use it effectively.
User story: As a user, I need to be able to navigate the Design System space in Github so that I can participate in the community, share knowledge and ask questions.
User story: As a user I need the Design System content to be consistent so I have confidence in it and I know I am building something based on the best evidence and advice.
User story: As a user of the Design System, I need content structured so that it's easy to digest.
User story: As a user I need a taxonomy for components and patterns I understand, so that I can find what I'm looking for without having to open up many different components and patterns.
User story: as a user, I need help to identify the location of something I'm looking for, so that it's easier to remember where it is the next time I look for it.
User story: As a user I need the right components and patterns so that I can build the (internal) services I am working on.
User story: As a user I need to understand that the Figma Design System library is one element within the Design System environment so that I use it correctly in conjunction with GOV.UK Design System guidance and Frontend.
User story: As a user I need the Design System Figma library to be up to date so that I can be sure that it reflects the current version of GOV.UK Design System.
User story: As a service owner/team lead I need to know when major Frontend updates are going to be released so I have time to schedule in the work required to update Frontend and we continue using the most up to date version.
User story: As a user I need to know when updates have been made, so that I am confident I'm using the most up to date version of a thing and won't have to re-do work.
User story: As a user I need access to community support so that I can make the best use of the Design System and Frontend.
The text was updated successfully, but these errors were encountered: