Skip to content

Build a working version of feedback link which can be used by test partners #5207

@kellylee-gds

Description

@kellylee-gds

Brief

In cycle 26, we agreed to proceed with the below prototype for the mvp iteration of feedback link.

Initial prototype

Building consistency with the feedback link used on GOV.UK mainstream pages, the feedback mechanism will move to the bottom of the page, above the footer.

Image

When a user selects the "Feedback" button, the state will change to provide more information to enable users to provide higher quality feedback:

Image

Our first actions this cycle should be to:

  • refine the design and content
  • agree whether we want to proceed with the two-state approach, or move the expanded content into the initial state
  • agree on the content of one or both states, referring back to our user needs to ensure we're addressing them
  • agree on which changes will be required to the existing phase banner as a result of this iteration
  • inform stakeholders, such as the Service Manual team or GOV.UK (possibly Nav), of our plans

We don't believe at this stage we need to do any further community engagement, other than with test partners and the stakeholders mentioned above.

When this has been agreed, we can begin to build a working version which can be shared. We'll need to consider how we provide a working version, how robust it needs to be, and it's relationship with GOV.UK Frontend and the Design System website.

We'll also need to decide the testing parameters ahead of kick off sessions with test partners. We will need to decide:

  • methods for testing in a live service
  • testing period
  • how the feedback loop will work

We should aim to hold kick off sessions with test partners in the final week of the cycle.

Squad

@hazalarpalikli @lewisdarlow-gds @owenatgov @calvin-lau-sig7 @lamiece-gds @kellylee-gds @trang-erskine @emma1carter @NickColley

Consulting: @selfthinker

Further detail

Metadata

Metadata

Labels

epicEpics are used in planning project boards to group related stories

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions