Our existing service is a transactional journey, where a user can provide us with information about themselves for us to identify if they are eligible for a payment. If the user is eligible, they can then proceed to submit a claim for payment.
We're now designing an iteration to this journey, which will allow for some users to complete the journey more efficiently. This post is about the first step of that iteration.
Rather than ask the user to provide complex information about their qualification, where they work, and who they are - we should be able to gather that information automatically, if we have some key identifiers about the user. We've established that we can use the information provided by the DfE Identify service to gather what we need to know about the user.
We've therefore designed an iteration to the start of our journey, to provide users with two routes. These are:
- sign or create a DfE Identify account
- continue without using an account
We've offered users the route of continuing without using DfE Identify, as there's a business requirement for the user to be able to complete the journey without creating an account - which keeps the original journey intact. We'll be looking to iterate content to accurately communicate the benefits of using a DfE Identify account.
If a user chooses to use DfE Identify, they will be routed to the identify service where they can sign in or create an account, and then routed back to our service.
We have included the DfE Identify journeys in our prototype so we can accurately research with the end-to-end journey and identify any pain points.