Open natalia-fitzgerald opened 1 year ago
@angelcardoz @natalia-fitzgerald three last questions for the task flow related to how we handle progress:
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?
@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.
@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.
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.
Reorganized epic content to match new epic template.
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
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.