Open angelcardoz opened 9 months ago
@angelcardoz @dan-padgett I'd like to dig in to the premise of this user story a bit more. I originally interpreted this user story simply indicating the broad filing status to a user - not started (no files have been uploaded), started (a file has been uploaded), or completed (filing signed and submitted). In the initial mock-ups this is indicated in the card heading, the card body text, and the button language.
The acceptance criteria, as written, takes this a step further and indicates that the financial institution card must accommodate an update status for each of the 5 steps in the filing process. This adds complexity, both visually and technically. So, before we decide to move in this direction I want to be sure that we've confirmed that a more simple approach does not meet the needs of the user, particularly in thinking about MVP.
In the current design there is a "History of progress this filing period" on the homepage that lists the actions that have been taken for a filing. It was determined recently that this is not needed for MVP. Additionally some determined that this level of detail would be more helpful at the upload stage, if we decided to later add it.
The "History of progress this filing period" would provide a user with a detailed accounting of all of the actions that have happened within a filing period (and the names of the users within the FI that made those changes). In HMDA, and as originally designed for SBL, this means file uploads. But for SBL, it has recently been mentioned that actions could include non-upload actions, in other words any type of change that is made by the user within a step/task. The "History of progress" is not immediately visible and must be clicked on by the user to see it. But, if this contextual information is only needed for certain users (users that start and come back, users that have multiple authorized/associated filers within their FI - are these the users that would need this?).
So, I'd like to dig a little deeper as to whether the user needs to see the 5 process steps and the status of each step on the filing home screen within the financial institution card? I wouldn't want to overwhelm a user or make the process seem more complicated or open ended than it actually is. Can we dig into this a bit more? Can we consider alternative places where we can give the user the opportunity to jump around while still providing more structure and guidance from the home card?
Also, this story looks similar but perhaps not identical to: https://github.com/cfpb/sbl-project/issues/110
@natalia-fitzgerald Here's a recap of our discussion from this morning and then a proposed change to the acceptance criteria.
Did I miss anything about where the discussion ended?
If we want to move in that direction, I think the acceptance criteria should be changed as follows:
Given a system user is logged in and has started the filing process for an associated financial institution, when they visit the small business lending filing home page, then the system displays the tasks that are in progress and/or have been completed for the respective financial institution along with an actionable element allows them to review financial institution details or start/continue the file upload process, then when the user clicks on the element they are redirected to that task.
With this revision, both the POC and sign and submit steps fall under the file upload task flow. Once a user goes to the file upload process, they would see a progress indicator similar to what HMDA shows.
@dan-padgett Documenting our discussion yesterday...we discussed the possibility of pulling out the "Type of financial institution" and the "Financial institution point of contact" as something that is requested either at the beginning or right before the sign and submit step. @angelcardoz planned to check the legal requirements related to the "Type of financial institution" question and whether there is specific language about where it must be requested.
We talked about the sign and submit step being an opportunity for the user to review everything (read-only) that they are about to submit (Financial institution details, Type of financial institution, Point of contact information, data file, etc.). In this flow the Reviewing and updating of financial institution details would be divorced from the linear filing flow, and separate from the filing process. We would still prioritize this review/update financial institution details step as a part of what is highlighted on the filing home page.
And to add some nuance/clarity to that first point, the options were:
Capturing financial institution first could be useful later on if type of financial institution affects any of the validations on a file. With any of these options, we'd effectively be consolidating the review of financial institution details to the end of the process, but before signing and submitting.
@dan-padgett - I think the user story will need some adjusting too. How's this?
@natalia-fitzgerald Yes, I think changing the language from "select a step" to "select the next step" fits with how we've been evolved our thinking on this task. I'm not sure we need "when I leave the platform" in the story since this would also cover the case of a user starting the filing process (in my mind, "next step" include "first step").
@dan-padgett
Yep, makes sense. How's this?
User story:
As a filer, I want to select the next step in the filing process for my associated financial institution, so that I can progress toward the completion of my filing.
Short name: Select the next step in the filing process for my associated financial institution
@angelcardoz @dan-padgett and I worked on updating this. Feel free to adjust as needed. We have been trying to determine whether there is a secondary action for each primary action and whether there is any need for any more than 2 possible actions for each entry point. In HMDA, for example, in the Review edits step there is: "Review edits" (button), "Download edit report" (link) and "Upload a new file" (link).
Generally we are trying to move toward guiding a user into the process (from the home screen) - through a more defined path - with the idea that if they would like to jump around and not follow the linear flow they have that option once they are in the filing app. Within the app they would be able to revisit steps they have "completed" but probably not be able to move ahead past uncompleted steps.
User story: As a filer, I want to select the next step in the filing process for my associated financial institution, so that I can progress toward the completion of my filing.
Short name: Select the next step in the filing process for my associated financial institution
Acceptance criteria Given a system user is logged in and has started the filing process for an associated financial institution, when they visit the small business lending filing home page, then the system displays the next step and an actionable element, then when the user clicks on the element they are redirected to that task.
Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
[Epic] Small business lending filing home https://github.com/cfpb/sbl-project/issues/14
User story
[Story] As a filer, I want to select the next step in the filing process for any of my associated financial institution, so that I can progress toward the completion of my filing.
Acceptance criteria
Given a system user is logged in and has started the filing process for an associated financial institution, when they visit the small business lending filing home page, then the system displays the next step and an actionable element, then when the user clicks on the element they are redirected to that task.
Technical tasks
Developers should create technical tasks and add links (below) prior to sprint planning.
Front end
Back end