-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: update apply service pattern page (#1033)
* docs: update apply service pattern page * Service pattern updates * Updating layout and subsection --------- Co-authored-by: Rob McCarthy <[email protected]>
- Loading branch information
1 parent
1a20657
commit dcd3f48
Showing
3 changed files
with
162 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,159 @@ | ||
--- | ||
layout: layouts/service-patterns.njk | ||
title: ‘Apply’ service pattern prototype | ||
--- | ||
{% tabs "Contents" %} | ||
{% tab "Overview" %} | ||
|
||
## Overview | ||
|
||
A cross-government team has developed a prototype to help teams design an ‘apply’ journey in a service. It contains some common parts of this service pattern, which could be developed into a reusable pattern for government. | ||
|
||
This prototype was created from multiple ‘apply’ journey examples in DWP, MoJ, DfE, Defra and HMRC. These services were designed for different users and contexts, but the prototype shows the common and reusable parts of them. | ||
|
||
The prototype has 2 parts: | ||
|
||
- user needs for internal and public users (for teams to validate) | ||
- user scenarios | ||
|
||
This is part of [work to develop service patterns across government](/service-patterns/). | ||
|
||
### How to use service patterns | ||
|
||
Service patterns are starting points. They give you some user needs for your team to explore and validate. You still need to do research and design - service patterns do not replace any of these activities. | ||
|
||
We’ll share case studies and examples of this service pattern in use. | ||
|
||
### How to give feedback | ||
|
||
We’d like some feedback on the usefulness of the prototype. | ||
|
||
Please complete the [apply pattern prototype survey](https://forms.office.com/Pages/ResponsePage.aspx?id=KEeHxuZx_kGp4S6MNndq2ML_UAYVtf1Jv53R4CVxx1hURFpPVDhUQVJVNkQxMzQyODRON0kzVVpKUi4u) by the end of April 2025. | ||
|
||
Or you can email your responses to the 3 questions: | ||
|
||
1. Would you find this concept useful for designing services? | ||
2. Would this prototype help you design an apply journey in your current role? | ||
3. What else would you value in a service pattern like this? | ||
|
||
Send your answers to [[email protected]](mailto:[email protected]). | ||
|
||
### Other resources for the ‘apply’ pattern | ||
|
||
You can also find [apply patterns in the GOV.UK Design System](https://design-system.service.gov.uk/patterns/). | ||
|
||
{% endtab %} | ||
{% tab "User needs" %} | ||
|
||
## User needs | ||
|
||
The cross-government work to identify an ‘apply’ service pattern followed a user needs approach. | ||
|
||
### User needs for public-facing services | ||
|
||
#### Higher confidence: | ||
|
||
- I need to be treated with respect, feel understood and not judged throughout the process. | ||
- I need the process to be suitable for my language and/or communication needs. | ||
- I need to easily understand the whole process, know what I need to do at each stage, how long it might take and what relevant information I need to provide. | ||
- I need to know how to get access to help or support if I need it during the application process. | ||
- I need to enter information as few times as possible to avoid repeating my story. | ||
- I need to trust that any third party will act in a way that does not leave me vulnerable (to fraud). | ||
- I need to know I can save my application progress and return to it. | ||
- I need to have clear questions to enable me to understand things and provide the correct supporting evidence. | ||
- I need to get confirmation of submission of my application and know what the next steps are and when they will happen. | ||
- I need my completed application and supporting information to be saved for future reference. | ||
- I need to trust that the data I provide will be stored securely, kept safe and only used for the specific application. | ||
- I need to trust that the right decision will be made based on my individual circumstances and the information I've provided. | ||
- I need to get reassurance of progress. | ||
|
||
#### Lower confidence: | ||
|
||
- I need to apply with a channel and format that suits me and my circumstances. | ||
- I need the service to look and feel official. | ||
- As a third party, I need to be able to upload and receive correspondence for the claimant. | ||
- As a third party, I need to easily be able to review information to help the claimant. | ||
- I need to know a third party will be able to act on my behalf if needed. | ||
- I need to be kept safe throughout the ‘apply’ process (for example, if I'm a victim of domestic violence). | ||
|
||
### User needs for internal services | ||
|
||
#### Higher confidence: | ||
|
||
- I need to easily view relevant information about the applicant so that I can understand the full picture. | ||
- I need to be able to access other systems that might be helpful so that I can determine eligibility for the application. | ||
- I need information to be in as few places as possible so that I do not have to move between systems. | ||
- I need to feel confident in the systems that I'm using and the questions that I'm asking so that I can advise my claimants accurately. | ||
|
||
#### Lower confidence: | ||
|
||
- I need a clear and consistent process to follow so that I can ensure all applicants have the same experience and I can ask for help when needed. | ||
- I need to feel valued and supported so that I can perform at my best and give applicants a quality experience. | ||
- I need to communicate effectively and in a way that suits the applicant so that I can feel confident. | ||
- I need to be empathetic and sensitive to applicants so they trust me and know I’m listening. | ||
- I need to be able to verify an applicant’s identity so that I can progress. | ||
- I need the systems I use to be efficient and reliable so that there are no delays. | ||
- I need to accurately capture applicant information so that there are no mistakes. | ||
- I need to ensure I only ask relevant questions to applicants so that I can collect the right information. | ||
- I need a clear list of supporting evidence (where necessary) so that I can easily validate and know information is correct. | ||
- I need to make sure sensitive information is only seen by relevant people so that the department meets GDPR standards. | ||
- I need to know that the information we hold about an applicant is up-to-date so that I can advise on next steps appropriately. | ||
- I need an efficient way of communicating personal data changes across products so that it saves time. | ||
- I need to be confident the data I'm accessing is accurate and up-to-date. | ||
- I need to have confidence that users have access to relevant guidance to make a decision because I cannot advise them on their specific circumstances. | ||
|
||
{% endtab %} | ||
{% tab "Stages and steps" %} | ||
|
||
## Stages and steps | ||
|
||
### User scenarios | ||
|
||
These are some scenarios you may have to design for as part of your service. | ||
|
||
#### Happy paths: | ||
|
||
- Individual applying for themselves | ||
- Individual applying on behalf of someone else | ||
- Business or organisation applying for themselves | ||
- Business or organisation applying on behalf of someone else | ||
- Staff user applying for something on behalf of an individual, business or organisation | ||
- Multiple user types contributing to the same application | ||
|
||
#### Variations: | ||
|
||
- Additional application information is needed before it can be processed | ||
- Evidence in support of application needs to be resent because it's deemed unsuitable | ||
- User decides they want to withdraw their application | ||
- User information changes between starting application and completion | ||
- Eligibility to apply changes while applying | ||
- User pauses application and returns to it | ||
- User switches channel during application | ||
- On checking their answers, user changes something which significantly affects subsequent answers | ||
- User requires point of contact for support | ||
|
||
#### Unhappy Paths: | ||
|
||
- User does not understand what they need to complete application | ||
- User does not meet the eligibility threshold or criteria | ||
- User cannot find the application form | ||
- Application is missing information or contains the wrong information | ||
- User did not receive receipt notification | ||
- Third party does not complete their part of the application | ||
- Time limit elapse (for example, SLA for response) | ||
- Application window closes | ||
- User is logged out of the service part way through their application due to time out | ||
|
||
{% endtab %} | ||
{% tab "Contribute" %} | ||
|
||
## Contributing to MoJ service patterns | ||
|
||
You'll likely design multiple instances of potential service patterns when you develop new products or services. | ||
|
||
Contact <a href="mailto:[email protected]">Martin Ford-Downes</a> if you have a potential service pattern idea or want to help us work on others. | ||
|
||
We welcome feedback from everyone, including from people outside of the Ministry of Justice. | ||
|
||
{% endtab %} | ||
{% endtabs %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters