GOV.UK is constantly being iterated and updated and sometimes we need to draw users’ (including departments and agencies) attention to this. We do it by saying something is in 'beta'. Of course, the way we show that something is in beta is also subject to change.
Testing a new beta explanation
We're testing a new way to show users that something is in beta on GOV.UK. The explanation we are testing is: “This part of GOV.UK is being rebuilt - find out what this means.” This links through to the beta explanation on the help page.
We need to point the user to existing services, where possible, to make sure we don't get in the way if the beta can't do everything they need. In which case, we can add "Go to (organisation name) if you can't find what you need here." to our messaging to help them get to the right place.
This approach worked well on the tax disc service page: 4% of users clicked through to the beta explanation page, with 75% of them returning to complete the transaction.
Where are we testing the new beta explanation?
We're testing the new beta explanation on types of content that might be:
- subject to rapid and extensive change
- greater need for feedback
- fragile and may break
Why are we testing a new beta explanation?
We draw users’ attention to this content to ask them for their patience as we continue to improve GOV.UK, and to keep departments and agencies informed that we are updating and improving their content.
We need feedback
We know that the in-page feedback for our betas needs to be better. We're working on a couple of different ways of doing this because we know that feedback helps improve GOV.UK.
As part of making digital government simpler, clearer and faster, we're also looking at how we explain beta within transactions and services themselves, which we'll share in a future blog post.