stevenjmesser
commented
1 year ago There's a couple of options for how this could work. What feels simplest and closer to a complete solution (to me) is to hand the user off to a styled SmartSurvey, which handles data storage and privacy notices, reducing the amount of work to do with Information Assurance. It also allows us to include a question asking which components and patterns are used on a service, meaning we collect more information through one form; if a form was embedded on each component or pattern page instead, that's a lot of forms to fill in!
We might also want to collect service name, organisation name and a contact email address to help with de-duplicating submissions too. Collecting the email address allows us to screen out spam submissions too. (We can suggest that mailbox is used instead of a person's email address, though both are fine.)
I've had other thoughts of how this would feed into better collecting data on usage of the design system, so would love to chat that through with anyone involved in this. It shouldn't widen the scope but will make sure all the work aligns and the data can be analysed.
calvin-lau-sig7
owenatgov
kellylee-gds
What
Add a button to the guidance where teams are encouraged to share their service name, department and consent to contact for further research.
Mvp button could be 'We have used this component".
Also consider whether the button is needed on both the component guidance and pattern, or just the component guidance.
Why
To help us track where EtP is being used and set up further conversations.
Who needs to work on this
TBC - need further info from the team before decision reached.
Who needs to review this
TBC
Done when