diff --git a/app/images/claims/scaling-back-mvp/authenticator.png b/app/images/claims/scaling-back-mvp-claims/authenticator.png similarity index 100% rename from app/images/claims/scaling-back-mvp/authenticator.png rename to app/images/claims/scaling-back-mvp-claims/authenticator.png diff --git a/app/images/claims/scaling-back-mvp/before-you-start-v7.png b/app/images/claims/scaling-back-mvp-claims/before-you-start-v7.png similarity index 100% rename from app/images/claims/scaling-back-mvp/before-you-start-v7.png rename to app/images/claims/scaling-back-mvp-claims/before-you-start-v7.png diff --git a/app/images/claims/scaling-back-mvp/before-you-start-v8.png b/app/images/claims/scaling-back-mvp-claims/before-you-start-v8.png similarity index 100% rename from app/images/claims/scaling-back-mvp/before-you-start-v8.png rename to app/images/claims/scaling-back-mvp-claims/before-you-start-v8.png diff --git a/app/images/claims/scaling-back-mvp/claim-details-v7.png b/app/images/claims/scaling-back-mvp-claims/claim-details-v7.png similarity index 100% rename from app/images/claims/scaling-back-mvp/claim-details-v7.png rename to app/images/claims/scaling-back-mvp-claims/claim-details-v7.png diff --git a/app/images/claims/scaling-back-mvp/claim-details-v8.png b/app/images/claims/scaling-back-mvp-claims/claim-details-v8.png similarity index 100% rename from app/images/claims/scaling-back-mvp/claim-details-v8.png rename to app/images/claims/scaling-back-mvp-claims/claim-details-v8.png diff --git a/app/images/claims/scaling-back-mvp/claim-history-v7.png b/app/images/claims/scaling-back-mvp-claims/claim-history-v7.png similarity index 100% rename from app/images/claims/scaling-back-mvp/claim-history-v7.png rename to app/images/claims/scaling-back-mvp-claims/claim-history-v7.png diff --git a/app/images/claims/scaling-back-mvp/claim-history-v8.png b/app/images/claims/scaling-back-mvp-claims/claim-history-v8.png similarity index 100% rename from app/images/claims/scaling-back-mvp/claim-history-v8.png rename to app/images/claims/scaling-back-mvp-claims/claim-history-v8.png diff --git a/app/images/claims/scaling-back-mvp/manage-claims-v7.png b/app/images/claims/scaling-back-mvp-claims/manage-claims-v7.png similarity index 100% rename from app/images/claims/scaling-back-mvp/manage-claims-v7.png rename to app/images/claims/scaling-back-mvp-claims/manage-claims-v7.png diff --git a/app/images/claims/scaling-back-mvp/manage-claims-v8.png b/app/images/claims/scaling-back-mvp-claims/manage-claims-v8.png similarity index 100% rename from app/images/claims/scaling-back-mvp/manage-claims-v8.png rename to app/images/claims/scaling-back-mvp-claims/manage-claims-v8.png diff --git a/app/images/claims/scaling-back-mvp/pagination-v7.png b/app/images/claims/scaling-back-mvp-claims/pagination-v7.png similarity index 100% rename from app/images/claims/scaling-back-mvp/pagination-v7.png rename to app/images/claims/scaling-back-mvp-claims/pagination-v7.png diff --git a/app/images/claims/scaling-back-mvp/pagination-v8.png b/app/images/claims/scaling-back-mvp-claims/pagination-v8.png similarity index 100% rename from app/images/claims/scaling-back-mvp/pagination-v8.png rename to app/images/claims/scaling-back-mvp-claims/pagination-v8.png diff --git a/app/images/claims/scaling-back-mvp/scheme-guidance.png b/app/images/claims/scaling-back-mvp-claims/scheme-guidance.png similarity index 100% rename from app/images/claims/scaling-back-mvp/scheme-guidance.png rename to app/images/claims/scaling-back-mvp-claims/scheme-guidance.png diff --git a/app/images/claims/scaling-back-mvp/select-training-v7.png b/app/images/claims/scaling-back-mvp-claims/select-training-v7.png similarity index 100% rename from app/images/claims/scaling-back-mvp/select-training-v7.png rename to app/images/claims/scaling-back-mvp-claims/select-training-v7.png diff --git a/app/images/claims/scaling-back-mvp/select-training-v8.png b/app/images/claims/scaling-back-mvp-claims/select-training-v8.png similarity index 100% rename from app/images/claims/scaling-back-mvp/select-training-v8.png rename to app/images/claims/scaling-back-mvp-claims/select-training-v8.png diff --git a/app/images/claims/scaling-back-mvp/sign-in.png b/app/images/claims/scaling-back-mvp-claims/sign-in.png similarity index 100% rename from app/images/claims/scaling-back-mvp/sign-in.png rename to app/images/claims/scaling-back-mvp-claims/sign-in.png diff --git a/app/images/claims/scaling-back-mvp/training-list.png b/app/images/claims/scaling-back-mvp-claims/training-list.png similarity index 100% rename from app/images/claims/scaling-back-mvp/training-list.png rename to app/images/claims/scaling-back-mvp-claims/training-list.png diff --git a/app/images/processing/scaling-back-mvp/claim-details-no.png b/app/images/processing/scaling-back-mvp-processing/claim-details-no.png similarity index 100% rename from app/images/processing/scaling-back-mvp/claim-details-no.png rename to app/images/processing/scaling-back-mvp-processing/claim-details-no.png diff --git a/app/images/processing/scaling-back-mvp/claim-details-v3.png b/app/images/processing/scaling-back-mvp-processing/claim-details-v3.png similarity index 100% rename from app/images/processing/scaling-back-mvp/claim-details-v3.png rename to app/images/processing/scaling-back-mvp-processing/claim-details-v3.png diff --git a/app/images/processing/scaling-back-mvp/claim-details-yes.png b/app/images/processing/scaling-back-mvp-processing/claim-details-yes.png similarity index 100% rename from app/images/processing/scaling-back-mvp/claim-details-yes.png rename to app/images/processing/scaling-back-mvp-processing/claim-details-yes.png diff --git a/app/posts/processing/2024-10-18-rejection-notes copy.md b/app/posts/archive/__2024-10-18-rejection-notes copy.md similarity index 99% rename from app/posts/processing/2024-10-18-rejection-notes copy.md rename to app/posts/archive/__2024-10-18-rejection-notes copy.md index 2ba0798..4375f84 100644 --- a/app/posts/processing/2024-10-18-rejection-notes copy.md +++ b/app/posts/archive/__2024-10-18-rejection-notes copy.md @@ -1,3 +1,5 @@ +[Archived] + --- title: Improving rejection notes description: Helping processors provide useful information to submitters when a claim is rejected. diff --git a/app/posts/claims/2024-03-05-starting-beta.md b/app/posts/claims/2024-03-05-starting-beta.md index 2ee4b63..c00c7a3 100644 --- a/app/posts/claims/2024-03-05-starting-beta.md +++ b/app/posts/claims/2024-03-05-starting-beta.md @@ -14,6 +14,13 @@ aside: Password: bsaasc123 --- +Contents +--- [Recording design decisions in alpha](#recording-design-decisions-in-alpha) +--- [Challenges with the Confluence approach](#challenges-with-the-confluence-approach) +--- [Transition to the x-govuk design history tool](#transition-to-the-x-govuk-design-history-tool) +--- [Alignment with NHS BSA UCD logs](#alignment-with-nhs-bsa-ucd-logs) +--- [Next steps](#next-steps) + ## Recording design decisions in alpha During alpha, we recorded design decisions in Confluence using a simple table format. This method helped us: - Keep information organized. diff --git a/app/posts/claims/2024-03-14-cost-per-learner-submitter.md b/app/posts/claims/2024-03-14-cost-per-learner-submitter.md index a6af345..927b093 100644 --- a/app/posts/claims/2024-03-14-cost-per-learner-submitter.md +++ b/app/posts/claims/2024-03-14-cost-per-learner-submitter.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work For care skills claims there is a maximum reimbursement amount for every training course or qualification. This is set by DHSC as part of the [scheme guidance](https://www.gov.uk/government/publications/adult-social-care-learning-and-development-support-scheme/eligible-training-courses-and-qualifications). diff --git a/app/posts/claims/2024-03-23-scaling-back-mvp.md b/app/posts/claims/2024-03-23-scaling-back-mvp-claims.md similarity index 94% rename from app/posts/claims/2024-03-23-scaling-back-mvp.md rename to app/posts/claims/2024-03-23-scaling-back-mvp-claims.md index 0c05905..43fa40c 100644 --- a/app/posts/claims/2024-03-23-scaling-back-mvp.md +++ b/app/posts/claims/2024-03-23-scaling-back-mvp-claims.md @@ -1,5 +1,5 @@ --- -title: Scaling back MVP +title: Scaling back MVP (Claims) description: With a tight delivery deadline fast approaching and an increasing amount of technical unknowns the decision was made by the product owner to scale back the MVP at the start of Beta. author: name: Mark Portnell (Interaction designer) @@ -21,6 +21,20 @@ aside: Password: ascbsa123 --- +Contents +--- [Introduction](#introduction) +--- [Using Azure B2C for authentication and account creation](#using-azure-b2c-for-authentication-and-account-creation) +--- [Remove eligible training list from service for MVP](#remove-eligible-training-list-from-service-for-mvp) +--- [Remove paid status from MVP](#remove-paid-status-from-mvp) +--- [Remove searching/filtering for MVP](#remove-searching/filtering-for-mvp) +--- [Remove pagination for MVP](#remove-pagination-for-mvp) +--- [Remove multiple learners per claim for MVP](#remove-multiple-learners-per-claim-for-mvp) +--- [Remove ability to view uploaded evidence for MVP](#remove-ability-to-view-uploaded-evidence-for-mvp) +--- [Remove training details for MVP](#remove-training-details-for-mvp) +--- [Remove claim history information for MVP](#remove-claim-history-information-for-mvp) + +## Introduction + With an aggressive delivery deadline fast approaching and an increasing amount of technical unknowns the decision was made by the product owner to scale back the MVP at the start of Beta. Across a couple of workshops attended by the entire product team a series of key decisions were made to cut out or scale back certain features for MVP. These product decisions were all logged in our project decision log held in Jira along with any associated risks and mitigations. We finished Alpha with v7 of the prototype, this version was not tested with users before these decisions were made and therefore changes were made in v8 of the prototype for future testing. As these decisions also impact design and explain how we moved from v7 to v8 and some of the changes are made. diff --git a/app/posts/claims/2024-03-26-manage-claims.md b/app/posts/claims/2024-03-26-manage-claims.md index 168d58a..e6aa0b0 100644 --- a/app/posts/claims/2024-03-26-manage-claims.md +++ b/app/posts/claims/2024-03-26-manage-claims.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work At the end of alpha, the design for managing claims consisted of a single page with a tabs component. Each tab represented a specific state a claim could be in (e.g., approved or submitted). Within each tab was a table displaying claims in that corresponding state. diff --git a/app/posts/claims/2024-03-27-removing-cpd.md b/app/posts/claims/2024-03-27-removing-cpd.md index 1867c10..aee1b54 100644 --- a/app/posts/claims/2024-03-27-removing-cpd.md +++ b/app/posts/claims/2024-03-27-removing-cpd.md @@ -14,6 +14,11 @@ aside: [View claims v8 prototype](https://adult-social-care-7fe9bafd955a.herokuapp.com/claims/prototypes/design/v8/) Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) ## Why we did this work diff --git a/app/posts/claims/2024-03-28-claims-tables.md b/app/posts/claims/2024-03-28-claims-tables.md index 554d79b..99680de 100644 --- a/app/posts/claims/2024-03-28-claims-tables.md +++ b/app/posts/claims/2024-03-28-claims-tables.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work We knew that in the near future we would need designs to accommodate 60/40 claims. As part of our exploration of 60/40 claims, we considered the possibility of having three different types of claims in the service for care skills funding: 100%, 60%, and 40% claims. We were also exploring a design hypothesis for how users might manage revalidation funding claims. diff --git a/app/posts/claims/2024-04-06-account-creation-mvp.md b/app/posts/claims/2024-04-06-account-creation-mvp.md index afb834b..e01b845 100644 --- a/app/posts/claims/2024-04-06-account-creation-mvp.md +++ b/app/posts/claims/2024-04-06-account-creation-mvp.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work To use the service, organisations must first be onboarded, and users within those organisations will need accounts. Onboarding ensures that the organisations are legitimate, and the user authentication process helps reduce fraud and maintain a secure service. diff --git a/app/posts/claims/2024-04-08-time-sensitive.md b/app/posts/claims/2024-04-08-time-sensitive.md index cc74ceb..14984c8 100644 --- a/app/posts/claims/2024-04-08-time-sensitive.md +++ b/app/posts/claims/2024-04-08-time-sensitive.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work Two time-sensitive policy requirements were introduced: diff --git a/app/posts/claims/2024-04-15-claim-duplication.md b/app/posts/claims/2024-04-15-claim-duplication.md index 9fe9ffa..1831855 100644 --- a/app/posts/claims/2024-04-15-claim-duplication.md +++ b/app/posts/claims/2024-04-15-claim-duplication.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work The scheme rules state that a claim will only be paid out once per training and learner combination. This means that organisations can't claim reimbursement for training that a learner takes more than once. We need to enforce this rule within our service. diff --git a/app/posts/claims/2024-04-15-learner-duplication.md b/app/posts/claims/2024-04-15-learner-duplication.md index f542813..6c0e968 100644 --- a/app/posts/claims/2024-04-15-learner-duplication.md +++ b/app/posts/claims/2024-04-15-learner-duplication.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work Learners in our service are unique entities identified by their National Insurance (NI) number. Whenever a learner is added to the service for use in a claim, that learner is saved and can be used in future claims. As a result, if a user adds a new learner with an NI number that matches a learner already in the system, we need a mechanism to address this and prevent duplicate learners from being added. diff --git a/app/posts/claims/2024-04-16-multiple-evidence-payment.md b/app/posts/claims/2024-04-16-multiple-evidence-payment.md index cacf1c1..287deba 100644 --- a/app/posts/claims/2024-04-16-multiple-evidence-payment.md +++ b/app/posts/claims/2024-04-16-multiple-evidence-payment.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work During routine reading of project material, our content designer had a realization: diff --git a/app/posts/claims/2024-04-21-claim-submission-error.md b/app/posts/claims/2024-04-21-claim-submission-error.md index d0fd446..908f9a4 100644 --- a/app/posts/claims/2024-04-21-claim-submission-error.md +++ b/app/posts/claims/2024-04-21-claim-submission-error.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work The claim scaffold screen features a somewhat unique use of the summary list component. This screen allows users to add the relevant information to each section in a flexible way, at times suitable for the user. Our design decision log from alpha covers the rationale behind using summary lists in this way, rather than other patterns like the task list. diff --git a/app/posts/claims/2024-04-25-select-training.md b/app/posts/claims/2024-04-25-select-training.md index 4169e14..71c2028 100644 --- a/app/posts/claims/2024-04-25-select-training.md +++ b/app/posts/claims/2024-04-25-select-training.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work We had been given an agreed eligible training list for the care skills funding pot for the start of private beta. To date, we had made some assumptions and created a general structure for what we felt this data would contain and then designed around that. Now we had this new training list, and we needed to adapt how the training list is displayed in the select training screen to accommodate the new data structure. diff --git a/app/posts/claims/2024-05-21-claims-tables-iteration.md b/app/posts/claims/2024-05-21-claims-tables-iteration.md index c629551..3ffc966 100644 --- a/app/posts/claims/2024-05-21-claims-tables-iteration.md +++ b/app/posts/claims/2024-05-21-claims-tables-iteration.md @@ -16,6 +16,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work Before implementing the new funding model, we conducted preliminary groundwork to prepare for its introduction. With the new model, different types of claims were introduced, initially categorized as: diff --git a/app/posts/claims/2024-05-30-60-40-design.md b/app/posts/claims/2024-05-30-60-40-design.md index a6064b6..8602382 100644 --- a/app/posts/claims/2024-05-30-60-40-design.md +++ b/app/posts/claims/2024-05-30-60-40-design.md @@ -15,6 +15,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work Our service previously focused on a 100% funding model, where claims were submitted after course completion. However, we needed to adapt the design to support a new 60/40 funding model. This model requires users to submit evidence of payment for 60% of the reimbursement amount after the course begins and then submit evidence of completion for the remaining 40%. diff --git a/app/posts/claims/2024-06-11-supporting-onboarding.md b/app/posts/claims/2024-06-11-supporting-onboarding.md index 3cfbb7f..ac50b16 100644 --- a/app/posts/claims/2024-06-11-supporting-onboarding.md +++ b/app/posts/claims/2024-06-11-supporting-onboarding.md @@ -12,6 +12,12 @@ tags: - content --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work DHSC and NHSBSA were keen to quickly onboard adult social care (ASC) organisations to the live service during private beta. This is important to see how the service is performing in the real world, understand how well the scheme is understood and utilise the fund effectively by getting as much money as possible to claimants. diff --git a/app/posts/claims/2024-06-20-cpd-claims.md b/app/posts/claims/2024-06-20-cpd-claims.md index 216e1be..dd9f272 100644 --- a/app/posts/claims/2024-06-20-cpd-claims.md +++ b/app/posts/claims/2024-06-20-cpd-claims.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + So far the prototype only allows for TU claims to be submitted, as dictated by roadmap and priorities we now want to bring in CPD claims. The expectation is that there are going to be less of these type of claims, so the direction was to balance user needs with coming up with a design flow that has the least amount of changes needed to the TU journey, with minimal technical effort, to allow for less work and quicker delivery. ## Why we did this work diff --git a/app/posts/claims/2024-06-27-org-admin-phase-1.md b/app/posts/claims/2024-06-27-org-admin-phase-1.md index 0d161d0..257efb3 100644 --- a/app/posts/claims/2024-06-27-org-admin-phase-1.md +++ b/app/posts/claims/2024-06-27-org-admin-phase-1.md @@ -15,6 +15,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work For the start of private beta, a key constraint of the service was that it would only allow one user per organisation, this user was the signatory. Due to the delivery deadline and uncertainty around the legal aspect of the grant determination letter, our onboarding process for the start of private beta would need to have this signatory be the representative from the organisation who signs up and subsequently would be the only permitted user of the service from that organisation for day 1 of private beta. diff --git a/app/posts/claims/2024-07-17-cpd-claim-iteration.md b/app/posts/claims/2024-07-17-cpd-claim-iteration.md index b969d38..2375460 100644 --- a/app/posts/claims/2024-07-17-cpd-claim-iteration.md +++ b/app/posts/claims/2024-07-17-cpd-claim-iteration.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + There were three key aspects of the CPD journey identified as not working and needing further iteration. The activity type, evidence of completion collection, and CPD eligibility. Worked through options of design and held workshop to discuss and crit with business. ## Why we did this work diff --git a/app/posts/claims/2024-07-25-60-40-iteration.md b/app/posts/claims/2024-07-25-60-40-iteration.md index 4d37166..ffaca5b 100644 --- a/app/posts/claims/2024-07-25-60-40-iteration.md +++ b/app/posts/claims/2024-07-25-60-40-iteration.md @@ -15,6 +15,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work At the end of May 2024 and the start of June 2024, we introduced a 60/40 funding model for eligible training (as described in the post "Designing for a different funding model - 60/40"). During this work, we had two conflicting mental models about how users might approach the 60/40 claim: diff --git a/app/posts/claims/2024-08-12-signatory-to-sro.md b/app/posts/claims/2024-08-12-signatory-to-sro.md index c79e248..24b0bf0 100644 --- a/app/posts/claims/2024-08-12-signatory-to-sro.md +++ b/app/posts/claims/2024-08-12-signatory-to-sro.md @@ -17,6 +17,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work During alpha, we had established the need for each organisation to sign the grant determination letter (GDL) before they could use the service. diff --git a/app/posts/claims/2024-08-20-delete-a-claim.md b/app/posts/claims/2024-08-20-delete-a-claim.md index 706903d..de1ea8e 100644 --- a/app/posts/claims/2024-08-20-delete-a-claim.md +++ b/app/posts/claims/2024-08-20-delete-a-claim.md @@ -15,6 +15,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work There are a few scenarios that could lead to a claim being created that can't or won't be progressed: diff --git a/app/posts/claims/2024-08-20-delete-a-submitter.md b/app/posts/claims/2024-08-20-delete-a-submitter.md index 3500f0c..1c5a2f4 100644 --- a/app/posts/claims/2024-08-20-delete-a-submitter.md +++ b/app/posts/claims/2024-08-20-delete-a-submitter.md @@ -15,6 +15,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work Senior Responsible Officers (SROs), previously called Signatories, can invite up to 9 additional submitters to use the service on behalf of the organisation. We identified a few scenarios where a submitter invited by an SRO might no longer need access to the service: diff --git a/app/posts/claims/2024-08-20-view-uploaded-evidence.md b/app/posts/claims/2024-08-20-view-uploaded-evidence.md index 9fdf767..1761a41 100644 --- a/app/posts/claims/2024-08-20-view-uploaded-evidence.md +++ b/app/posts/claims/2024-08-20-view-uploaded-evidence.md @@ -14,6 +14,11 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) + ## Why we did this work Once a submitter uploads a file as a piece of evidence, there is currently no way to view that file in the service. We identified a few scenarios that may mean an individual would benefit from viewing the evidence they uploaded: diff --git a/app/posts/claims/2024-09-18-removing-care-skills.md b/app/posts/claims/2024-09-18-removing-care-skills.md index 253010a..04e07b0 100644 --- a/app/posts/claims/2024-09-18-removing-care-skills.md +++ b/app/posts/claims/2024-09-18-removing-care-skills.md @@ -17,6 +17,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work The original funding scheme - the Training Fund Reimbursement Scheme (TFRS) - consisted of 2 types of funding: diff --git a/app/posts/claims/2024-10-20-find-a-claim.md b/app/posts/claims/2024-10-20-find-a-claim.md index 993367e..0d1d0b4 100644 --- a/app/posts/claims/2024-10-20-find-a-claim.md +++ b/app/posts/claims/2024-10-20-find-a-claim.md @@ -15,6 +15,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work During alpha a few options were tried to allow users to search and filter for claims in their dashboard, this was removed from the prototype to help descope the complexity of the MVP. The need for users to be able to find a claim easily is still present. diff --git a/app/posts/claims/2024-11-11-three-character-minimum-search.md b/app/posts/claims/2024-11-11-three-character-minimum-search.md index 719a5de..94c651d 100644 --- a/app/posts/claims/2024-11-11-three-character-minimum-search.md +++ b/app/posts/claims/2024-11-11-three-character-minimum-search.md @@ -15,6 +15,11 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) + ## Why we did this work The introduction of a three-character minimum search limit emerged during advanced search design discussions. Initially, users could search with a single character, which had potential to produced lengthy result lists requiring pagination and table sorting features to be a higher priority to help the user work through results. These features are more technically complex and time-consuming to implement though so this prompted a consideration of the trade-offs between usability and roadmap priorities. It was decided that users likely have sufficient information to input at least three characters, making this a minimal inconvenience to users, while dramatically reducing number of results. Pagination and sorting were deprioritized and added to the backlog for post-MVP implementation across the service. diff --git a/app/posts/claims/2024-11-20-aligning-user-expectations.md b/app/posts/claims/2024-11-20-aligning-user-expectations.md index 5779f58..d495fb0 100644 --- a/app/posts/claims/2024-11-20-aligning-user-expectations.md +++ b/app/posts/claims/2024-11-20-aligning-user-expectations.md @@ -13,6 +13,12 @@ tags: - WDF --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work We suspected for a while that some new users of the service had unrealistic expectations of what they could get reimbursement for and how the claims process worked. We thought this was particularly likely for people who'd used the Workforce Development Fund (WDF) previously. This is the legacy reimbursement scheme that LDSS is replacing. diff --git a/app/posts/claims/2024-12-13-claim-table-pagination.md b/app/posts/claims/2024-12-13-claim-table-pagination.md index a40c3c0..6aa6ba1 100644 --- a/app/posts/claims/2024-12-13-claim-table-pagination.md +++ b/app/posts/claims/2024-12-13-claim-table-pagination.md @@ -14,6 +14,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work As part of work done to scale back the MVP in March to try and meet an aggressive delivery schedule, we removed pagination from the proposed designs. Please see the design history post [Scaling back MVP](../scaling-back-mvp) for more details on the aspects removed from the MVP as part of that work. diff --git a/app/posts/claims/2025-01-08-claim-history.md b/app/posts/claims/2025-01-08-claim-history.md index d3e5cb7..de42667 100644 --- a/app/posts/claims/2025-01-08-claim-history.md +++ b/app/posts/claims/2025-01-08-claim-history.md @@ -14,6 +14,12 @@ aside: Password: bsaasc123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work As part of the work done to scale back the MVP in March to meet an aggressive delivery schedule, we removed claims from the proposed designs for the claims app. For more details about the aspects removed from the MVP, please refer to the design history post [Scaling back MVP](../scaling-back-mvp). diff --git a/app/posts/processing/2024-05-05-scoping-for-mvp.md b/app/posts/processing/2024-05-05-scoping-for-mvp.md index 64d7fee..b171569 100644 --- a/app/posts/processing/2024-05-05-scoping-for-mvp.md +++ b/app/posts/processing/2024-05-05-scoping-for-mvp.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + Version 1 Claim ID's Submitted: Z1Z-F1J6-3XF7-C Approved: Z8S-F1J6-4GH7-C diff --git a/app/posts/processing/2024-05-12-iterating-post-research.md b/app/posts/processing/2024-05-12-iterating-post-research.md index 7dbd30b..dd71740 100644 --- a/app/posts/processing/2024-05-12-iterating-post-research.md +++ b/app/posts/processing/2024-05-12-iterating-post-research.md @@ -14,6 +14,13 @@ aside: [View processing prototypes](https://adult-social-care-7fe9bafd955a.herokuapp.com/version-index?area=Processing) Password: ascbsa123 --- + +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + Version 2 Claim ID's Submitted: Z1Z-F1J6-3XF7-C Approved: Z8S-F1J6-4GH7-C diff --git a/app/posts/processing/2024-05-13-cost-per-learner-processor.md b/app/posts/processing/2024-05-13-cost-per-learner-processor.md index 9e3e44b..fff527e 100644 --- a/app/posts/processing/2024-05-13-cost-per-learner-processor.md +++ b/app/posts/processing/2024-05-13-cost-per-learner-processor.md @@ -17,6 +17,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work During alpha, we had explored [asking submitters to identify the training cost per learner](/claims/cost-per-learner-submitter/) so the service could accurately calculate the amount of reimbursement due. diff --git a/app/posts/processing/2024-05-15-scaling-back-mvp.md b/app/posts/processing/2024-05-15-scaling-back-mvp-processing.md similarity index 96% rename from app/posts/processing/2024-05-15-scaling-back-mvp.md rename to app/posts/processing/2024-05-15-scaling-back-mvp-processing.md index 220b277..09c3a96 100644 --- a/app/posts/processing/2024-05-15-scaling-back-mvp.md +++ b/app/posts/processing/2024-05-15-scaling-back-mvp-processing.md @@ -1,5 +1,5 @@ --- -title: Scaling back MVP +title: Scaling back MVP (Processing) description: Due to MVP decisions we stripped back many of the design decisions to accommodate quicker technical delivery. author: @@ -16,6 +16,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What we removed](#what-we-removed) +--- [Next steps](#next-steps) + + Claim id's to test version 3: 100 Submitted: Z1Z-F1J6-3XF7-A @@ -39,7 +45,7 @@ With an aggressive delivery deadline fast approaching and tight time to technica In a workshop attended by the entire product team a series of key decisions were made to cut out or scale back certain features for this journey. These product decisions were all logged in our project decision log held in Mira along with any associated risks and mitigations. The extended journey is in V2 of the prototype, this version was untested with users before these decisions were made so changes were made in V3 of the prototype. V3 has been tested with 4 users in the week commencing 15 May 2024. -## What our ideas were +## What we removed Here is the new scaled back landing view of a claim in the processing a claim prototype journey: @@ -94,8 +100,7 @@ Removed ability to save claim mid processing for MVP as is a feature deemed nice - Processors will be aware they need to complete their checks in one go. ------- - +## Next steps Future research: - Research to understand the impact of MVP changes diff --git a/app/posts/processing/2024-05-17-approved-and-rejected-states-for-100-claim.md b/app/posts/processing/2024-05-17-approved-and-rejected-states-for-100-claim.md index 1471e2a..152123d 100644 --- a/app/posts/processing/2024-05-17-approved-and-rejected-states-for-100-claim.md +++ b/app/posts/processing/2024-05-17-approved-and-rejected-states-for-100-claim.md @@ -16,6 +16,11 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) + ## Why we did this work diff --git a/app/posts/processing/2024-05-30-update-for-40.md b/app/posts/processing/2024-05-30-update-for-40.md index 9a8a62c..ba03ae6 100644 --- a/app/posts/processing/2024-05-30-update-for-40.md +++ b/app/posts/processing/2024-05-30-update-for-40.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + Version 3 claim id's for processing 100 diff --git a/app/posts/processing/2024-05-30-update-for-60.md b/app/posts/processing/2024-05-30-update-for-60.md index ff32d6b..e863f34 100644 --- a/app/posts/processing/2024-05-30-update-for-60.md +++ b/app/posts/processing/2024-05-30-update-for-60.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work For care skills funding there are two funding types: 100, and 60/40. So far the prototype and designs allow for 100 claims to be processed, but for MVP both 100 and 60 claims are expected to be delivered. There are differences between the information that is supplied by the submitter for these two types of claims so the designs need to be changed and considered to allow for them to be processed. The 40 part of the 60/40 claim is not expected to have any claims submitted for for quite some time so some scope that they may not need to be included for MVP, but because so closely linked with 60, still need to be considered during the design process to allow for a holistic journey and reduce amount of work needing to be done in the future. diff --git a/app/posts/processing/2024-07-09-cpd-processing.md b/app/posts/processing/2024-07-09-cpd-processing.md index 43db3e3..d71a3db 100644 --- a/app/posts/processing/2024-07-09-cpd-processing.md +++ b/app/posts/processing/2024-07-09-cpd-processing.md @@ -15,6 +15,11 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) + ## Why we did this work The prototype has been expanded to allow CPD claims to be submitted. The expectation is that there are going to be less of these type of claims, so the work balanced user needs with coming up with a design flow that has the least amount of changes needed to the TU journey, with minimal technical effort. This means when bringing CPD claims now into the processing side of the service there is also minimal design effort, more following the patterns and process of what has already been done. diff --git a/app/posts/processing/2024-08-08-reimbursement-calculations.md b/app/posts/processing/2024-08-08-reimbursement-calculations.md index 4017d57..4d1f1e9 100644 --- a/app/posts/processing/2024-08-08-reimbursement-calculations.md +++ b/app/posts/processing/2024-08-08-reimbursement-calculations.md @@ -16,6 +16,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work It’s important for processing staff to understand how the reimbursement amount for a claim is calculated. This gives them the confidence they’ve processed it correctly and allows them to respond to any queries escalated from the contact centre. diff --git a/app/posts/processing/2024-09-18-post-processing-emails.md b/app/posts/processing/2024-09-18-post-processing-emails.md index 60748b8..d782b79 100644 --- a/app/posts/processing/2024-09-18-post-processing-emails.md +++ b/app/posts/processing/2024-09-18-post-processing-emails.md @@ -16,6 +16,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work It was very apparent from the earliest rounds of UR in alpha that users did not want the reimbursement process to be a ‘black box’. They wanted to know what was happening to their claims, for instance, so they could predict when the money would reach their bank account and therefore manage their cash flow effectively. diff --git a/app/posts/processing/2024-10-09-registering-a-org-iteration.md b/app/posts/processing/2024-10-09-registering-a-org-iteration.md index d092176..9cc0058 100644 --- a/app/posts/processing/2024-10-09-registering-a-org-iteration.md +++ b/app/posts/processing/2024-10-09-registering-a-org-iteration.md @@ -15,6 +15,13 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + + Three journey flows developed, id's to search to force down particular journeys in the prototype: - New org (type in "G03944234"), add a signatory and invite them and org. - A invited not registered signatory (type in "B02944934"), can send a new invite or edit details to send new diff --git a/app/posts/processing/2024-11-25-find-a-organisation.md b/app/posts/processing/2024-11-25-find-a-organisation.md index b3e26b9..8f109a8 100644 --- a/app/posts/processing/2024-11-25-find-a-organisation.md +++ b/app/posts/processing/2024-11-25-find-a-organisation.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work At the moment, both organisations and BSA staff are struggling to resolve organisation-related problems quickly, which is affecting processing times. The limitation of accessibility to organisational details and a centralized access for BSA staff, including processors and CCS agents, makes organisation-related issues unable to be resolved promptly. Currently BSA staff are unable to carry out IDCV when an organisation calls and they cannot currently verify who they are speaking to. These are both issues I aimed to answer in this first ticket. diff --git a/app/posts/processing/2024-11-26-complete-id-cv-check.md b/app/posts/processing/2024-11-26-complete-id-cv-check.md index 29dbc8e..9728382 100644 --- a/app/posts/processing/2024-11-26-complete-id-cv-check.md +++ b/app/posts/processing/2024-11-26-complete-id-cv-check.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## Why we did this work As part of the work to help organisations and BSA staff resolve organisation-related problems quickly, this is the second part of my ticket to give BSA staff functionality to complete the ID/CV check so then they can progress with the query within the centralised organisation view. Important while doing this piece of work to bear in mind the wider scope and potential future features to make sure we design in a way that is scalable and maintainable. diff --git a/app/posts/processing/2024-12-13-find-org-and-do-check-design.md b/app/posts/processing/2024-12-13-find-org-and-do-check-design.md index 214f5c2..03e6343 100644 --- a/app/posts/processing/2024-12-13-find-org-and-do-check-design.md +++ b/app/posts/processing/2024-12-13-find-org-and-do-check-design.md @@ -15,6 +15,12 @@ aside: Password: ascbsa123 --- +Contents +--- [Why we did this work](#why-we-did-this-work) +--- [What our ideas were](#what-our-ideas-were) +--- [How we tested our ideas and what we found](#how-we-tested-our-ideas-and-what-we-found) +--- [What we will do next](#what-we-will-do-next) + ## What our ideas were >**We believe that** having one input box with examples of valid