cfpb / sbl-project

Project management repo for the SBL project
Creative Commons Zero v1.0 Universal
0 stars 1 forks source link

[Epic] Small business lending filing home #14

Open natalia-fitzgerald opened 1 year ago

natalia-fitzgerald commented 1 year ago

Milestone: View financial institution details

The small business lending filing app will be used by financial institutions to file their annual lending data, view past filings, view financial institution details for past filings and review data files for errors and warnings.

Epic: Small business lending filing home

Overview

The small business lending filing home is the starting point for filing small business lending data.

Tasks

User stories

MVP (Beta release)

Backlog (post-MVP)

Questions

  1. How much consideration do we need to give now to all of the 2nd year+ scenarios?
    1. A filer is told by SEFL they need to re-file after an exam.
    2. A filer didn't file for a past year.
  2. Are we going to have a 3-year window where we allow refiling like HMDA?

Requirements

Technical requirements

Content

User testing

Research goals

Task ideation

Current mock-ups

Updated: MM/DD/YYYY

The purpose of this mock-up is to give an impression of how the components that I have shared might fit together. The details are all subject to change based on the design and functionality of the rest of the filing platform screens.

SBL filing home
9ec867c2-f0cf-4ad7-8885-f3d6afb53674
dan-padgett commented 7 months ago

@angelcardoz @natalia-fitzgerald three last questions for the task flow related to how we handle progress:

  1. If a filing has been submitted, what actions can the user take? Currently we will show them that the filing is submitted. But should they be able to review the submission?
  2. When it comes to showing progress for the filing process, one approach is to include the date that a page was last accessed or updated (or, a bit more user friendly, whether it's been updated since they last viewed the page). To me, this seems like a good way to go for steps like reviewing financial institution details where there's not as clear of a linear flow like there is for the file upload step. For the file upload step we would still include the progress indicator. What do you think of this proposal?
  3. I've modified the task flow so that what the user sees on this page depends on what they've done:
    • If they haven't started, they only have a way to start the process
    • If they've started the process but haven't completed the file upload step, they see all the steps except the final one
    • Once their file is error free, they see the final step

The thought behind this approach is that it's another way to indicate progress: as you complete more steps, you have more actions available to you. Do you think this approach is worth pursuing?

natalia-fitzgerald commented 7 months ago

@dan-padgett As a starting point for discussion, here's what a user sees in HMDA once a filing has been submitted. The user can click on "View completed filing" to see a submitting receipt with all of the filing details. Or they can click on the "Upload a new file" to create a new submission.
Screenshot 2024-02-05 at 7 23 39 AM screencapture-ffiec-cfpb-gov-filing-2023-BANK1LEIFORTEST12345-submission-2024-02-05-07_21_50 Screenshot 2024-02-05 at 1 22 20 PM

natalia-fitzgerald commented 7 months ago

@dan-padgett I have some additional questions that are a little jumbled together (definitely broader than this epic) but hopefully some useful morsels in here.

Questions for discussion

What does a user gain in knowing that a step is in progress but not completed? If in progress simply means that any change was made (box checked, file uploaded, text input populated) wouldn't a user need to know what change was made for this progress status information to be useful? If they know something was done but don't know what then don't they have to review everything again anyway?

Zooming out a little further if a user can revisit any step in the filing process (or even if they can't) then no step is really ever complete until the filing is signed and submitted. The filing is in progress in all respects until the submit filing button is clicked. So when we say completed for a step or task what do we mean and what does this mean to a user?

Can a user come back and resubmit (changing whatever they wish) as many times as they wish until the filing deadline is reached or until a certain period is reached (3 years for HMDA?)?

Is the "Review financial institution details" step (which doesn't fit in the sequential flow) the one that is leading us to the need for prioritizing the visualization of the status of each step in the process on the homepage? If the steps were sequential would we still need this?

What does a user lose if they only see the current status more broadly (not started, in progress, complete) and they return to the next step (in other words the step which they have not yet clicked the save and continue for). If there is a need to allow them to jump around in the flow? If yes, an alternative to explore is giving them a way to do this within the filing process instead of from the filing home.

If "Review financial institution details" is outside of the sequential steps should we consider separating it out from the sequential steps/the filing flow without sacrificing the rest of the sequential flow? Maybe we could include a link on the financial institution card. And then we could include a review FI step (read-only) at the end of the filing process as a part of provide financial institution point of contact and sign and submit. Just brainstorming.

Or we can leave the review/update at the beginning and also put it at the end. So it doesn't stop the user from proceeding but it gets them to start thinking that they will need these details to be accurate before they file. At the end it could be an actual confirmation of the financial institution details (read-only) they are about to submit with their filing.

Speaking of which, what language do we need to communicate that the financial institution details must be accurate to file? Thus far there is no language to this effect in what we've built/are building. As a part of the "Review fi details" step we'll want to provide context as to why this content needs to be accurate.

What happens if the financial institution profile details (in our system) change before the filing deadline (either because of user requests OR because of data source updates)? Does the user's filing get updated with whatever is current in our system on the filing deadline date or does the information only reflect the financial institution details as true on the date of submission?

For reference, in HMDA once you are in the process you can go back to a previous step but not forward to a subsequent step (until you have completed the current step). So as you move forward the previous steps become available to you. This ability to go back to a previous step is something that is available to a user within the filing process but not on the filing home card. The filing home card in HMDA visualizes the progress (just a visual) but does not allow a user to access any step in the process from there.

Screenshot 2024-02-05 at 8 16 53 AM

angelcardoz commented 6 months ago

Reorganized epic content to match new epic template.