Contribution model
The GOV.UK Design System was originally built on a culture of cross-government collaboration, and since early on the Design System has been open to contributions. Over the years we’ve learned a lot about how to make this work well, and we iterated the contribution model in 2023.
This forms the basis of our product operating model: how we combine evidence and perspectives from across government to deliver a useful, usable, consistent and versatile design system for service teams across government.
There is no one-size-fits-all process for how we work. The contribution model is process agnostic, and there are many processes that could happen to create value at different stages of the model.
View the model
You can see the model and the activities we do at each stage in a spreadsheet or watch the video that describes the model. The model shows team members what stages we work through, who does what at each stage, and what’s expected of them.
Roles and responsibilities
We work in a multidisciplinary way. Many people contribute to the work happening across the stages of the contribution model, but some people have a clear role and responsibility to drive things forward. We also rely on each other to provide the necessary inputs at each stage.
For example, a designer will consolidate multiple designs to define a versatile style, component or pattern. Designers need evidence as source material for that, which they may get from the user researcher.
When not playing a driving role, people play either - a supporting role, contributing to work at this stage, or - need awareness of what’s happening, so they can have input later.
The team collaborated on defining roles and responsibilities in a workshop during 2023. This spreadsheet shows the results.
Prioritise what to work on
The product manager, lead developer and lead designer play a driving role. The delivery manager, user researcher and community designer play a supporting role.
The product manager requires good-enough data to make realistic calls on what’s valuable, and input from delivery, design and development to understand what’s feasible.
Gather evidence
The user researcher, community designer, developer and designer play a driving role in gathering evidence. The product manager, accessibility specialist and content designer play a supporting role.
The designer and developer need examples from the community, which the community designer and user researcher help facilitate.
Consolidate designs
The designer and developer play a driving role. The accessibility specialist, community designer and product manager play a supporting role.
The designer and developer need to know the design direction or rationale for any constraints.
Scope to something deliverable
The product manager and delivery manager play a driving role. Everyone else plays a supporting role.
The product manager and delivery manager need to know the major risks or uncertainties that need exploring and the extent of possible variations.
Create a rough proposal
The designer and developer play a driving role. The accessibility specialist, content designer and product manager play a supporting role.
The developer and designer need someone to communicate with the working group to let them know about the upcoming proposal.
Build a working version of the thing
The designer, developer and accessibility specialist play a driving role. The content designer and technical writer play a supporting role.
This is a highly collaborative stage of the model.
Do more user research (only if needed)
The user researcher plays a driving role. The accessibility specialist, community designer and product manager play a supporting role.
The user researcher needs information from the designer and developer in order decide whether research is necessary.
Build a robust version of the thing
The accessibility specialist, content designer, delivery manager, designer, developer, technical writer and user researcher play a driving role.
This is a highly collaborative stage of the model.
Publish
The community designer, content designers, developer and technical writer play a driving role. The delivery manager, product manager, lead developer and lead designer play a supporting role.
The content designer needs a plan and expected audience for communicating the publication.