Discovery within DWP’s first design system
Introduction
DWP has scaled a lot since I was first here, back in 2014. Hiring designers of differing skills - interaction, content, user research, and with gov.uk getting 922 million visits per year - there is a great need to have services to be consistent and accessible for all.
This is where a design system comes in, treating this as a product that will provide a collection of tools, guidance and standards that can be used together to design and deliver services will shape us for a better and more accessible future whilst providing an ease and consistent use for our end users.
The goal
The need for Design Systems goes hand in hand with the need for efficiency, consistency and scale of design.
Efficiency: Instead of repeatedly designing the same components/patterns, design systems enable reuse
Consistency: Components/patterns are designed and built with a shared set of principles and assurances
Scale: increased efficiency and consistency allow more service to be delivered faster.
In short: To make it easier for teams to find, use and share the patterns they need to design and build services
- get buy-in from all levels and roles
- get a "thing" up and running
- get contribution model up and running
We break this down into three handy segments: +- educating / adoption / engagement -+
What do we know?
- The design community have shared a library of patterns and code not covered by GOV.UK in different platforms over 3 years.
- The design has increasingly become more complex and involves more distributed, cross-functional disciplines.
- Users are not sure how to contribute to existing patterns or components
- We need to up the output to provide value and support
Outcome (KPIs)
Increase the usage of DWP patterns, traffic to the design system, contribution and engagement with new and existing backlog items, improvements on accessibility, performance and shared knowledge, code is activitly maintained - a lot more covering many differing roles and users!
Hypothesis
By improving and implementing a design system, services will successfully be using the right and accessible pattern.
Where to start - Discovery?
I joined as the teams first Interaction Designer, and my first task was to update the teams purpose, align current and future plans to user needs, and rearrange the backlog against delivery.
In this session, I wanted to know what are the users, what are their needs, what does their success look like.
And the big one that I felt was going to be huge, get all the backlog out on the board and tidy it up, group it into similar themes, (we had a lot of duplications), I also challenged the team on what can we do to assist in getting more out of our community, things like tracking conversations to building trust and also do a little work around technology, what can we do that could be a quick win in removing tech debt around the website (for example).
Upon completion of these, we dot voted and highlighted which ones were to be worked on next (this ranged from opinion, to feedback on the github issue, to people just asking for it) and finally highlight which ones we need to do user research on as opposed to a pattern we could put out as "experimental".
Finally, the session ended with a system that I love doing,
Now, next and later.
We take all the post its from the user needs (and successes) and the backlog and put them in a column to work on and decide the order.
In my experience this has helped so many teams gain buy-in internally as we can card sort all our future work-tickets in order.
Next - community education
Moving from the welfare dept of DWP to this team, I got invited to speak to the internal community (approx 100 people) and introduced the team, highlighting what we are working on, whats next and finally what challenges we faced and tried to be as transparent as possible, this allowed questions, ideas and instigated my DM's on slack to erupt!
One thing I did highlight was “the design system is not owned by us, we just put the jigsaw together, without the community a design system dies - I can push and push for feedback and solutions, but I need contrition to help us get somewhere in the future”. On that note I reminded the group what we are working is powered by focus groups, workshops and need, so we had items in our backlog on the cusp of being launched, we even had an item of ours going into GDS' pattern library (which is the end goal).
Where we are now and what next for me
The Design system is a living thing, there is no end, if we do this right the service will forever live, but until that time I need to redefine how the contribution model works, I need to reinvent, reinvest and reignite (I made it to three words) my colleagues to feel the need to contribute and give back, but first we need to show value.
I realised the lack of success within our current contribute model, it was not working and needed customising for us - with that in mind, I am running sessions that have united teams, services and locations to help us get talking freely - less about work and more about THE work, specific work that helps us all.
I also know there is always a need around showcasing the work we do, the design doesn’t automatically come with a value output, and always promoting and showing the purpose of the work we and I are doing is key and to do this means public speaking, workshopping and communiting openly and honestly.
With the community vibe in mind, I decided to trial the following:
Office hours - where we share an hour of the week/month and explain what we did (i guess its similar to design community show and tell)
Power hour - where we open a slack channel for drop-in calls, and discuss their patterns and talk openly (a show and tell for them, lead by them)
Brown bag - we get folks who do not want high-level talk but a deep dive (optional attendance) into a pattern - bring your lunch!
A survey - find out how to find how the design system is working for you.
It’ll be an interesting test to see which sinks or which come through as a shining light - plenty of work to do in this area but, all projects have challenges and all projects need the work, I’m just glad it’s this kind of work where I can control and have a lot of input in the outcomes (whilst trying new things and learning).
This case study is not finished, and will not be for a while, but this is phase 1.
All sounds simple eh? Anyone who worked on a design system knows it isn’t - I need to get the community to feel it’s part of their role, their need, and to find time to provide us with the solutions or problems - I also need to remember this is key in solving any contributing issues, many Systems in the past fall into the styleguide where it becomes one person leading the charge and making decisions - I see myself as the person who puts the jigsaw together, not the jigsaw maker.
What I learned so far
With every project, it needs a strategy, a purpose and I still feel design system’s arent crystal clear on this, so its around finding “what works for us and why are we doing it”, which I think we are clear on now.It is important to communicate wide, down and up to everyone to teach them the values of a design system, the biggest takeaway I could give anyone is let people know it’s a slow process, we strive for good patterns not just patterns. It’s quality over quanity.
Finally, work on your contribution model, in a pinch it can become more powerful than discussions, using a well made visual has saved me a ton when words fail me due to presentation-fatigue or just overexplaining.
It can also be the difference between getting funding and support to “doing it yourself”, and I can not think of a recipe for failure more than that being a system.