How to measure success

We like to work with evidence.

We know figuring out how to measure success of a component, pattern or piece of content can be difficult. Although every piece of work is different this guide includes what data we have available and what measuring success might look like.

We have a range of data that will help us check if a new addition to the design system is successful or needs improving. Using a range of these will give us the best outcome

• Google Analytics
• Community discussions on GitHub
• Community outreach (X-GOV slack)
• Always on research
• Service explorer
• Surveys
• GitHub analytics
• Adoption of component in other X-GOV Design Systems

Example Scenario

You want to measure the success of a new component, as an example the Feedback component.

You might

• Open up a community discussion asking for feedback
• Add a question to the always on research, to ask how service teams are using the component
• Use analytics to see how much engagement the guidance page is getting
• Use the service explorer to see the adoption of the component

Every piece of work you might measure success differently and it’s up to your squad to decide what that looks like. This guidance is here to show what this could look like.

Review stages

We aim to have a ‘review’ meeting of the data after three months of something going live, so we’re in a position to make improvements. We can also have an optional six month check in too.

Recording findings

It’s important that we write a brief summary of the findings, the success and things that didn’t go so well, so this material can be referenced and used in future planning sessions and by other team members.

It will be up to your squad to decide how to make this data accessible and where to record it.

Ask for help

If you’re unsure of how to apply any of these techniques, or need help to identify the appropriate technique for your scenario, reach out to a delivery manager, product manager or user researcher who can help with this.