Open bencullimore opened 5 years ago
We had a beta banner on NHS login. It caused issues during Apple App Store approval for app based services using NHS login. Even thought the app using NHS login wasn't in beta, the use of NHS login resulted in rejection.
This prompted the removal of our banner, which looked like this: We questioned what the banner was doing for users. Apart from the link to T&Cs we didn't see a benefit.
We could see the benefit of a banner that provided feedback, but we had that elsewhere in the page.
Here's another example of one in use, again no real user benefit:
From @GrilloPress:
I think we have to be very cautious about things like phase banners.
In health context, trust is key.
And though in beta we may be a little less polished than live, we still have the same standards of clinical assurance. Beta can undermine that when it shouldn’t
Same with “beta” data services. There will be the same standards of data security.
We shouldn’t be undermining people’s confidence in our services. Especially in the healthcare context. And if beta means “we’re learning and will change things to meet user need” well shouldn’t we always be doing that anyway?
I am very much of the mindset that unless it meets a user need - phase banners tend to add very little overall. However there are potentially times when they might.
For example, I work on service which has more than one version of the service running at the same time i.e. a purely offline application (live), and one that only certain groups can apply online for the time being (private beta).
Users obviously need to understand the 2 versions, and which route suits them best. For this use case, the phase banner may come in handy.
I was recently assessing an NHS service and came to this page to find guidance.
It felt unfair to comment in the assessment about the banner use, so I left it out. But it would be great to get a definitive decision on here, about whether we do banners or not.
Note that GOV.UK suggests some alternatives:
Just a possible hypothesis if a banner at the top of a page were to contain a "feedback" link: If we ask people for feedback before they read the content of a page Then we will get premature feedback before someone has had the chance to read a whole page
So, would it be best to let people know about new guidance or new styles, components and patterns without the ability to feedback until the bottom of a page?
Note that GOV.UK suggests some alternatives:
We are looking to test something like this in the service manual, perhaps with a tag "New guidance" or just "New", though it will be interesting to see if people see us as promoting new stuff, as opposed to warning them that it's new (and hence not so well tested).
I was recently assessing an NHS service and came to this page to find guidance.
It felt unfair to comment in the assessment about the banner use, so I left it out. But it would be great to get a definitive decision on here, about whether we do banners or not.
I agree.
The beta phase banner is in use at the moment on several heavily-used, COVID-related NHS services, such as reporting lateral flow test results or ordering LFT kits. It is the GDS phase banner component that has been used on these service pages.
In the absence of an NHS-specific component, is the expected approach that an available GDS component is used in the interim, an example being the Phase banner component? The Ministry of Justice design system pages make it very clear that "If a similar component is in the GOV.UK Design System, you should use that component instead."
@promisingict. Thanks for your comment. We're keen to firm up guidance on phase banners but aren't in a position to do so yet.
Generally we encourage people to start with GOV.UK components, if there isn't anything in the NHS design system. But if your user research suggests that you need something else in a health context (like the examples above), it is OK to do something different.
If you're doing any work on this, please feedback and share learnings.
I raised the issue of the phase banner with the DHSC assurance team as it came up in a recent service manual enquiry.
They fed back a general view, plus some specific comments from the team.
The general consensus in assurance was:
An adapted version of the end of service page gets more feedback than the standard banner. They haven't seen anyone change the BETA icon, though some teams have changed the wording on the banner.
@JLarbie and I have recently done some work over in TEL to look at making the phase banner better meet user needs
We believe the problem that the phase banner is trying to solve is likely to:
This work is intended to pull then focus of this element more towards user engagement. We've updated the term beta to “Feedback”. We believe that this is a much clearer message and will be more widely understood. Feedback is also actionable so users know whats expected at a glance and this follows a very similar pattern to a something put forward on the alpha gov community channel. We've also amended the text to link to the gov.uk beta page to help inform users what this means where appropriate.
we surveyed 21 users:
In summary it would appear that there is significant evidence to suggest that using the primary term ‘Feedback’ to lead the introduction of the Beta banner phase description may be beneficial in strengthening the user’s association of the process of giving feedback and improvements at this point of a website’s lifecycle.
NHS Business Services Authority seems to use phase banners on 3 of their services:
What
GOV issue on the design system backlog https://github.com/alphagov/govuk-design-system-backlog/issues/57
Why
A discovery piece ran on NHS.UK to understand what user needs the phase banner was meeting.
We came to the conclusion that there weren't any user needs, only 'product owner' needs.
Anything else