govuk-design-system
govuk-design-system copied to clipboard
alphagov
Undertake a review of insights and feedback shared by users on selected components and patterns
Brief
To start this brief, #4281 must be completed in order to establish which components and patterns to look at first.
In this brief, a small disciplinary squad will review the community backlog and our repositories, reviewing insights and feedback from users and creating proposal iterations.
The squad should identify iterations which are low risk, and which need further research, with a view to making iterations in the next cycle.
As part of this brief, we should also establish a regular cadence of reviewing all our components and patterns, and create an OKR to help us achieve this.
Epic lead
Calvin
Driving role(s)
Owen, Hazal, Kelly
Needs awareness
Share findings with whole team
Tasks
- [ ] Review all open issues on govuk-design-system and govuk-frontend repositories and add labels to any issues which are related to Checkboxes, Accordion, Button, Character count or Tabs
- [ ] Priority order for review: Accordion (week 1), Tabs & Checkboxes (week 2), Button & Character count (week 3)
- [ ] Async review of each component, with insights and feedback collated on this spreadsheet: https://docs.google.com/spreadsheets/d/1vhEOW27a7WYpeaI5XsNt_ys7EIeOxGZXj33h0Erk12I/edit?gid=0#gid=0
- [ ] Whole group discussion of feedback
- [ ] Identify possible iterations, or where we need further evidence to make a decision
- [ ] Share with the team for feedback
- [ ] Document in GitHub as future brief or small story
Week 1: Accordion
Monday: Cycle planning & add labels to open issues on repo
Tuesday: Async review of Accordion backlog & discussion
Wednesday: Identify iterations & create briefs / small stories
Thursday: Review by wider team
Friday: Review feedback from the team & make any changes
Week 2: Tabs & Checkboxes
Monday: Async review of Tabs backlog
Tuesday: Discuss findings on Tabs & identify iterations
Wednesday: Async review of Checkboxes backlog (non-meeting day)
Thursday: Team away day
Friday: Discuss findings on Checkboxes & identify iterations
Week 2: Button & Character count
Monday: Async review of Button backlog
Tuesday: Discuss findings on Button & identify iterations / Async review of Character count backlog
Wednesday: Discuss findings on Character count & identify iterations
Thursday: Create briefs and small stories / Show & tell
Friday: Document process and decide whether it's repeatable
Chat with Imran 22/1:
Potential future engagement when we start to iterate a component or pattern. Let users know they've contributed an iteration and thank them. If there's something complex we're not sure about, we could run a workshop with the community to help guide us.
For this cycle specifically, we could do shout out at the beginning of cycle to let us know of any burning issues with these particular components.