Gather evidence on how navigation is currently being used in services

[christopherthomasdesign]

Brief

By the end of the cycle, gather evidence on how navigation is currently being used in services, so we understand the different variations and use cases. Play back your findings to the team (and if you choose to, the community).

Aligns with step 1 of the contribution model. In the next cycle we will consolidate the designs and scope it to something deliverable. Don't do any scoping in this cycle, but if you feel like consolidating the designs as a stretch goal, that's OK.

Epic lead

Charlotte

Driving role(s)

Designers, developers

Supporting role(s)

Designer

Further detail

• Think about how to involve the community, and what we would need to start steps 2 & 3 of the contribution model in the next cycle.
• This theme got the most responses in our survey in 2022 – some of the respondents have given permission to contact them, that might be a useful avenue
• Some community members have shared designs and insights here: Navigation — we want your input (examples, research, code) #2376
• There is further discussion here: Navigation govuk-design-system-backlog#76
• One Login is an important dependency – they have created a header for services with logins to use, we need to bear in mind that more and more services will use One Login if they have account-based features

Desk research

Preview Give feedback

1. Desk research of navigation discussions (Mia) #3522
   +0
   
2. Desk research of backlog prioritisation survey data 2022 (Mia) #3526
   2 of 2
   +0
   
3. Desk research of design system analytics (want to look at header component page and search box) (Charlotte) #3490
   +0
   
4. Desk research of the impact of the number of items within a single navigation element #3549
   +0
   
5. Desk research of how accessibility intersects with navigation #3476
   +0
   
6. Look at interesting 'Navigation' on existing services #3531
   +0

Other internal tasks

Preview Give feedback

1. Ensure navigation related conversations with users are recorded in the discussion space
2. Check other government department libraries and design systems for navigation component/patterns #3474
   +0
   
3. Check non-UK government design systems #3475
   +0
   
4. Prepare what we want to chat to one login about (governance, what's next) #3530
   community +1
   
5. Prepare something to collect examples and share between the squad (mural, google slides, figma etc.)
6. Collect all design system dependencies (Charlotte) #3494
   +0
   
7. Chat to one login (enable them to still do what they need to do) #3557
   +0

Community engagement

Preview Give feedback

1. Prepare what we will need to ask users
2. Review messaging to community from user researcher
3. Contact users directly who gave permission in backlog prioritisation survey 2022
4. Contact users openly on slack
5. Split and plan things we want to know from users / community (Charlotte) #3540
   +0
   

   
6. Run an open session on sharing examples with the community
7. Who are we going to share this with?

Decisions

Preview Give feedback

1. We have gathered evidence to decide: What type of service Navigation supports? (Will come out later)
2. We have gathered evidence to decide: What type of navigation? What do people use to navigate a GOV.UK page?

[CharlotteDowns]

Conclusions

We will continue to find answers to the following questions in the next cycle, Consolidate designs and form a steering group for a navigation contribution #3567:

• What is the impact of the number of items within a single navigation element?
• How does accessibility intersect with navigation?
• What are the technical concepts related to navigation?

We parked some of the community engagement tasks at this stage because it feels like engaging with users is going to be more useful once we've made a shortlist of options. We want these interactions to help us narrow our scope rather than expand it, hence this will be a main focus of the next cycle.

Our slides from End-of-cycle demo