Decide on way to present 'other elements' guidance in Navigation pattern (all cycle)
calvin-lau-sig7 opened this issue · comments
What
Decide how we present guidance on navigation-related elements in the pattern. Aka the guidance under the "Adding other elements alongside navigation" heading
Why
We want to tell service teams specific guidance on how to plan and design certain navigation header elements.
We're not entirely confident on what'd be best for most services, but want to give some form of guidance to establish consistency and encourage feedback from services.
For example, instead of our usual method of deciding what's best based on user research, we could frame guidance "based on a survey of government services", presented as suggested guidance "to help with consistency".
Who needs to work on this
Content designer, interaction designer
Who needs to review this
Navigation squad, working group?
Done when
- Decide on rationale for giving guidance (Why should service teams follow our guidance?)
- Evidence our guidance (What research have we done? How have we come up with our advice?)
Jotting some rough ideas, open for discussion:
Why should services follow our guidance on how to plan their navigation?
- ensure consistency amongst services
quote from steering group: “search is key, very important [users need to know that] search is for the service not the whole of GOV.UK” - best practice for visual hierarchy and content prioritisation
quote from steering group: “important to not confuse users with too many things at the same time” - we want to keep design system code as robust as possible and “design out” risk caused by unusual implementations
e.g. not placing the phase banner between the GOV.UK header and service header navigation
What research work have we done?
- survey of top 100 services, looking for most common implementations, asking what they’ve done, asked about other implementations
- consult with working group and steering group
- desk research, considering overall user needs when using government services
Closing issue, as remaining steps will be covered by #3880