Use the iterated contribution model to deliver a community contribution of ‘Navigation’

[kellylee-gds]

What

Using the iterated contribution model to explore which Navigation components are needed in the Design System.

Why

• Navigation was voted the most needed component in the 22/23 prioritisation survey
• The One Login programme have designed a new header with sub-navigation, backed by research, which we can help roll out
• It’s an opportunity to look at different contexts and use cases, e.g. internal services like case management systems as well as public-facing transactional services
• An opportunity to test the new contribution model
• Create artefacts and templates that allow us to scale running community sessions across the team

Epic lead

Charlotte

Who needs to work on this

Stage 1 team:

• Charlotte (leading)
• Designer (supporting)
• Developer (supporting)
• Community Designer (supporting)
• Product Manager (supporting)
• Interested external parties to form a steering group

## Prerequisites
- [ ] Epic lead has capacity to lead this work
- [ ] Published 'Help users to share user research' guidance
- [ ] Create a tailored version of contribution model for Navigation specifically
- [ ] Speak to One Login programme to share our plans and understand any constraints they have, and whether it will impact us

## Stage 1 (3 months)
- [ ] Gather evidence epic
- [ ] Consolidate designs epic
- [ ] Scope to something deliverable epic
- [ ] Create proposals epic
- [ ] First working group review epic

[kellylee-gds]

From scoping session on 15/08/2023:

What are the major risks?

• Any changes to the working group's responsibilities
• Scope creep at certain junctures - make sure we make conscious choices about scope so that we don’t try delivering everything in one go

[kellylee-gds]

We will begin Stage 1 of this work when the WCAG 2.2 design sprint research has concluded, findings have been analysed and next steps have been agreed.