Build a repeatable framework to collect examples of how the Design System is being used in services

[kellylee-gds]

Brief

We want to collect examples of how the Design System is being used, starting with the top 75 services on GOV.UK.

This is so we can:

• understand how they're using our components and patterns
• help us understand which are the most used components and patterns
• understand where teams are not using the Design System / our services
• where our components and patterns are being iterated (to help with future prioritisation)
• any common components and patterns missing from the Design System
• we build a repository of services for looking an examples of how things are being used
• tracking crown updates (stretch)

For this first cycle we will focus on building a repeatable framework that can be used by the team to collect and analyse examples on an ongoing basis.

Epic lead

Ciandelle

Driving role(s)

Designer, Technical Writer

Supporting role(s)

Senior Delivery Manager, Lead Frontend Developer

Build a repeatable framework

Beta Give feedback

1. Explore what types of information we can collect about services from desk research #3592
   +0
   

   
2. Speak to the Navigation squad about the similar exercise they have just done #3591
   +0
   
3. How do we record and store the information we collect from services #3595
   +0
   

   
4. Build a prototype of an information database using Airtable #3631
   +0
   
5. Build a prototype of an information database using Notion #3632
   +0
   
6. Build a prototype of an information database using FileMaker #3647
   +0
   
7. Decide what information to collect from services #3594
   +0
   

   
8. Decide which services to prioritise collecting examples from #3596
   +0
   

   
9. Establish a methodology for analysing services #3597
   +0
   

   

[kellylee-gds]

There may be collaboration with folks external to the team, eg Jonathan in IA team.

[kellylee-gds]

Preferable to buy a tool that can do this rather than build it ourselves (this would be an additional cycle, with more developers in the squad).

[kellylee-gds]

We'll have daily stand ups, with one longer stand up once a week for more in-depth conversations. We'll have a dedicated Slack channel for conversations. We'll have a more in-depth kick off meeting on Tuesday next week, possibly in person.

[kellylee-gds]

This is based on the assumption that collecting this data is valuable to the team, therefore has value in being repeatable framework.

[kellylee-gds]

Questions from mid-cycle demo:

• Should we speak to Uzma Razaq (GDS ResearchOps manager) who may have budget for tools we could use for this?
• Have we considered a wiki?
• Could Wappalyzer help us find further services?
• Should we cross-reference our services list with the list of services GOV.UK are using to track crown updates